Page Comparison

Table of Contents

minLevel	2
maxLevel	2
type	flat

Overview

Proofpoint's Email Isolation solution is a powerful tool for protecting against email-based threats, such as phishing and malware attacks. By isolating potentially dangerous email messages in a secure environment, Proofpoint prevents these messages from reaching end-users and reduces the risk of an attack succeeding.

With With Proofpoint Email Isolation, administrators can configure isolation policies based on specific criteria, such as sender reputation, attachment type, or keyword filtering. Isolated messages are stored securely and can be analyzed for threats, providing visibility into potential attacks and allowing organizations to take action to prevent them.

Configuration requirements

To run this collector, there are some configurations detailed below that you need to consider.

...

Configuration

...

Details

...

Cylance APP

...

You need to run a Cylance app.

...

Application ID

...

Once you create the App, it gives you an Application ID.

...

Application Secret

...

Once you create the App, it gives you an Application Secret.

...

Tenant ID

...

Proofpoint Browser Isolation secures the web browsing and email activities of your users. It uses cloud-based remote browser isolation to allow your people to access websites and their personal and corporate email freely, without exposing your organization to malware and data loss.

Devo collector features

Feature	Details
Allow parallel downloading (`multipod`)	`not allowed`
Running environments	`collector server` `on-premise`
Populated Devo events	`table`
Flattening preprocessing	`no`
Allowed source events obfuscation	`yes`

Data sources

Data source	Description	API endpoint	Collector service name	Devo table	Available from release
Browser and email isolation reports	Browser and email isolation report events	`https://proofpointisolation.com/api/v2/reporting/usage-data/`	`browser_and_email_isolation`	`tap.proofpoint.isolation.browser_and_email`	`v1.0.0`
URL isolation reports	URL isolation report events	`https://urlisolation.com/api/v2/reporting/usage-data/`	`url_isolation`	`tap.proofpoint.isolation.url_isolation`	`v1.0.0`

For more information on how the events are parsed, visit our page.

Vendor setup

Minimum configuration required for basic pulling

Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.

Info
This minimum configuration refers exclusively to those specific parameters of this integration. There are more required parameters related to the generic behavior of the collector. Check setting sections for details.

Setting	Details
`api_key`	API key

Steps

Action	Steps
Obtain API key	Navigate to Product Settings → Reporting API. The API key can be generated and found in the Isolation Reporting API Console's main viewing panel under Reporting API Key.

Assigning necessary permissions

Only the credentials above are required.

Run the collector

Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).

Rw ui tabs macro

Rw tab

title	On-premise collector

This data collector can be run in any machine that has the Docker service available because it should be executed as a docker container. The following sections explain how to prepare all the required setup for having the data collector running.

Structure

The following directory structure should be created for being used when running the collector:

Code Block

<any_directory>
└── devo-collectors/
    └── <product_name>/
        ├── certs/
        │   ├── chain.crt
        │   ├── <your_domain>.key
        │   └── <your_domain>.crt
        ├── state/
        └── config/ 
            └── config.yaml

Note
Replace `<product_name>` with the proper value.

Devo credentials

In Devo, go to Administration → Credentials → X.509 Certificates, download the Certificate, Private key and Chain CA and save them in <product_name>/certs/. Learn more about security credentials in Devo here.

Image Removed

Image Added

Note
Replace `<product_name>` with the proper value.

Editing the config.yaml file

Code Block

globals:
  debug: <debug_status>
  id: not_used
  name: proofpoint_isolation_collector
  persistence:
    type: filesystem
    config:
      directory_name: state
outputs:
  devo_us_1:
    type: devo_platform
    config:
      address: <devo_address>
      port: 443
      type: SSL
      chain: <chain_filename>
      cert: <cert_filename>
      key: <key_filename>
inputs:
  proofpoint_isolation:
    id: <input_id_value>
    enabled: true
    credentials:
      api_key: <api_key_value>
    services:
      browser_and_email_isolation:
        override_tag: <override_tag_value>
        start_time_in_utc: <start_time_in_utc_value>
        obfuscation_data: [<obfuscation_data_values>]
        override_query_window_offset_in_minutes: <override_query_window_offset_in_minutes_value>
      url_isolation:
        override_tag: <override_tag_value>
        start_time_in_utc: <start_time_in_utc_value>
        obfuscation_data: [<obfuscation_data_values>] obfuscation_data: [<obfuscation_data_values>]
        override_query_window_offset_in_minutes: <override_query_window_offset_in_minutes_value>

