--- title: "Cisco AMP collector" canonical: "https://docs.devo.com/space/latest/526057478/Cisco%20AMP%20collector" format: markdown --- > Macro (toc) ## Overview Cisco Advanced Malware Protection (AMP) for Endpoints is a cloud-managed endpoint security solution that provides advanced protection against viruses, malware, and other cyber-threats by detecting, preventing, and responding to threats. ## Devo collector features | **Feature** | **Details** | | --- | --- | | Allow parallel downloading (`multipod`) | `not allowed` | | Running environments | - `collector server` - `on-premise` | | Populated Devo events | `table` | | Flattening preprocessing | `yes` | ## Data sources | **Data source** | **Description** | **API endpoint** | **Collector service name** | **Devo table** | **Available from release** | | --- | --- | --- | --- | --- | --- | | Events | Events in Event Stream | `/Events` | `Events` | `edr.cisco.amp.events` | `v1.0.0` | For more information on how the events are parsed, [visit our page](https://devodocs.atlassian.net/wiki/spaces/latest/pages/355565682). ## 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_client_id` | User Client ID to authenticate to the service. | | `api_key` | User Api Key to authenticate to the service. | | `event_stream_name` | The name of the event stream | | `event_stream_password` | The password for the event stream | ## Accepted authentication methods The following are the accepted authentication methods for this collector. | **Authentication method** | **Client ID** | **Api key** | **Event stream name** | **Event stream password** | | --- | --- | --- | --- | --- | | Basic Authentication | [REQUIRED] | [REQUIRED] | [REQUIRED] | [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). > 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. > > To enable the collector for a customer: > > 1. In the **Collector Server** **GUI**, access the **domain** in which you want this instance to be created > 2. Click **Add Collector** and find the one you wish to add. > 3. In the **Version** field, select the latest value. > 4. In the **Collector Name** field, set the value you prefer (this name must be unique inside the same Collector Server domain). > 5. In the sending method select **Direct Send. Direct Send** configuration is optional for collectors that create `Table` events, but mandatory for those that create `Lookups`. > 6. In the **Parameters** section, establish the **Collector Parameters** as follows below: > > ### Editing the JSON configuration > > ``` > { > "global_overrides": { > "debug": false > }, > "inputs": { > "cisco_amp": { > "id": "", > "enabled": true, > "credentials": { > "api_endpoint": "", > "api_client_id": "", > "api_key": "", > "event_stream_name": "", > "event_stream_password": "", > "all_event_types": "0 or 1 defaults to 1", > "event_types": "use only if all_event_types is 0", > "ack_messages": true > }, > "services": { > "event_stream": {} > } > } > } > } > ``` > > > ℹ️ 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. > > > ⚠️ Please replace the placeholders with real world values following the description table below > > | | | | | | > | --- | --- | --- | --- | --- | > | **Parameter** | **Data type** | **Type** | **Value range / Format** | **Details** | > | `debug_status` | `bool` | `Mandatory` | `false` / `true` | 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. | > | `short_unique_id` | `int` | `Mandatory` | Minimum length: 1 > Maximum length: 5 | Use this param to give an unique id to this input service.
> ⚠️ This parameter is used to build the persistence address, do not use the same value for multiple collectors. It could cause a collision. | > | `enabled` | `bool` | `Mandatory` | `false` / `true` | Use this param 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_endpoint` | `str` | `Optional` | | By default, the base url is `api.amp.cisco.com`. This parameter allows you to customize the base url.
> 📝 This parameter should be removed if it is not used. | > | `api_client_id` | `str` | `Mandatory` | Any | User Client ID to authenticate to the service. | > | `api_key` | `str` | `Mandatory` | Any | User Api Key to authenticate to the service. | > | `event_stream_name` | `str` | `Mandatory` | Any | Name of Event Stream | > | `event_stream_password` | `str` | `Mandatory` | Any | The Password for the event stream | > | `all_event_types` | `int` | `Optional` | 0 or 1 | | > | `ack_messages` | `bool` | `Mandatory` | `false` / `true` | Use this param to enable or disable the given input logic when running the collector. If the value is `true`, the message will be deleted from the queue. If the value is `false`, it will be not be deleted. | > > > 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 > > In Devo, go to **Administration → Credentials → X.509 Certificates**, download the **Certificate**, **Private key** and **Chain CA** and save them in `/certs/`. Learn more about security credentials in Devo [here](#). > > ![image-20240229-092634.png](media://b91f040e-2e20-42e3-a1fe-5e3a0b9bd935) > > > ⚠️ Replace `` with the proper value. > > ### Editing the config.yaml file > > ``` > globals: > debug: false > id: not_used > name: cisco_amp > persistence: > type: filesystem > config: > directory_name: state > # type: redis > # config: > # host: host > # port: port > # password: password > # db: db > > outputs: > # devo_1: > # type: devo_platform > # config: > # address: collector-us.devo.io > # port: 443 > # type: SSL > # chain: chain.crt > # cert: .crt > # key: .key > # devo_2: > # type: devo_platform > # config: > # address: collector-eu.devo.io > # port: 443 > # type: SSL > # chain: chain.crt > # cert: .crt > # key: .key > # relay_1: > # type: syslog > # config: > # address: 127.0.0.1 > # port: 13000 > > console_1: > type: console > > inputs: > cisco_amp: > id: 12345 > enabled: true > credentials: > api_endpoint: "api.amp.cisco.com" > api_client_id: "" > api_key: "" > event_stream_name: "" > event_stream_password: "" > all_event_types: 1 > ack_messages: False > services: > event_stream: > request_period_in_seconds: 60 > ``` > > > ℹ️ 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` | `false` / `true` | 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 > Maximum length: 5 | Use this param to give an unique id to this collector. | > | `collector_name` | `str` | `Mandatory` | Minimum length: 1 > Maximum length: 10 | Use this param to give a valid name to this collector. | > | `devo_address` | `str` | `Mandatory` | `collector-us.devo.io` > `collector-eu.devo.io` | Use this param to identify the Devo Cloud where the events will be sent. | > | `chain_filename` | `str` | `Mandatory` | Minimum length: 4 > Maximum length: 20 | Use this param 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 param to identify the `file.cert` downloaded from your Devo domain. | > | `key_filename` | `str` | `Mandatory` | Minimum length: 4 > Maximum length: 20 | Use this param to identify the `file.key` downloaded from your Devo domain. | > | `short_unique_id` | `int` | `Mandatory` | Minimum length: 1 > Maximum length: 5 | Use this param to give an unique id to this input service.
> ⚠️ This parameter is used to build the persistence address, do not use the same value for multiple collectors. It could cause a collision. | > | `enabled` | `bool` | `Mandatory` | `false` / `true` | Use this param 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_endpoint` | `str` | `Optional` | | By default, the base url is `api.amp.cisco.com`. This parameter allows you to customize the base url.
> 📝 This parameter should be removed if it is not used. | > | `api_client_id` | `str` | `Mandatory` | Any | User Client ID to authenticate to the service. | > | `api_key` | `str` | `Mandatory` | Any | User Api Key to authenticate to the service. | > | `event_stream_name` | `str` | `Mandatory` | Any | Name of Event Stream | > | `event_stream_password` | `str` | `Mandatory` | Any | The Password for the event stream | > | `all_event_types` | `int` | `Optional` | 0 or 1 | | > | `ack_messages` | `bool` | `Mandatory` | `false` / `true` | Use this param to enable or disable the given input logic when running the collector. If the value is `true`, the message will be deleted from the queue. If the value is `false`, it will be not be deleted. | > | `enabled` | `bool` | `Mandatory` | `false` / `true` | Use this param 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. | > > ### 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-cisco_amp_if-docker-image-1.1.1](https://drive.google.com/file/d/1vMxaqugy7mirxRiX49E4Jv-0WmQjVjV2/view?usp=drive_link) | `f6b5ca2beacbb2d18e79d23cb7eb0a65078b921145327d6ac87f53173565ccaf` | > > 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. ### Events service
Verify data collection 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: ``` INFO InputProcess::CiscoAmpPullerSetup(unknown,cisco_amp#23512,event_stream#predefined) -> Authentication Successful 2024-02-23T08:24:54.579 INFO InputProcess::CiscoAmpPullerSetup(unknown,cisco_amp#23512,event_stream#predefined) -> Setup for module has been successfully executed 2024-02-23T08:24:54.794 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> credentials are valid ``` #### 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. ``` 2024-02-23T08:24:54.795 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> Starting data collection every 60 seconds 2024-02-23T08:24:55.046 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> Pika version 1.3.2 connecting to ('107.20.203.8', 443) 2024-02-23T08:24:55.071 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> Socket connected: 2024-02-23T08:24:55.123 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> SSL handshake completed successfully: 2024-02-23T08:24:55.124 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> Streaming transport linked up: (, _StreamingProtocolShim: params=>). 2024-02-23T08:24:55.196 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> AMQPConnector - reporting success: params=> 2024-02-23T08:24:55.196 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> AMQPConnectionWorkflow - reporting success: params=> 2024-02-23T08:24:55.196 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> Connection workflow succeeded: params=> 2024-02-23T08:24:55.197 INFO InputProcess::CiscoAmpPuller(cisco_amp,23512,event_stream,predefined) -> Created channel=1 ```
Restart the persistence Currently, this collector uses no persistence. > ⚠️ Note that this action clears the persistence and cannot be recovered in any way. Resetting persistence could result in duplicate or lost events.
## 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: ``` INFO MainProcess::MainThread -> (CollectorMultiprocessingQueue) standard_queue_multiprocessing -> max_size_in_messages: 1000, max_size_in_mb: 1024, max_wrap_size_in_items: 100 INFO MainProcess::MainThread -> [OUTPUT] OutputMultiprocessingController::__init__ Configuration -> {'devo_1': {'type': 'devo_platform', 'config': {'address': 'collector-eu.devo.io', 'port': 443, ...}}} INFO MainProcess::MainThread -> OutputProcess - Starting thread (executing_period=300s) INFO MainProcess::MainThread -> InputProcess - Starting thread (executing_period=300s) INFO OutputProcess::MainThread -> Process started INFO InputProcess::MainThread -> Process Started INFO InputProcess::MainThread -> InitVariables Started INFO InputProcess::MainThread -> Validating variables in collector definitions Started INFO InputProcess::MainThread -> Flatten data is not provided in the config.yaml. Considering the flatten data from collector definitions INFO InputProcess::MainThread -> Validating collector Variables is terminated INFO InputProcess::MainThread -> Initialization of api_base_url has started. INFO InputProcess::MainThread -> api_base_url has been initialized INFO InputProcess::MainThread -> Initialization of credentials has started. INFO InputProcess::MainThread -> credentials have been initialized. INFO OutputProcess::MainThread -> [INTERNAL LOGIC] DevoSender::_validate_kwargs_for_method__init__ -> The
does not appear to be an IP address and cannot be verified: collector-eu.devo.io INFO InputProcess::MainThread -> InitVariables Terminated INFO InputProcess::MainThread -> InputThread(wiz_data_puller,111) - Starting thread (execution_period=120s) INFO InputProcess::MainThread -> ServiceThread(wiz_data_puller,111,issues,predefined) - Starting thread (execution_period=120s) INFO InputProcess::MainThread -> WizDataPullerSetup(wiz_collector,wiz_data_puller#111,issues#predefined) -> Starting thread INFO InputProcess::MainThread -> WizDataPuller(wiz_data_puller,111,issues,predefined) - Starting thread WARNING InputProcess::WizDataPuller(wiz_data_puller,111,issues,predefined) -> Waiting until setup will be executed INFO InputProcess::WizDataPullerSetup(wiz_collector,wiz_data_puller#111,issues#predefined) -> Puller Setup Started INFO InputProcess::WizDataPullerSetup(wiz_collector,wiz_data_puller#111,issues#predefined) -> This is the first run of collector. Generating the access token INFO InputProcess::WizDataPullerSetup(wiz_collector,wiz_data_puller#111,issues#predefined) -> Getting the auth token url based on provided api_base_url INFO InputProcess::WizDataPullerSetup(wiz_collector,wiz_data_puller#111,issues#predefined) -> Using default Authentication Domain auth.wiz.io for fetching Access Token INFO OutputProcess::MainThread -> [INTERNAL LOGIC] DevoSender::_validate_kwargs_for_method__init__ -> The
does not appear to be an IP address and cannot be verified: collector-eu.devo.io INFO OutputProcess::MainThread -> [INTERNAL LOGIC] DevoSender::_validate_kwargs_for_method__init__ -> The
does not appear to be an IP address and cannot be verified: collector-eu.devo.io INFO OutputProcess::MainThread -> DevoSender(standard_senders,devo_sender_0) -> Starting thread INFO OutputProcess::MainThread -> DevoSenderManagerMonitor(standard_senders,devo_1) -> Starting thread (every 300 seconds) INFO OutputProcess::MainThread -> DevoSenderManager(standard_senders,manager,devo_1) -> Starting thread INFO OutputProcess::MainThread -> DevoSender(lookup_senders,devo_sender_0) -> Starting thread INFO OutputProcess::MainThread -> DevoSenderManagerMonitor(lookup_senders,devo_1) -> Starting thread (every 300 seconds) INFO OutputProcess::MainThread -> DevoSenderManager(lookup_senders,manager,devo_1) -> Starting thread INFO OutputProcess::MainThread -> DevoSender(internal_senders,devo_sender_0) -> Starting thread INFO OutputProcess::MainThread -> DevoSenderManagerMonitor(internal_senders,devo_1) -> Starting thread (every 300 seconds) INFO OutputProcess::MainThread -> DevoSenderManager(internal_senders,manager,devo_1) -> Starting thread INFO InputProcess::MainThread -> [GC] global: 36.7% -> 36.7%, process: RSS(26.93MiB -> 27.97MiB), VMS(334.43MiB -> 334.67MiB) INFO OutputProcess::MainThread -> [GC] global: 36.7% -> 36.3%, process: RSS(26.68MiB -> 28.61MiB), VMS(910.71MiB -> 910.71MiB) INFO OutputProcess::DevoSender(internal_senders,devo_sender_0) -> Created a sender: {"group_name": "internal_senders", "instance_name": "devo_sender_0", "url": "collector-eu.devo.io:443", ...} ``` ### 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: ``` INFO OutputProcess::SyslogSenderManagerMonitor(standard_senders,sidecar_0) -> Number of available senders: 1, sender manager internal queue size: 0 INFO OutputProcess::SyslogSenderManagerMonitor(standard_senders,sidecar_0) -> enqueued_elapsed_times_in_seconds_stats: {} INFO OutputProcess::SyslogSenderManagerMonitor(standard_senders,sidecar_0) -> Sender: SyslogSender(standard_senders,syslog_sender_0), status: {"internal_queue_size": 0, "is_connection_open": True} INFO OutputProcess::SyslogSenderManagerMonitor(standard_senders,sidecar_0) -> Standard - Total number of messages sent: 44, messages sent since "2022-06-28 10:39:22.511671+00:00": 44 (elapsed 0.007 seconds) INFO OutputProcess::SyslogSenderManagerMonitor(internal_senders,sidecar_0) -> Number of available senders: 1, sender manager internal queue size: 0 INFO OutputProcess::SyslogSenderManagerMonitor(internal_senders,sidecar_0) -> enqueued_elapsed_times_in_seconds_stats: {} INFO OutputProcess::SyslogSenderManagerMonitor(internal_senders,sidecar_0) -> Sender: SyslogSender(internal_senders,syslog_sender_0), status: {"internal_queue_size": 0, "is_connection_open": True} INFO OutputProcess::SyslogSenderManagerMonitor(internal_senders,sidecar_0) -> Internal - Total number of messages sent: 1, messages sent since "2022-06-28 10:39:22.516313+00:00": 1 (elapsed 0.019 seconds) ``` > ℹ️ 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: | **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: 44, messages sent since "2022-06-28 10:39:22.511671+00:00": 21 (elapsed 0.007 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 `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.
> ℹ️ By default these traces will be shown every 10 minutes. |
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) ``` > ℹ️ 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
Enable/disable the logging debug mode 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.
## Change log | **Release** | **Released on** | **Release type** | **Details** | **Recommendations** | | --- | --- | --- | --- | --- | | `v1.1.1` | 6/3/2024 | [IMPROVEMENTS] [BUG FIXES] | **Bug fixes**
- Updated files for vulnerability fixes and fixed auto acknowledging | `Recommended version` | | `v1.1.0` | 3/25/2024 | [IMPROVEMENTS] [BUG FIXES] | **Improvements**
- Updated DCSDK to 1.11.1 - Added extra check for not valid message timestamps - Added extra check for improve the controlled stop - Changed default number for connection retries (now 7) - Fix for Devo connection retries - Updated DevoSDK to v5.1.9 - Fixed some bug related to development on MacOS - Added an extra validation and fix when the DCSDK receives a wrong timestamp format - Added an optional config property for use the Syslog timestamp format in a strict way - Updated DevoSDK to v5.1.10 - Fix for SyslogSender related to UTF-8 Enhance of troubleshooting. Trace Standardization, Some traces has been introduced. - Introduced a mechanism to detect "Out of Memory killer" situation
**Features**
- Fixed bug in create stream | `Update` | | `v1.0.0` | 2/23/2024 | [FEATURE] | - | `Initial version` |