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

## Overview

This collector pulls events from the Box API and pulls from admin activities endpoint.

## 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** |
| --- | --- | --- | --- |
| Admin | `https://api.box.com/2.0/events` | `admin` | `cloud.box.events.json` |

For more information on how the events are parsed, [visit our page](https://devodocs.atlassian.net/wiki/spaces/latest/pages/94661298).

## Vendor setup

To log in to the Box environment. Using the vendor doc [here](https://developer.box.com/guides/authentication/jwt/jwt-setup/):

#### Enable the Box API Playground

1. Navigate to the Developer Console Log into Box and go to the [Developer Console](https://app.box.com/developers/console). Select Create New App.
2. Select application type Select Custom App from the list of application types. A modal will appear to prompt a selection for the next step.
3. Provide basic application information

| **Purpose** | **Details** |
| --- | --- |
| Automation, Custom Portal | Specify if the app is built by a customer or partner. |
| Integration | Specify the integration category, external system name if the app is built by a customer or partner. |
| Other | Specify the app purpose and if it is built by a customer or partner. |

4. Select application authentication Select Server Authentication (with JWT) if you would like to verify application identity with a key pair and confirm with Create App. Once created you will not be able to change it
5. Public and private key pair Once a Custom App is created leveraging Server Authentication with JWT, a key pair can be generated via the configuration tab within the [Developer Console](https://app.box.com/developers/console). Alternatively, you can generate your own and supply Box with the public key. Regardless of the method you select, your Box account will need to have 2FA enabled for security purposes.
  1. **Generate a keypair (Recommended)** If you would like to use a Box generated keypair, navigate to the [Developer Console](https://app.box.com/developers/console) where you can generate a configuration file. This file includes a public/private keypair and a number of other application details that are necessary for authentication.
  2. To generate this file, navigate to the **Configuration** tab of the [Developer Console](https://app.box.com/developers/console) and scroll down to the **Add and Manage Public Keys** section. Once this step is completed a File will be downloaded, this is the information you will use to copy to your Collector in the Self Service Application.
6. App Authorization Before the application can be used, a Box Admin needs to authorize the application within the Box Admin Console.

Navigate to the Authorization tab for your application within the [Developer Console](https://app.box.com/developers/console). Your Box Admin will need to authorize this. Once completed your app is ready to use.

## 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** |
| --- | --- |
| `client_id` | The Box client ID |
| `client_secret` | The Box client secret |
| `public_key_id` | The Box Public Key Id |
| `private_key` | The Box Private Key |
| `passphrase` | Box Passphrase |
| `enterprise_id` | The Box Account Enterprise ID |

## Accepted Authentication Methods

| **Authentication Method** | **Client ID** | **Client Secret** | **Public Key Id** | **Private Key** | **Passphrase** | **Enterprise Id** |
| --- | --- | --- | --- | --- | --- | --- |
| JWT | Required | Required | 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 (<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.
> 
> 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": {
>     "box": {
>       "id": "<short_unique_id>",
>       "enabled": true,
>       "credentials": {
>         "client_id": "john_doe",
>         "client_secret": "1234",
>         "public_key_id": "string",
>         "private_key": "string",
>         "passphrase": "string"
>       },
>       "enterprise_id": "124east",
>       "services": {
>         "admin": {
>           "lag_seconds": 120,
>           "initial_run_delta_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.
> 
> Please replace the placeholders with real world values following the description table below:
> 
> | **Parameter** | **Data Type** | **Requirement** | **Value Range / Format** | **Details** |
> | --- | --- | --- | --- | --- |
> | `short_unique_id` | `str` | `Mandatory` | Min length: 1, Max length: 5 | Short, unique ID for the input service, used in persistence addressing. Avoid duplicates to prevent collisions. |
> | `client_id` | `str` | `Mandatory` | Min length: 1 | Client ID from config.json |
> | `client_secret` | `str` | `Mandatory` | Min length: 1 | Client secret from config.json |
> | `public_key_id` | `str` | `Mandatory` | Min length: 1 | Public Key from config.json |
> | `private_key` | `str` | `Mandatory` | Begin Private key ... End Private key | Private key from config.json |
> | `passphrase` | `str` | `Mandatory` | Min length: 1 | Passphrase from config.json |
> | `enterprise_id` | `str` | `Mandatory` | Min length: 1 | Enterprise Id from config.json |
> | `lag_seconds` | `int` | `Optional` | Min: 60 | Custom period to start the query now()-120 seconds (120s). |
> | `initial_run_delta_seconds` | `int` | `Optional` | Min: 60 | Custom period for time between start and end of query |
> 
> > 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-20241022-092535.png](media://1baab077-579b-40e5-b38e-1d27fc40dbba)
> 
> > ⚠️ Replace `<product_name>` with the proper value.
> 
> ### Editing the config.yaml file
> 
> ```
> globals:
>   debug: false
>   id: <collector_id_value>
>   name: <collector_name_value>
>   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:
>   box:
>     id: "<short_unique_id>"
>     enabled: true
>     credentials:
>       client_id: john_doe
>       client_secret: '1234'
>       public_key_id: string
>       private_key: string
>       passphrase: string
>     enterprise_id: 124east
>     services:
>       admin:
>         lag_seconds: 120
>         initial_run_delta_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** | **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 the input service, used in persistence addressing. Avoid duplicates to prevent collisions. |
> | `client_id` | `str` | Mandatory | Min length: 1 | Client ID from config.json |
> | `client_secret` | `str` | Mandatory | Min length: 1 | Client secret from config.json |
> | `public_key_id` | `str` | Mandatory | Min length: 1 | Public Key from config.json |
> | `private_key` | `str` | Mandatory | Begin Private key ... End Private key | Private key from config.json |
> | `passphrase` | `str` | Mandatory | Min length: 1 | Passphrase from config.json |
> | `enterprise_id` | `str` | Mandatory | Min length: 1 | Enterprise Id from config.json |
> | `lag_seconds` | `int` | Optional | Min: 60 | Custom period to start the query now()-120 seconds (120s). |
> | `initial_run_delta_seconds` | `int` | Optional | Min: 60 | Custom period for time between start and end of query |
> 
> ### 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-box_if-docker-image-1.0.0.tgz](https://drive.google.com/file/d/17quaTD44vHsSqbU1_SRiXU9W57mAU2rR/view?usp=drive_link) | `dc6b18ddae1ac44847e84817a0a8d4d031f6e33472d3087e351bf9c93160413d` |
> 
> 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.

<details>
<summary>Event deduplication</summary>

The process for deduplication of events is handled by the event id that is returned that is stored and checked against on each pull.
</details>

<details>
<summary>Devo categorization and destination</summary>

All services are tagged by the service they are pulled by.
</details>

<details>
<summary>Setup/Puller Output</summary>

```
2024-04-02T12:36:10.881042712Z 2024-04-02T12:36:10.880    INFO InputProcess::MainThread -> InputThread(Box,45635) - Starting thread (execution_period=300s)
2024-04-02T12:36:10.900848871Z 2024-04-02T12:36:10.900    INFO InputProcess::MainThread -> ServiceThread(Box,45635,admin,predefined) - Starting thread (execution_period=300s)
2024-04-02T12:36:10.901635871Z 2024-04-02T12:36:10.901    INFO InputProcess::MainThread -> BoxPullerSetup(Box-collector,Box#45635,admin#predefined) -> Starting thread
2024-04-02T12:36:10.902970384Z 2024-04-02T12:36:10.902    INFO InputProcess::MainThread -> BoxPuller(Box,45635,admin,predefined) - Starting thread
2024-04-02T12:36:10.903841384Z 2024-04-02T12:36:10.903 WARNING InputProcess::BoxPuller(Box,45635,admin,predefined) -> Waiting until setup will be executed
2024-04-02T12:36:10.910390935Z 2024-04-02T12:36:10.909 WARNING InputProcess::BoxPullerSetup(Box-collector,Box#45635,admin#predefined) -> The token/header/authentication has not been created yet
2024-04-02T12:36:10.912045728Z 2024-04-02T12:36:10.911    INFO InputProcess::BoxPullerSetup(Box-collector,Box#45635,admin#predefined) -> using base url: https://manage.office.com
2024-04-02T12:36:11.221983503Z 2024-04-02T12:36:11.221    INFO InputProcess::BoxPullerSetup(Box-collector,Box#45635,admin#predefined) -> Setup for module <BoxPuller> has been successfully executed
2024-04-02T12:36:11.906707525Z 2024-04-02T12:36:11.905    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> BoxPuller(Box,45635,admin,predefined) Starting the execution of pre_pull()
2024-04-02T12:36:11.907795456Z 2024-04-02T12:36:11.906    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Reading persisted data
2024-04-02T12:36:11.910462424Z 2024-04-02T12:36:11.909    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Data retrieved from the persistence: {'@persistence_version': 1, 'start_time_in_utc': None, 'last_event_time_in_utc': '2024-04-02 12:35:07'}
2024-04-02T12:36:11.911358075Z 2024-04-02T12:36:11.910    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Start time not found in config, using 2024-04-02 12:35:11
2024-04-02T12:36:11.912847398Z 2024-04-02T12:36:11.911    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Running the persistence upgrade steps
2024-04-02T12:36:11.915154717Z 2024-04-02T12:36:11.913    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Running the persistence corrections steps
2024-04-02T12:36:11.916748235Z 2024-04-02T12:36:11.915    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Running the persistence corrections steps
2024-04-02T12:36:11.918276116Z 2024-04-02T12:36:11.917    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> No changes were detected in the persistence
2024-04-02T12:36:11.919248467Z 2024-04-02T12:36:11.918    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> BoxPuller(Box,45635,admin,predefined) Finalizing the execution of pre_pull()
2024-04-02T12:36:11.920446419Z 2024-04-02T12:36:11.919    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Starting data collection every 60 seconds
2024-04-02T12:36:11.924162570Z 2024-04-02T12:36:11.923    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Pull Started
2024-04-02T12:36:12.045307400Z 2024-04-02T12:36:12.044    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Found 1 removed 0
2024-04-02T12:36:12.221770395Z 2024-04-02T12:36:12.221    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> (Partial) Statistics for this pull cycle (@devo_pulling_id=1712061371905):Number of requests made: 1; Number of events received: 30; Number of duplicated events filtered out: 0; Number of events generated and sent: 30; Average of events per second: 101.027.
2024-04-02T12:36:12.222243522Z 2024-04-02T12:36:12.222    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Statistics for this pull cycle (@devo_pulling_id=1712061371905):Number of requests made: 1; Number of events received: 30; Number of duplicated events filtered out: 0; Number of events generated and sent: 30; Average of events per second: 100.751.
2024-04-02T12:36:12.222631040Z 2024-04-02T12:36:12.222    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> The data is up to date!
2024-04-02T12:36:12.223216005Z 2024-04-02T12:36:12.223    INFO InputProcess::BoxPuller(Box,45635,admin,predefined) -> Data collection completed. Elapsed time: 0.318 seconds. Waiting for 59.682 second(s) until the next one```
```
</details>

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

To change the persistence you must edit the short_id of the collector in the config.
</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** |
| --- | --- | --- | --- | --- |
| BoxAPIException |  | The stack trace will be generated dynamically from the events session method of the box sdk. |  |  |
| JWT token set up |  | {"error":"invalid_grant","error_description":"Please check the 'sub' claim. The 'sub' specified is invalid."} | The remote source being pullable is due to the set up of your credentials in the config. | The "sub" claim in the JWT should always be a Box ID — depending on the value of "box_sub_type" it would be either the ID of the user you're trying to generate tokens for or the ID of the enterprise you're authenticating as the service account for. You want to verify this value is correct and that you're passing it as a string. |
</details>

## Collector operations

<details>
<summary>Operations to verify collector</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-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-<name>\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 sender services depending on the event type to deliver (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. |
| 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 the collector executed the pull logic. 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 were 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. |

### 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 the collector executed the pull logic. 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 were sent to Devo between the last UTC checkpoint and now.
- Those 21 events required 0.00 seconds to be delivered. |
</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)
```
</details>

## Change log

| **Release** | **Released on** | **Release type** | **Recommendations** |
| --- | --- | --- | --- |
| `v1.0.0` | 9/16/2024 | [NEW FEATURE] | `Recommended version` |