Info
All defined service entities will be executed by the collector. If you do not want to run any of them, just remove the entity from the `services` object.

Replace the placeholders with your required values following the description table below:

Parameter

Data type

Type

Value Range / Format

Details

debug_status

bool

mandatory

true / false

If the value is true, the debug logging traces will be enabled when running the collector. If the value is false, only the info, warning, and error logging levels will be printed.

devo_address

str

mandatory

collector-us.devo.io

collector-eu.devo.io

Use this parameter to identify the Devo Cloud where the events will be sent.

chain_filename

str

mandatory

minimum length: 4

maximum length: 20

Use this parameter to identify the chain.cert file downloaded from your Devo domain. Usually this file's name is: chain.crt.

cert_filename

str

mandatory

minimum length: 4

maximum length: 20

Use this parameter to identify the file.cert downloaded from your Devo domain.

key_filename

str

mandatory

minimum length: 4

maximum length: 20

Use this parameter to identify the file.key downloaded from your Devo domain.

input_id_value

int

Mandatory

Minimum length: 5

Maximum length: 15

Use this param to give a unique id to this input service.

Note
This parameter is used to build the persistence address. Do not use the same value for multiple collectors. It could cause a collision.

api_key_value

str

mandatory

Minimum length: 1

The API key obtained from the Proofpoint Isolation portal.

override_tag_value

str

optional

Devo tag-friendly string (no special characters, spaces, etc.)

An optional tag that allows users to override the service default tags.

Info
This parameter can be removed or commented.

start_time_in_utc_value

str

optional

UTC datetime string having datetime string format %-Y-%m-%d %H-%M-%S (e.g., “2000-01-01 00:00:01”)

This configuration allows you to set a custom date as the beginning of the period to download. This allows downloading historical data (one month back for example) before downloading new events.

Info
This parameter should be removed if it is not used.

obfuscation_data_values

array<object>

optional

The objects in the array look like this:

Code Block
obfuscation_data: - name: - credentials - "" value: "*********"

Each object represents the necessary configuration to obfuscate messages before these are sent to Devo.

Info
This parameter can be removed or commented.

Download the Docker image

The collector should be deployed as a Docker container. Download the Docker image of the collector as a .tgz file by clicking the link in the following table:

Collector Docker image	SHA-256 hash
collector-proofpoint_isolation_if-docker-image-1.01.01	`d8a7d12bc23189c5e83d11f110399ab283ce91768ff57c0b66706446c92b5ede732ce0edfd7c5855810227ee61f936e773d847ea78449810ff49b9bbde216d39`

Use the following command to add the Docker image to the system:

Code Block
gunzip -c <image_file>-<version>.tgz \| docker load

Note
Once the Docker image is imported, it will show the real name of the Docker image (including version info). Replace `<image_file>` and `<version>` with a proper value.

The Docker image can be deployed on the following services:

Docker

Execute the following command on the root directory <any_directory>/devo-collectors/<product_name>/

Code Block

docker run 
--name collector-<product_name> 
--volume $PWD/certs:/devo-collector/certs 
--volume $PWD/config:/devo-collector/config 
--volume $PWD/state:/devo-collector/state 
--env CONFIG_FILE=config.yaml 
--rm 
--interactive 
--tty 
<image_name>:<version>

Note
Replace `<product_name>`, `<image_name>` and `<version>` with the proper values.

Docker Compose

The following Docker Compose file can be used to execute the Docker container. It must be created in the <any_directory>/devo-collectors/<product_name>/ directory.

Code Block

version: '3'
services:
  collector-<product_name>:
    image: <image_name>:${IMAGE_VERSION:-latest}
    container_name: collector-<product_name>
    volumes:
      - ./certs:/devo-collector/certs
      - ./config:/devo-collector/config
      - ./credentials:/devo-collector/credentials
      - ./state:/devo-collector/state
    environment:
      - CONFIG_FILE=${CONFIG_FILE:-config.yaml}

To run the container using docker-compose, execute the following command from the <any_directory>/devo-collectors/<product_name>/ directory:

Code Block
IMAGE_VERSION=<version> docker-compose up -d

Note
Replace `<product_name>`, `<image_name>` and `<version>` with the proper values.

Rw tab

title	Cloud collector

We use a piece of software called Collector Server to host and manage all our available collectors. If you want us to host this collector for you, get in touch with us and we will guide you through the configuration.

Collector services detail

This section is intended to explain how to proceed with specific actions for services.

Expand

title	Browser and email isolation

Internal process and deduplication method

