--- title: "Cohesity collector" canonical: "https://docs.devo.com/space/latest/676233217/Cohesity%20collector" format: markdown --- > Macro (toc) ## Overview Cohesity gives you both data security and data management. Defend against ransomware with immutable backup, AI-based early threat detection, and rapid data. The Cohesity Helios API is lazy, so the collector will have to observe a lookback window to ensure that the least amount of events are lost. To define this window the collector has 2 parameters: - `lookback`: This is the amount of time to look back and extract data. - `lookback_width`: The width of the slot to extract data from the look-back parameter. If not defined, the collector will default to `1h` for the lookback and `5m` for the lookback width. This means that every time the request period is reached the collector will look back at the last 1 hour and pull all events that have occurred in that 5-minute time frame. These are reasonable defaults, but you can adjust them to your needs. > ⚠️ **Important**: The `lookback_width` parameter must be the same as the `request_period_in_seconds` parameter. If not, events will get lost or be duplicated. ## 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** | **API endpoint** | **Collector service name** | **Devo table** | | --- | --- | --- | --- | | Helios Audit | `/v2/mcm/audit-logs` | `audit` | `dmp.cohesity.helios.audit` | | Helios Alert | `/v2/mcm/alerts` | `alerts` | `dmp.cohesity.helios.alerts` | For more information on how the events are parsed, [visit our page](https://devodocs.atlassian.net/wiki/spaces/latest/pages/596705284). ## Flattening preprocessing The audit logs have flattening enabled. If a record has several records, the new records will be extracted and partially applied to the original log. For example: ```json {"a": 1, "b": 2, "c": [{"name": "john"},{"name": "scott"}]} ``` The flattening process will be applied and you'll get the additional logs such as: ```json {"a": 1, "b": 2, "newRecord": [{"name": "john"}]} {"a": 1, "b": 2, "newRecord": [{"name": "scott"}]} ``` ## Source Event Obfuscation There is no default source obfuscation for this collector. ## Minimum configuration required for basic pulling Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below. > ℹ️ 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_name` | The name of the API given in setup. | | `api_key` | The key generated in setup. | ## Accepted authentication methods | **Authentication method** | **api_key_name** | **api_key** | | --- | --- | --- | | OAuth2 | [REQUIRED] | [REQUIRED] | ## Vendor setup Follow these steps to get the required credentials: > Macro (rw-ui-steps-macro) > > > Macro (rw-step) > > Log in to Helios using your username and password. > > ![image-20240620-105040.png](media://a5493d8e-4e7d-4369-be6c-8682e2656d08) > > > Macro (rw-step) > > Click the **Settings** icon at the top right corner and select **Access Management**. > > ![image-20240620-105255.png](media://100be09b-8ace-4b4a-bd24-b738335c737e) > > > Macro (rw-step) > > From the available tabs, select **API Keys**. > > ![image-20240620-105351.png](media://a676e18e-0f9c-4824-894b-795e2c8cc5b2) > > > Macro (rw-step) > > Click the **Add API Key** button. > > ![image-20240620-105444.png](media://45f39403-b46f-4066-a4e1-72b385585071) > > > Macro (rw-step) > > Give the API key a name and click the **Save** button. > > ![image-20240620-105524.png](media://bf278974-fa71-430f-96ce-983a40cccb4b) > > Note that once you navigate to a different page from this page, you won't be able to view the **apiKey** again, so copy and save it. > > > Macro (rw-step) > > Copy the key and API name, those are the credentials needed. > > ![image-20240620-105622.png](media://2a7b1a37-568b-484f-867f-17f17b535021) ## 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). > Macro (rw-ui-tabs-macro) > > > Macro (rw-tab) > > ```json > { > "global_overrides": { > "debug": false > }, > "inputs": { > "cohesity": { > "id": "", > "enabled": true, > "credentials": { > "api_key_name": "", > "api_key": "" > }, > "services": { > "audit": { > "lookback": "", > "lookback_width": "", > "request_period_in_seconds": > }, > "alerts": { > "lookback": "", > "lookback_width": "", > "request_period_in_seconds": > } > } > } > } > } > ``` > > The following table outlines the parameters available for configuring the collector. Each parameter is categorized by its necessity (mandatory or optional), data type, acceptable values or formats, and a brief description. > > | **Parameter** | **Data type** | **Requirement** | **Value range / Format** | **Description** | > | --- | --- | --- | --- | --- | > | `short_unique_id` | `str` | Mandatory | Min length: 1, Max length: 5 | Short, unique ID for input service, used in persistence addressing. Avoid duplicates to prevent collisions. | > | `api_key_name` | `str` | Mandatory | Min length: 1 | Api Key Name | > | `api_key` | `str` | Mandatory | Min length: 1 | Api Key | > | `lookback_value` | `str` | Optional | Min length: 1 | Amount of time to look back and extract data. This is usually seconds, but can be a specific time like `1h`, `30m`, etc. If not specified, by default its value is `1h`. | > | `lookback_width_value` | `str` | Optional | Min length: 1 | The width of the slot to extract data from the look-back parameter. This is usually seconds, but can be a specific time like `1h`, `30m`, etc. If specified, set the same amount as `request_period_in_seconds_value`, or events will get lost or be duplicated. If not specified, by default its value is `5m`. | > | `request_period_in_seconds_value` | `int` | Optional | Min: 60 | Custom period in seconds between data pulls, overriding default (180s). | > > > ℹ️ Parameters marked as "Mandatory" are required for the collector's configuration. Optional parameters can be omitted or removed if not used, but they provide additional customization and control over the collector's behavior. > > > Macro (rw-tab) > > 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: > > ``` > > └── devo-collectors/ > └── / > ├── certs/ > │ ├── chain.crt > │ ├── .key > │ └── .crt > ├── state/ > └── config/ > └── config.yaml > ``` > > > ⚠️ Replace `` with the proper value. > > ### Devo credentials > > To send data securely to the Devo platform, you will need to download X.509 Certificates from your Devo Domain: > > 1. Login to your Devo tenant. > 2. On the left menu, click on **Administration**, click on **Credentials**, then **X.509 Certificates**. > 3. Download your Certificate by clicking on **Certificate**. > 4. Download your Private Key by clicking on **Private Key**. > 5. Download your Chain CA by clicking on **Chain CA.** > 6. Move the downloaded files to `/certs/` folder. > > ![image-20240613-130355.png](media://8e0dd03d-904d-4fc0-94c8-4020b8deabfc) > > For more information about how to get the Devo certificates, please visit [Devo Docs](https://docs.devo.com/space/latest/94763741/X.509+certificates). > > > ⚠️ Replace `` with the proper value. > > ### Editing the config.yaml file > > ```yaml > globals: > debug: false > id: not_used > name: cohesity > persistence: > type: filesystem > config: > directory_name: state > > outputs: > devo_1: > type: devo_platform > config: > address: > port: 443 > type: SSL > chain: > cert: > key: > > inputs: > cohesity: > id: > enabled: true > credentials: > api_key_name: > api_key: > services: > audit: > lookback: > lookback_width: > request_period_in_seconds: > alerts: > lookback: > lookback_width: > request_period_in_seconds: > ``` > > > ℹ️ 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. > > The following table outlines the parameters available for configuring the collector. Each parameter is categorized by its necessity (mandatory or optional), data type, acceptable values or formats, and a brief description. Replace the placeholders with your required values following the description table below: > > | | | | | | > | --- | --- | --- | --- | --- | > | **Parameter** | **Data type** | **Requirement** | **Value range / Format** | **Description** | > | `collector_id_value` | `str` | Mandatory | Min length: 1, Max length: 5 | Unique identifier for the collector. | > | `collector_name_value` | `str` | Mandatory | Min length: 1, Max length: 10 | Name assigned to the collector. | > | `devo_address` | `str` | Mandatory | One of: `collector-us.devo.io`, `collector-eu.devo.io` | Devo Cloud destination for events. | > | `chain_filename` | `str` | Mandatory | Min length: 4, Max length: 20 | Filename of the `chain.crt` file from your Devo domain. | > | `cert_filename` | `str` | Mandatory | Min length: 4, Max length: 20 | Filename of the `file.cert` from your Devo domain. | > | `key_filename` | `str` | Mandatory | Min length: 4, Max length: 20 | Filename of the `file.key` from your Devo domain. | > | `short_unique_id` | `str` | Mandatory | Min length: 1, Max length: 5 | Short, unique ID for input service, used in persistence addressing. Avoid duplicates to prevent collisions. | > | `api_key_name` | `str` | Mandatory | Min length: 1 | Api Key Name | > | `api_key` | `str` | Mandatory | Min length: 1 | Api Key | > | `lookback_value` | `str` | Optional | Min length: 1 | Amount of time to look back and extract data. This is usually seconds, but can be a specific time like `1h`, `30m`, etc. If not specified, by default its value is `1h`. | > | `lookback_width_value` | `str` | Optional | Min length: 1 | The width of the slot to extract data from the look-back parameter. This is usually seconds, but can be a specific time like `1h`, `30m`, etc. If specified, set the same amount as `request_period_in_seconds_value`, or events will get lost or be duplicated. If not specified, by default its value is `5m`. | > | `request_period_in_seconds_value` | `int` | Optional | Min: 60 | Custom period in seconds between data pulls, overriding default (300s). | > > > ℹ️ Parameters marked as "Mandatory" are required for the collector's configuration. Optional parameters can be omitted or removed if not used, but they provide additional customization and control over the collector's behavior. > > ### 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-cohesity_helios_if-docker-image-1.2.0](https://drive.google.com/file/d/1mNZSkJeS3PSKegculGhUeeyxTAUYC-Tc/view?usp=drive_link) | `40cd6b4439045881d75674bd34c5b496e39a218bdb5eb8df51752ab48849d14c` | > > Use the following command to add the Docker image to the system: > > ``` > gunzip -c -.tgz | docker load > ``` > > > ⚠️ Once the Docker image is imported, it will show the real name of the Docker image (including version info). Replace `` and `` with a proper value. > > The Docker image can be deployed on the following services: > > #### Docker > > Execute the following command on the root directory `/devo-collectors//` > > ``` > docker run > --name collector- > --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 > : > ``` > > > ⚠️ Replace ``, `` and `` 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 `/devo-collectors//` directory. > > ``` > version: '3' > services: > collector-: > image: :${IMAGE_VERSION:-latest} > container_name: collector- > 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 `/devo-collectors//` directory: > > ``` > IMAGE_VERSION= docker-compose up -d > ``` > > > ⚠️ Replace ``, `` and `` with the proper values. ## Collector services detail This section is intended to explain how to proceed with specific actions for services. ### Alerts (`alerts`) #### Internal process and deduplication method All alerts data are pulled with an Id value. The collector checks the Ids each run. Checkpoints are persisted to ensure that duplicate data is not sent to Devo. #### Devo categorization and destination All events of this service are ingested into the table `dmp.cohesity.helios.alerts`. #### Setup output ``` 2024-04-09T09:56:19.561389088Z 2024-04-09T09:56:19.561 WARNING InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,alerts#predefined) -> Testing fetch from /mcm/alerts. 2024-04-09T09:56:19.771898077Z 2024-04-09T09:56:19.771 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Number of available senders: 1, sender manager internal queue size: 0 2024-04-09T09:56:19.772167710Z 2024-04-09T09:56:19.771 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Number of available senders: 1, sender manager internal queue size: 0 2024-04-09T09:56:19.772327665Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> enqueued_elapsed_times_in_seconds_stats: {} 2024-04-09T09:56:19.772395427Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> enqueued_elapsed_times_in_seconds_stats: {} 2024-04-09T09:56:19.772425735Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Sender: DevoSender(internal_senders,devo_sender_0), status: {"internal_queue_size": 0, "is_connection_open": True} 2024-04-09T09:56:19.772519048Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Sender: DevoSender(lookup_senders,devo_sender_0), status: {"internal_queue_size": 0, "is_connection_open": False} 2024-04-09T09:56:19.772601144Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Internal - Total number of messages: 6333 messages/bytes sent since/to "2024-04-09T09:51:19.771169+00:00/2024-04-09T09:56:19.772408+00:00": 25/13762, (elapsed 0.052 seconds) 2024-04-09T09:56:19.772631900Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Lookup - Total number of messages sent: 0, messages sent since "2024-04-09 09:51:19.770969+00:00": 0 (elapsed 0.000 seconds) 2024-04-09T09:56:20.261298432Z 2024-04-09T09:56:20.261 INFO InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,alerts#predefined) -> Successfully tested fetch from /mcm/alerts. Source is pullable. 2024-04-09T09:56:20.262730750Z 2024-04-09T09:56:20.262 INFO InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,alerts#predefined) -> Setup for module has been successfully executed ``` #### Puller output ``` 2024-04-09T09:56:22.704294203Z 2024-04-09T09:56:22.704 INFO InputProcess::CohesityPuller(cohesity,56752,alerts,predefined) -> Pull Started 2024-04-09T09:56:23.124016843Z 2024-04-09T09:56:23.123 INFO InputProcess::CohesityPuller(cohesity,56752,alerts,predefined) -> Updating the persistence 2024-04-09T09:56:23.124811682Z 2024-04-09T09:56:23.124 INFO InputProcess::CohesityPuller(cohesity,56752,alerts,predefined) -> (Partial) Statistics for this pull cycle (@devo_pulling_id=1712656582704):Number of requests made: 535; Number of events received: 2; Number of duplicated events filtered out: 0; Number of events generated and sent: 2; Average of events per second: 4.759. ``` #### Restart the persistence Update the unique ID of the collector and restart, this will remove the Id values that have been pulled. This may cause duplicates. ### Audit (`audit`) #### Internal process and deduplication method Audit logs are pulled with a start time value, that value is updated anytime logs are found. If no logs are found the start time is not persisted. The start time will be used until logs are found. #### Devo categorization and destination All events of this service are ingested into the table `dmp.cohesity.helios.audit`. #### Setup output ``` 2024-04-09T09:56:19.561389088Z 2024-04-09T09:56:19.561 WARNING InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,audit#predefined) -> Testing fetch from /mcm/get-audit. 2024-04-09T09:56:19.771898077Z 2024-04-09T09:56:19.771 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Number of available senders: 1, sender manager internal queue size: 0 2024-04-09T09:56:19.772167710Z 2024-04-09T09:56:19.771 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Number of available senders: 1, sender manager internal queue size: 0 2024-04-09T09:56:19.772327665Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> enqueued_elapsed_times_in_seconds_stats: {} 2024-04-09T09:56:19.772395427Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> enqueued_elapsed_times_in_seconds_stats: {} 2024-04-09T09:56:19.772425735Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Sender: DevoSender(internal_senders,devo_sender_0), status: {"internal_queue_size": 0, "is_connection_open": True} 2024-04-09T09:56:19.772519048Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Sender: DevoSender(lookup_senders,devo_sender_0), status: {"internal_queue_size": 0, "is_connection_open": False} 2024-04-09T09:56:19.772601144Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(internal_senders,relay_0) -> Internal - Total number of messages: 6333 messages/bytes sent since/to "2024-04-09T09:51:19.771169+00:00/2024-04-09T09:56:19.772408+00:00": 25/13762, (elapsed 0.052 seconds) 2024-04-09T09:56:19.772631900Z 2024-04-09T09:56:19.772 INFO OutputProcess::DevoSenderManagerMonitor(lookup_senders,relay_0) -> Lookup - Total number of messages sent: 0, messages sent since "2024-04-09 09:51:19.770969+00:00": 0 (elapsed 0.000 seconds) 2024-04-09T09:56:20.261298432Z 2024-04-09T09:56:20.261 INFO InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,audit#predefined) -> Successfully tested fetch from /mcm/get-audit. Source is pullable. 2024-04-09T09:56:20.262730750Z 2024-04-09T09:56:20.262 INFO InputProcess::CohesityPullerSetup(cohesity,cohesity#56752,audit#predefined) -> Setup for module has been successfully executed ``` #### Puller output ``` 2024-04-09T09:56:22.704294203Z 2024-04-09T09:56:22.704 INFO InputProcess::CohesityPuller(cohesity,56752,audit,predefined) -> Pull Started 2024-04-09T09:56:23.124016843Z 2024-04-09T09:56:23.123 INFO InputProcess::CohesityPuller(cohesity,56752,audit,predefined) -> Updating the persistence 2024-04-09T09:56:23.124811682Z 2024-04-09T09:56:23.124 INFO InputProcess::CohesityPuller(cohesity,56752,audit,predefined) -> (Partial) Statistics for this pull cycle (@devo_pulling_id=1712656582704):Number of requests made: 535; Number of events received: 2; Number of duplicated events filtered out: 0; Number of events generated and sent: 2; Average of events per second: 4.759. ``` #### Restart the persistence Update the unique Id of the collector and restart, this will remove the Id values that have been pulled. This may cause duplicates. ### 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. #### Common logic | **Error Type** | **Error Id** | **Error Message** | **Cause** | **Solution** | | --- | --- | --- | --- | --- | | InitVariablesError | 1 | "lookback" parameter must be a valid time string. | The parameter has an unexpected type. | Review the configuration and ensure it is a string. | | InitVariablesError | 2 | "lookback_width" parameter must be a valid time string. | The parameter has an unexpected type. | Review the configuration and ensure it is a string. | | InitVariablesError | 3 | "lookback_width" is greater than "lookback" | The parameter has an invalid value. | Ensure the value is less than "lookback". | | InitVariablesError | 4 | "lookback_width" must be the same as the "request_period_in_seconds" parameter | The parameter is not the same as "request_period_in_seconds". | Ensure both values are the same. | | ApiError | 496 | Connection Error - Ensure the URL parameters are correct and the that host has access to the server. | Could not connect to the Host | Ensure the endpoint is reachable with the credentials | | ApiError | 497 | Max Retries Error - Request attempts with {retries} retries failed. \n{reason} | Max Retries Hit | Update rate limits | | SetUpError | 102 | Failed to fetch from {endpoint}. Error: {e} | The collector was unable to access the specified endpoint. | Ensure the endpoint is reachable with the credentials | ## Collector operations This section is intended to explain how to proceed with specific operations of this collector.
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: ``` 2023-01-10T15:22:57.146 INFO MainProcess::MainThread -> Loading configuration using the following files: {"full_config": "config-test-local.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": "C:\git\collectors2\devo-collector-\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: ``` 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.
> ℹ️ This value helps detect bottlenecks and needs to increase the performance of data delivery to Devo. This last can be made by increasing the concurrent senders. | | `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.00 seconds` to be delivered. |
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` ``` 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 | Release | Released on | Release type | Details | Recommended actions | | --- | --- | --- | --- | --- | | `v1.2.0` | 11/14/2024 | [Improvement] | | Recommended version | | `v1.1.0` | 10/14/2024 | [Improvement]
[bug fixing] | | Upgrade | | `v1.0.0` | 4/9/2024 | [INITIAL RELEASE] | | - |