---
title: "SpyCloud collector"
canonical: "https://docs.devo.com/space/latest/273186817/SpyCloud%20collector"
format: markdown
---
> Macro (toc)

## Overview

The** SpyCloud collector** can help fraud prevention teams stay ahead of customer ATO fraud by detecting and resetting exposed consumer passwords early in the breach lifecycle, heading off account takeover attempts.

## 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` | SpyCloud API key. You can access your API key(s)  
securely in your Customer Portal account. Your API keys carry many privileges, so be sure to keep them secret. Please do not share your API keys in any publicly accessible areas such as source code  
repositories, client-side web application code, etc. |

> ℹ️ See the **[Accepted authentication methods](#Accepted-authentication-methods)**[ ](#)section to verify what settings are required based on the desired authentication method.

## Devo collector features

| **Feature** | **Details** |
| --- | --- |
| Allow parallel downloading (`multipod`) | `Allowed` |
| Running environments | `Collector server`<br>`On-premise` |
| Populated Devo events | `Table` |
| Flattening preprocessing | `No` |

## Data sources

| **Data source** | **Description** | **API endpoint** | **Collector service name** | **Devo table** | **Available from release** |
| --- | --- | --- | --- | --- | --- |
| Watchlist | Watchlist assets extracted from breach data | `/enterprise-v1/breach/data/watchlist` | `watchlist` | `ofd.spycloud.ato_prevention.watchlist` | v1.0 |

## Vendor setup

1. **Configure domains**: Add all appropriate domains and subdomains owned by your company to the watchlist - you must own your domain to add it-.
2. **Configure emails**: Add all the personal email addresses of key employees and executives to the Personal email watchlist. The owner of the email will receive a verification message. Once the owner of the mailbox clicks the verification button in the message, the email address will be immediately added to monitor it.
3. **Configure IPs**: Add the IP address ranges that your company uses to the watchlist.
4. **Whitelist the Devo collector IP**:
  1. Request that your Devo account manager or support provide you with the IP of your Devo collector.
  2. Once you know the IP, request that SpyCloud add your IP to the whitelist in the API section.
  3. Obtain your SpyCloud API key from the API page.
5. **Generate sample events**:
  1. Insert `example.net` into the domains watchlist.
  2. Insert `192.168.1.0` into the IP watchlist.
  3. Wait for the SpyCloud platform to correlate watchlist entries with the collections dataset to create incidents.

> Macro (anchor)

 

## Accepted authentication methods

|  |  |
| --- | --- |
| **Authentication method** | **API key** |
| API key | [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 (<u>Cloud collector</u>), or deploy and host the collector in your own machine using a Docker image (<u>On-premise collector</u>).

> Macro (rw-ui-tabs-macro)
> 
> > Macro (rw-tab)
> 
> 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](https://devo.my.site.com/support/login?ec=302&startURL=%2Fsupport%2Fs%2F) and we will guide you through the configuration.
> 
> > 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:
> 
> ```
> <any_directory>
> └── devo-collectors/
>     └── <product_name>/
>         ├── certs/
>         │   ├── chain.crt
>         │   ├── <your_domain>.key
>         │   └── <your_domain>.crt
>         ├── state/
>         └── config/ 
>             └── config.yaml 
> ```
> 
> > ⚠️ 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](media://164ae194-9126-401d-919a-958d480267e3)
> 
> > ⚠️ Replace `<product_name>` with the proper value.
> 
> ### Editing the config.yaml file
> 
> ```
> globals:
>   debug: <debug_status>
>   id: <collector_id>
>   name: <collector_name>
>   persistence:
>     type: filesystem
>     config:
>       directory_name: state
> outputs:
>   devo_1:
>     type: devo_platform
>     config:
>       address: <devo_address>
>       port: 443
>       type: SSL
>       chain: <chain_filename>
>       cert: <cert_filename>
>       key: <key_filename>
> inputs:
>   spycloud:
>     id: <input_id>
>     enabled: <input_status>
>     credentials:
>       api_key: <api_key>
>     services:
>       watchlist:
>         tag: <tag>
>         initial_start_time_in_utc: <initial_start_time_in_utc>
> ```
> 
> > ℹ️ 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. |
> | `collector_id` | int | mandatory | minimum length: 1<br>maximum length: 5 | Use this parameter to give a unique ID to this collector. |
> | `collector_name` | str | mandatory | minimum length: 1<br>maximum length: 10 | Use this parameter to give a valid name to this collector. |
> | `devo_address` | str | mandatory | `collector-us.devo.io `<br>`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<br>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<br>maximum length: 20 | Use this parameter to identify the file.cert downloaded from your Devo domain. |
> | `key_filename` | str | mandatory | minimum length: 4<br>maximum length: 20 | Use this parameter to identify the file.key downloaded from your Devo domain. |
> | `input_id` | str | mandatory | minimum length: 1<br>maximum length: 20 | Use this parameter to give a unique ID to this input service.<br>This parameter is used to build the persistence address; do not use the same value for multiple collectors. It could cause a collision. |
> | `input_status` | bool | mandatory | true / false | Use this parameter to enable or disable the given input logic when running the collector. If the value is `true`, the input will be run. If the value is `false`, it will be ignored. |
> | `api_key` | str | mandatory |  | The API key obtained from SpyCloud portal. |
> | `tag` | str | optional | Devo tag-friendly string (no special characters, spaces, etc.) | An optional tag that allows users to override the service default tags. |
> | `initial_start_time_in_utc` | str | optional | UTC datetime string | 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.<br>Please note that setting the `initial_start_time_in_utc` for a particular service will override any `initial_start_time_in_utc` set in the commons level.<br>This parameter should be removed if it is not used. |
> 
> ### 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-spycloud_if-docker-image-1.2.0.tgz](https://drive.google.com/file/d/1TjwtWhQq27DpxHBYBnwGa0DxHrwW90c0/view?usp=drive_link) | `e477df388be0c767690d03f1fbfa90ceb841cacd4d9f5f81096f110a1318922d` |
> 
> Use the following command to add the Docker image to the system:
> 
> ```
> gunzip -c <image_file>-<version>.tgz | docker load
> ```
> 
> > ⚠️ 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>/`
> 
> ```
> 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>
> ```
> 
> > ⚠️ 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.
> 
> ```
> 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:
> 
> ```
> IMAGE_VERSION=<version> docker-compose up -d
> ```
> 
> > ⚠️ Replace `<product_name>`, `<image_name>` and `<version>` with the proper values.

## Collector services detail

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

### Events service

<details>
<summary>Watchlist</summary>

Watchlist events contain records extracted from breaches that correspond with your monitored IP, email address, and domain assets.

#### Internal process and deduplication method

Watchlist records are continuously fetched since the last known record time. Records are sorted by the `spycloud_publish_date`. The last known record time for a given batch of record(s) and the latest record hash(es) are persisted and referenced in the subsequent pull. Watchlist records are deduped by persisting the latest event object hashes from the previous run to ensure duplicate events are not inserted into Devo.

#### Devo categorization and destination

All events are sent by default to `my.app.spycloud.watchlist.`
</details>

<details>
<summary>Verify data collection</summary>

Once the collector has been launched, it is important to check if the ingestion is performed in a proper way. To do so, go to the collector’s logs console.

This service has the following components:

| **Component** | **Description** |
| --- | --- |
| Setup | The setup module is in charge of authenticating the service and managing the token expiration when needed. |
| Puller | The setup module is in charge of pulling the data in a organized way and delivering the events via SDK. |

#### Setup output

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

```
2023-02-01T18:57:33.935    INFO InputProcess::MainThread -> ServiceThread(spycloud,1,watchlist,predefined) - Starting thread (execution_period=60s)
2023-02-01T18:57:33.935    INFO InputProcess::MainThread -> SpyCloudWatchlistPullerSetup(unknown,spycloud#1,watchlist#predefined) -> Starting thread
2023-02-01T18:57:33.935    INFO InputProcess::MainThread -> SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) - Starting thread
2023-02-01T18:57:33.936 WARNING InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Waiting until setup will be executed
2023-02-01T18:57:33.936 WARNING InputProcess::SpyCloudWatchlistPullerSetup(unknown,spycloud#1,watchlist#predefined) -> The token/header/authentication has not been created yet
2023-02-01T18:57:34.635    INFO InputProcess::SpyCloudWatchlistPullerSetup(unknown,spycloud#1,watchlist#predefined) -> Successfully authenticated to SpyCloud API.
2023-02-01T18:57:34.636    INFO InputProcess::SpyCloudWatchlistPullerSetup(unknown,spycloud#1,watchlist#predefined) -> Setup for module <SpyCloudWatchlistPuller> has been successfully executed
```

#### Puller output

A successful initial run has the following output messages for the puller module:

> ℹ️ Note that the `PrePull` action is executed only one time before the first run of the `Pull` action.

```
2023-02-01T19:05:37.183    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) Starting the execution of pre_pull()
2023-02-01T19:05:37.184    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Reading persisted data
2023-02-01T19:05:37.184    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Data retrieved from the persistence: {'@persistence_version': 1, 'initial_start_time_in_utc': '2020-12-01T00:00:00Z', 'last_event_time_in_utc': '2023-02-03T00:04:36Z', 'last_ids': []}
2023-02-01T19:05:37.184    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Running the persistence upgrade steps
2023-02-01T19:05:37.184    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Running the persistence corrections steps
2023-02-01T19:05:37.184    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Running the persistence corrections steps
2023-02-01T19:05:37.185    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> No changes were detected in the persistence
2023-02-01T19:05:37.185    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) Finalizing the execution of pre_pull()
2023-02-01T19:05:37.185    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Starting data collection every 60 seconds
2023-02-01T19:05:37.185    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Pull Started
2023-02-01T19:05:37.186    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Retrieving/sending watchlist events having spycloud_publish_date between 2023-02-03T00:04:36+00:00 and 2023-02-02T00:05:37.183795+00:00
2023-02-01T19:05:37.188    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Updating the persistence
2023-02-01T19:05:37.188    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> (Partial) Statistics for this pull cycle (@devo_pulling_id=1675296337183):Number of requests made: 0; 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.
2023-02-01T19:05:37.188    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Statistics for this pull cycle (@devo_pulling_id=1675296337183):Number of requests made: 0; 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.
2023-02-01T19:05:37.189    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> The data is up to date!
2023-02-01T19:05:37.189    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Data collection completed. Elapsed time: 0.005 seconds. Waiting for 59.995 second(s) until the next one
```

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

```
2023-02-01T19:05:37.188    INFO InputProcess::SpyCloudWatchlistPuller(spycloud,1,watchlist,predefined) -> Statistics for this pull cycle (@devo_pulling_id=1675296337183):Number of requests made: 0; 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.
```

> ℹ️ The value `@devo_pulling_id` is injected in each event to group all events ingested by the same pull action. You can use it to get the exact events downloaded in that `Pull` action in Devo’s search window.
</details>

<details>
<summary>Restart the persistence</summary>

This collector uses persistent storage to download events in an orderly fashion and avoid duplicates. In case you want to re-ingest historical data or recreate the persistence, you can restart the persistence of this collector by following these steps:

1. Edit the configuration file.
2. Change the value of the `initial_start_time_in_utc` parameter to a different one.
3. Save the changes.
4. Restart the collector.

The collector will detect this change and will restart the persistence using the parameters of the configuration file or the default configuration in case it has not been provided.

> ⚠️ Note that this action clears the persistence and cannot be recovered in any way. Resetting persistence could result in duplicate or lost events.
</details>

<details>
<summary>Troubleshooting</summary>

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** |
| `InitVariableError` | xxx | JSON schema / validation message. | The provided configuration does not match the required schemas. | Update the indicated value in the error message. |
| `SetupError` | 100 | The remote data is not pullable with the given credentials. Check the error traces for details. | The credentials are incorrect or the Devo collector IP is not whitelisted. | Check that credentials are correct and that Devo collector IP is whitelisted. |
| `PrePullerror` | - | - | - | - |
| `PullError` | 300 | Received 403 Forbidden. Check that calling IP is whitelisted in SpyCloud. | The collector IP is not whitelisted. | Check that the collector IP is whitelisted. |
| `PullError` | 301 | Received 401 Unauthorized. Check that the API key is valid. | The API key does not have access to the watchlist data. | Check that credentials are  correct. |
| `PullError` | 302 | Received 429 Too Many Requests. Check that the monthly quota is not met. | SpyCloud is responding with 429 server messages even after attempting to retry the request. | Check that the monthly API quota is not met. Contact SpyCloud to adjust the API quota accordingly. |
| `PullError` | 303 | Received HTTP error | Generic HTTP error handler for all other server calls. | Review the error message to determine the issue. |
</details>

## Collector operations

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

<details>
<summary>Verify collector operations</summary>

### 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-josemi-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-trend-micro-vision-one\config\config-josemi-test-local.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)", 
```

> ℹ️ By default, these information traces will be displayed every 10 minutes.

#### 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:

| **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.<br>> ℹ️ 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. |
| `Standard - Total number of messages sent: 44, messages sent since ""2022-06-28 10:39:22.511671+00:00": 21 (elapsed 0.007 seconds)` | Displayes the number of events from the last time and following the given example, the following conclusions can be obtained:<br>- 44 events were sent to Devo since the collector started.
- The last checkpoint timestamp was `2022-06-28 10:39:22.511671+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.<br>> ℹ️ By default these traces will be shown every 10 minutes. |

#### 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.<br>> ℹ️ 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. |
| `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:<br>- 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.<br>Those 21 events required `0.00` seconds to be delivered.<br>> ℹ️ By default these traces will be shown every 10 minutes. |
</details>

<details>
<summary>Check memory usage</summary>

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)
```

> ℹ️ Differences between `RSS` and `VMS` memory usage:
> ℹ️ 
> ℹ️ - `RSS` is the Resident Set Size, which is the actual physical memory the process is using
> ℹ️ - `VMS` is the Virtual Memory Size which is the virtual memory that process is using
</details>

<details>
<summary>Enable/disable the logging debug mode</summary>

Sometimes it is necessary to activate the debug mode of the collector's logging. This debug mode increases the verbosity of the log and allows you to print execution traces that are very helpful in resolving incidents or detecting bottlenecks in heavy download processes.

- To enable this option you just need to edit the configuration file and change the debug_status parameter from false to true and restart the collector.
- To disable this option, you just need to update the configuration file and change the debug_status parameter from true to false and restart the collector.

For more information, visit the configuration and parameterization section corresponding to the chosen deployment mode.
</details>

## Change log

| **Release** | **Released on** | **Release type** | **Details** | **Recommendations** |
| --- | --- | --- | --- | --- |
| `v1.2.0` | 11/29/2024 | [IMPROVEMENTS] [SECURITY] |  | `Recommended version` |
| `v1.1.0` | 5/24/2024 | [IMPROVEMENTS] |  | `Upgrade` |
| `v1.0.1` | 6/21/2023 | [BUG FIX] |  | `Upgrade` |
| `v1.0.0` | 6/9/2023 | [RELEASE] |  | `Initial release` |