Proofpoint Isolation API stores events up to 30 days in the past. All isolation events are fetched on a polling basis. If there are more events available for a given time period than can be retrieved in a single page (limited to 10,000 records per page), the collector continues to fetch new events until none are available for the query window.

Events are sorted by the date field and deduplicated by comparing the hash signature of the event against previous pulls.

Devo categorization and destination

All events of this service are ingested into the table tap.proofpoint.isolation.url_isolation

Setup output

A successful run has the following output messages for the setup module:

Code Block

2023-04-03T16:18:50.783    INFO InputProcess::MainThread -> IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Starting thread
2023-04-03T16:18:50.784 WARNING InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> The token/header/authentication has not been created yet
2023-04-03T16:18:50.785    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Making sample request to test authentication.
2023-04-03T16:18:50.792    INFO InputProcess::MainThread -> IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Starting thread
2023-04-03T16:18:50.792    INFO InputProcess::MainThread -> IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) - Starting thread
2023-04-03T16:18:50.792 WARNING InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Waiting until setup will be executed
2023-04-03T16:18:50.793 WARNING InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> The token/header/authentication has not been created yet
2023-04-03T16:18:51.509    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Setup for module <IsolationPuller> has been successfully executed
2023-04-03T16:18:51.510    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Making sample request to test authentication.
2023-04-03T16
2023-04-03T16:20:12.074    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Authentication successful.
2023-04-03T16:18:52.096    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Setup for module <IsolationPuller> has been successfully executed

Puller output

Code Block

2023-05-16T23:02:54.695    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) Starting the execution of pre_pull()
2023-05-16T23:02:54.696    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Reading persisted data
2023-05-16T23:02:54.698    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Data retrieved from the persistence: {'start_time_in_utc': '2023-05-16T00:00:00.000000Z', 'last_event_time_in_utc': '2023-05-17T03:01:40.121516Z', 'last_ids': ['57bddd353b7cc010ab4a696cf86d4c18e97aafbdc49a52498bddc756de044c9f', '57bddd353b7cc010ab4a696cf86d4c18e97aafbdc49a52498bddc756de044c9f'], '@persistence_version': 1}
2023-05-16T23:02:54.699    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Running the persistence upgrade steps
2023-05-16T23:02:54.700    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Running the persistence corrections steps
2023-05-16T23:02:54.700    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Running the persistence corrections steps
2023-05-16T23:02:54.701    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> No changes were detected in the persistence
2023-05-16T23:02:54.702    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) Finalizing the execution of pre_pull()
2023-05-16T23:02:54.702    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Starting data collection every 60 seconds
2023-05-16T23:02:54.702    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Pull Started
2023-05-16T23:02:54.702    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Fetching all url_isolation event(s) from 2023-05-17T03:01:40.121516Z to 2023-05-17T03:02:54.695673Z.
2023-05-16T23:02:55.648    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Updating the persistence
2023-05-16T23:02:55.650    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> (Partial) Statistics for this pull cycle (@devo_pulling_id=1684292574695):Number of requests made: 1; Number of events received: 0; Number of duplicated events filtered out: 0; Number of events generated and sent: 0; Average of events per second: 0.000.

After a successful collector’s execution (that is, no error logs found), you will see the following log message:

Code Block
2023-04-03T16:20:41.575 INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> The data is up to date!

Expand

title	URL isolation

title

Internal process and deduplication method

Proofpoint Isolation API stores events up to 30 days in the past. All isolation events are fetched on a polling basis. If there are more events available for a given time period than can be retrieved in a single page (limited to 10,000 records per page), the collector continues to fetch new events until none are available for the query window.

Events are sorted by the date field and deduplicated by comparing the hash signature of the event against previous pulls.

Devo categorization and destination

All events of this service are ingested into the table tap.proofpoint.isolation.url_isolation.

Setup output

A successful run has the following output messages for the setup module:

Code Block

