SentinelOne Destination

Docs > Observability Pipelines（観測データの制御） > 送信先 > SentinelOne Destination

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

次で利用可能:

Logs

Overview

Use Observability Pipelines’ SentinelOne destination to send logs to SentinelOne.

Setup

For Secrets Management: Only enter the identifier for the token. Do not enter the actual value.

Configure the SentinelOne destination when you set up a pipeline. You can set up a pipeline in the UI, using the API, or with Terraform. The steps in this section are configured in the UI.

After you select the SentinelOne destination in the pipeline UI:

Enter the identifier for your token. If you leave it blank, the default is used.
Select your SentinelOne logs environment in the dropdown menu.

If you enter secret identifiers and then choose to use environment variables, the environment variable is the identifier entered and prepended with DD_OP_. For example, if you entered PASSWORD_1 for a password identifier, the environment variable for that password is DD_OP_PASSWORD_1.

Optional buffering

Toggle the switch to enable Buffering Options. Enable a configurable buffer on your destination to ensure intermittent latency or an outage at the destination doesn’t create immediate backpressure, and allow events to continue to be ingested from your source. Disk buffers can also increase pipeline durability by writing data to disk, ensuring buffered data persists through a Worker restart. See Destination buffers for more information.

If left unconfigured, your destination uses a memory buffer with a capacity of 500 events.
To configure a buffer on your destination:
1. Select the buffer type you want to set (Memory or Disk).
2. Enter the buffer size and select the unit.
  1. Maximum memory buffer size is 128 GB.
  2. Maximum disk buffer size is 500 GB.
3. In the Behavior on full buffer dropdown menu, select whether you want to block events or drop new events when the buffer is full.

Secret defaults

These are the defaults used for secret identifiers and environment variables.

SentinelOne write access token identifier:
- The default identifier is DESTINATION_SENTINEL_ONE_TOKEN.

SentinelOne write access token:
- The default environment variable is DD_OP_DESTINATION_SENTINEL_ONE_TOKEN.

View logs in a SentinelOne cluster

After you’ve set up the pipeline to send logs to the SentinelOne destination, you can view the logs in a SentinelOne cluster:

Log into the S1 console.
Navigate to the Singularity Data Lake (SDL) Search page. To access it from the console, click on Visibility on the left menu to go to SDL, and make sure you’re on the Search tab.
Make sure the filter next to the search bar is set to All Data.
This page shows the logs you sent from Observability Pipelines to SentinelOne.

Health metrics

For component metrics and destination buffer metrics emitted by all destinations, see the Pipelines Usage Metrics documentation. To filter or group by Splunk HEC destination metrics, use the tag component_type:splunk_hec_logs.