> For the complete documentation index, see [llms.txt](https://docs.onum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onum.com/data-sinks/data-sink-integrations/send-data-to-falcon-logscale.md).

# Send data to Falcon LogScale

{% hint style="info" %}
See the changelog of this Data Sink type [here](/data-sinks-changelog/falcon-logscale-data-sink.md).
{% endhint %}

## Overview

Onum supports integration with Falcon LogScale.

With our **Falcon LogScale** Data Sink, you can send event data to Falcon LogScale via HTTP or HTTPS. It is an efficient and flexible way to ingest data into Falcon LogScale without the need for intermediary files or complex configurations. Events can be sent in either raw or JSON format.

## Falcon LogScale Setup

You'll need to generate an ingest token in your Falcon LogScale instance, which will be required in the Onum setup. Follow these steps to generate the required LogScale ingest token:

{% stepper %}
{% step %}
Access LogScale, access the **Repositories and views** tab and select the relevant repository.
{% endstep %}

{% step %}
Click **Ingest** > **Settings** on the side menu and click **Ingest tokens**.
{% endstep %}

{% step %}
In the **Ingest tokens** page, click **+ Add token** to add a token to this repository.
{% endstep %}

{% step %}
In the **New token** dialog box, enter a **Token name** to identify the token. You can optionally set an **Assigned parser** by selecting a parser from the list. For more information on parsers, see [this article](https://library.humio.com/data-analysis/parsers.html).
{% endstep %}

{% step %}
Click **Save**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Learn more about LogScale ingest tokens in [this article](https://library.humio.com/falcon-logscale-cloud/ingesting-data-tokens.html).
{% endhint %}

## Onum Setup

{% stepper %}
{% step %}
Access Onum, go to the **Data sinks** area and click **New data sink**. Select the **Falcon LogScale** Data Sink from the list.
{% endstep %}

{% step %}
Enter a **Name** for the Data Sink. Optionally, add a **Description** and some **Tags** to identify the Sink.
{% endstep %}

{% step %}
Decide whether or not to include this Data Sink info in the metrics and graphs of the [**Home**](https://docs.onum.com/the-workspace/home) area using the **Include in metrics** toggle.
{% endstep %}

{% step %}
Enter your **Instance URL** (check your required URL in [this article](https://library.humio.com/falcon-logscale-cloud/endpoints.html)) and the **Port** number. Port `443` is required for the **Falcon LogScale** connection.
{% endstep %}

{% step %}
Click on the **Token** field and select **New secret**. In the window that appears, give your secret a **Name** and choose if you want to give a **Expiration date** to your token or not. Then, click **Add new value** and paste the token that you generated in LogScale (see the [Falcon LogScale Setup](#falcon-logscale-setup) section above). Click **Save** when you're done.

{% hint style="info" %}
Learn more about Secrets in [this article](/settings/organization-settings/secrets-management.md).
{% endhint %}
{% endstep %}

{% step %}
Now, select the token you have just created in the **Token** field.
{% endstep %}

{% step %}
In the **Event format** section, choose either **JSON** or **Raw**.
{% endstep %}

{% step %}
In the **Advanced configuration** settings, you can add some additional config.

For optimal performance, we strongly recommend enabling **Bulk configuration** and enter these settings to significantly improve performance and reduce system load:

* **Event time limit** -  `2`
* **Number of events** -  `1500`
* **Batch size (bytes)** - `5000000`

Depending on your Pipelines ingestion level, you may need to adjust these values to optimize performance and prevent prolonged waiting periods that could contribute to back pressure.

{% hint style="warning" %}
Only enable Bulk configuration after completing Pipeline debugging. If you need to use Debug mode, temporarily disable Bulk configuration, then re-enable it once debugging is complete.
{% endhint %}
{% endstep %}

{% step %}
Toggle on the **Enable retry attempts** button if you want to define rules that dictate how the system will automatically re-run failed operations.

<table><thead><tr><th width="224.3125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Max attempts</strong></td><td>Maximum number of attempts before returning an error. The minimum value is <code>1</code>.</td></tr><tr><td><strong>Wait between attempts</strong></td><td>The milliseconds to wait between retry attempts. The minimum value is <code>100</code>.</td></tr><tr><td><strong>Backoff interval</strong></td><td>A multiplication factor you may apply to the time established in the <strong>Wait between attempts</strong> parameter to increase the time to wait between attempts. For example, if the <strong>Wait between attempts</strong> is <code>100</code>, and the <strong>Backoff interval</strong> is <code>2</code>, the retry time will increase as follows each time: <code>100</code>, <code>200</code>, <code>400</code>, <code>800</code>... The minimum value is <code>1</code>.</td></tr></tbody></table>
{% endstep %}

{% step %}
If you are using a proxy to establish the connection, toggle on the **Proxy configuration** button and enter these details:

<table><thead><tr><th width="224.4921875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Select scheme</strong></td><td>Choose the scheme to connect to (<strong>HTTP</strong> or <strong>HTTPS</strong>).</td></tr><tr><td><strong>Host</strong></td><td>The host of the proxy URL used to establish the connection.</td></tr><tr><td><strong>Port</strong></td><td>The port of the proxy URL used to establish the connection.</td></tr><tr><td><strong>Username</strong></td><td>This is the username used to access the proxy.</td></tr><tr><td><strong>Select password</strong></td><td>Choose the proxy passcode from your secrets or create a new one.</td></tr></tbody></table>
{% endstep %}

{% step %}
Click **Finish** when complete. Your new Data Sink will appear in the **Data sinks** area list.
{% endstep %}
{% endstepper %}

## Pipeline configuration

When it comes to using this Data sink in a [Pipeline](/pipelines.md), you must configure the following output parameters. To do it, simply click the Data sink on the canvas and select **Configuration**.

### Output configuration

<table><thead><tr><th width="169.8515625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Message</strong><mark style="color:red;"><strong>*</strong></mark></td><td>Select the field to include in the output message. The data type must be <code>string</code>.</td></tr></tbody></table>

#### Add fields

Optionally, you may include as many key-value pairs as required.

<table><thead><tr><th width="169.8515625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Field name</strong><mark style="color:red;"><strong>*</strong></mark></td><td>Enter a name for the new field.</td></tr><tr><td><strong>Value</strong><mark style="color:red;"><strong>*</strong></mark></td><td>Select the field that contains the value data. </td></tr></tbody></table>