2023-04-03T16:18:50.783    INFO InputProcess::MainThread -> IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Starting thread
2023-04-03T16:18:50.784 WARNING InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> The token/header/authentication has not been created yet
2023-04-03T16:18:50.785    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Making sample request to test authentication.
2023-04-03T16:18:50.792    INFO InputProcess::MainThread -> IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Starting thread
2023-04-03T16:18:50.792    INFO InputProcess::MainThread -> IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) - Starting thread
2023-04-03T16:18:50.792 WARNING InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Waiting until setup will be executed
2023-04-03T16:18:50.793 WARNING InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> The token/header/authentication has not been created yet
2023-04-03T16:18:51.509    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Setup for module <IsolationPuller> has been successfully executed
2023-04-03T16:18:51.510    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Making sample request to test authentication.
2023-04-03T16
2023-04-03T16:20:12.074    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Authentication successful.
2023-04-03T16:18:52.096    INFO InputProcess::IsolationPullerSetup(unknown,proofpoint_isolation#10001,url_isolation#predefined) -> Setup for module <IsolationPuller> has been successfully executed

Puller output

Code Block

2023-05-16T23:02:54.695    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) Starting the execution of pre_pull()
2023-05-16T23:02:54.696    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Reading persisted data
2023-05-16T23:02:54.698    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Data retrieved from the persistence: {'start_time_in_utc': '2023-05-16T00:00:00.000000Z', 'last_event_time_in_utc': '2023-05-17T03:01:40.121516Z', 'last_ids': ['57bddd353b7cc010ab4a696cf86d4c18e97aafbdc49a52498bddc756de044c9f', '57bddd353b7cc010ab4a696cf86d4c18e97aafbdc49a52498bddc756de044c9f'], '@persistence_version': 1}
2023-05-16T23:02:54.699    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Running the persistence upgrade steps
2023-05-16T23:02:54.700    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Running the persistence corrections steps
2023-05-16T23:02:54.700    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Running the persistence corrections steps
2023-05-16T23:02:54.701    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> No changes were detected in the persistence
2023-05-16T23:02:54.702    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) Finalizing the execution of pre_pull()
2023-05-16T23:02:54.702    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Starting data collection every 60 seconds
2023-05-16T23:02:54.702    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Pull Started
2023-05-16T23:02:54.702    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Fetching all url_isolation event(s) from 2023-05-17T03:01:40.121516Z to 2023-05-17T03:02:54.695673Z.
2023-05-16T23:02:55.648    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> Updating the persistence
2023-05-16T23:02:55.650    INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> (Partial) Statistics for this pull cycle (@devo_pulling_id=1684292574695):Number of requests made: 1; Number of events received: 0; Number of duplicated events filtered out: 0; Number of events generated and sent: 0; Average of events per second: 0.000.

After a successful collector’s execution (that is, no error logs were found), you should be able to see the following log message:

Code Block
2023-04-03T16:20:41.575 INFO InputProcess::IsolationPuller(proofpoint_isolation,10001,url_isolation,predefined) -> The data is up to date!

Expand

Restart the persistence

To restart the service, the user must reconfigure the start_time_in_utc parameter within the configuration file. When the collector is restarted, the system will register the new start time and begin pulling events from that date.

Expand

title	Troubleshooting

This collector has different security layers that detect both an invalid configuration and abnormal operation. This table will help you detect and resolve the most common errors.

Error Type	Error Id	Error Message	Cause	Solution
ApiError	403	API Key XXXXXX is not valid.	Invalid API key	The key is not valid. Please create a new one through the Isolation system.

Collector operations

This section is intended to explain how to proceed with specific operations of this collector.

Expand

title	Verify collector operations

Initialization

The initialization module is in charge of setup and running the input (pulling logic) and output (delivering logic) services and validating the given configuration.

A successful run has the following output messages for the initializer module:

Code Block

2023-01-10T15:22:57.146    INFO MainProcess::MainThread -> Loading configuration using the following files: {"full_config": "config.yaml", "job_config_loc": null, "collector_config_loc": null}
2023-01-10T15:22:57.146    INFO MainProcess::MainThread -> Using the default location for "job_config_loc" file: "/etc/devo/job/job_config.json"
2023-01-10T15:22:57.147    INFO MainProcess::MainThread -> "\etc\devo\job" does not exists
2023-01-10T15:22:57.147    INFO MainProcess::MainThread -> Using the default location for "collector_config_loc" file: "/etc/devo/collector/collector_config.json"
2023-01-10T15:22:57.148    INFO MainProcess::MainThread -> "\etc\devo\collector" does not exists
2023-01-10T15:22:57.148    INFO MainProcess::MainThread -> Results of validation of config files parameters: {"config": "config.yaml", "config_validated": True, "job_config_loc": "/etc/devo/job/job_config.json", "job_config_loc_default": True, "job_config_loc_validated": False, "collector_config_loc": "/etc/devo/collector/collector_config.json", "collector_config_loc_default": True, "collector_config_loc_validated": False}
2023-01-10T15:22:57.171 WARNING MainProcess::MainThread -> [WARNING] Illegal global setting has been ignored -> multiprocessing: False

Events delivery and Devo ingestion

The event delivery module is in charge of receiving the events from the internal queues where all events are injected by the pullers and delivering them using the selected compatible delivery method.

A successful run has the following output messages for the initializer module:

Code Block

2023-01-10T15:23:00.788    INFO OutputProcess::MainThread -> DevoSender(standard_senders,devo_sender_0) -> Starting thread
2023-01-10T15:23:00.789    INFO OutputProcess::MainThread -> DevoSenderManagerMonitor(standard_senders,devo_1) -> Starting thread (every 300 seconds)
2023-01-10T15:23:00.790    INFO OutputProcess::MainThread -> DevoSenderManager(standard_senders,manager,devo_1) -> Starting thread
2023-01-10T15:23:00.842    INFO OutputProcess::MainThread -> global_status: {"output_process": {"process_id": 18804, "process_status": "running", "thread_counter": 21, "thread_names": ["MainThread", "pydevd.Writer", "pydevd.Reader", "pydevd.CommandThread", "pydevd.CheckAliveThread", "DevoSender(standard_senders,devo_sender_0)", "DevoSenderManagerMonitor(standard_senders,devo_1)", "DevoSenderManager(standard_senders,manager,devo_1)", "OutputStandardConsumer(standard_senders_consumer_0)",

Sender services

The Integrations Factory Collector SDK has 3 different senders services depending on the event type to delivery (internal, standard, and lookup). This collector uses the following Sender Services:

Sender services	Description
`internal_senders`	In charge of delivering internal metrics to Devo such as logging traces or metrics.
`standard_senders`	In charge of delivering pulled events to Devo.

Sender statistics

Each service displays its own performance statistics that allow checking how many events have been delivered to Devo by type:

Logging trace

Description

Number of available senders: 1

Displays the number of concurrent senders available for the given Sender Service.

sender manager internal queue size: 0

Displays the items available in the internal sender queue.

Standard - Total number of messages sent: 57, messages sent since "2023-01-10 16:09:16.116750+00:00": 0 (elapsed 0.000 seconds

Displays the number of events from the last time and following the given example, the following conclusions can be obtained:

44 events were sent to Devo since the collector started.
The last checkpoint timestamp was 2023-01-10 16:09:16.116750+00:00.
21 events where sent to Devo between the last UTC checkpoint and now.
Those 21 events required 0.007 seconds to be delivered.

Expand

title	Check memory usage

To check the memory usage of this collector, look for the following log records in the collector which are displayed every 5 minutes by default, always after running the memory-free process.

The used memory is displayed by running processes and the sum of both values will give the total used memory for the collector.
The global pressure of the available memory is displayed in the global value.
All metrics (Global, RSS, VMS) include the value before freeing and after previous -> after freeing memory

Code Block

INFO InputProcess::MainThread -> [GC] global: 20.4% -> 20.4%, process: RSS(34.50MiB -> 34.08MiB), VMS(410.52MiB -> 410.02MiB)
INFO OutputProcess::MainThread -> [GC] global: 20.4% -> 20.4%, process: RSS(28.41MiB -> 28.41MiB), VMS(705.28MiB -> 705.28MiB)

Change log for v1.x.x

...

Release

...

Released on

...

Release type

...

Details

...

705.28MiB)

Change log

Release

Released on

Release type

Details

Recommendations

v1.1.1

26 Sep 2023

Status

colour	Red
title	bug fixing

Bug fixing

Controlled range values in user schemas for variable override_query_window_offset_in_minutes

Update

v1.1.0

22 Sep 2023

Status

colour	Yellow
title	NEW FEATURE

New feature

Added new variable override_query_window_offset_in_minutes to ensure the events are fully recorded in the API before we try to fetch them

Improvements

Upgraded DCSDK and internal modules to the latest version

Update

v1.0.0

01 Feb 2023

20 Mar 2022

Status

colour	Green
title	INITIAL RELEASE

Initial release

-

Versions Compared

Old Version 1

New Version Current

Key

Overview

Configuration requirements

Devo collector features

Data sources

Vendor setup

Minimum configuration required for basic pulling

Steps

Assigning necessary permissions

Run the collector

Structure

Devo credentials

Editing the config.yaml file

Download the Docker image

Docker

Docker Compose

Collector services detail

Internal process and deduplication method

Devo categorization and destination

Setup output

Puller output

Internal process and deduplication method

Devo categorization and destination

Setup output

Puller output

Restart the persistence

Collector operations

Initialization

Events delivery and Devo ingestion

Sender services

Sender statistics

Change log for v1.x.x

Change log