Google Chronicle Destination
This product is not supported for your selected
Datadog site. (
).
Observability Pipelines の Google Chronicle Destination を使用して、ログを Google Chronicle に送信します。
セットアップ
パイプラインをセットアップする 際に、Google Chronicle Destination とその環境変数を設定します。以下の情報は Pipelines UI で構成します。
Destination を設定する
To set up the Worker’s Google Chronicle destination:
- Enter the customer ID for your Google Chronicle instance.
- If you have a credentials JSON file, enter the path to your credentials JSON file. The credentials file must be placed under
DD_OP_DATA_DIR/config
. Alternatively, you can use the GOOGLE_APPLICATION_CREDENTIALS
environment variable to provide the credential path. - Select JSON or Raw encoding in the dropdown menu.
- Enter the log type. See template syntax if you want to route logs to different log types based on specific fields in your logs.
- Optionally, toggle the switch to enable Buffering Options.
Note: Buffering options is in Preview. Contact your account manager to request access.- If left disabled, the maximum size for buffering is 500 events.
- If enabled:
- Select the buffer type you want to set (Memory or Disk).
- Enter the buffer size and select the unit.
Note: Logs sent to the Google Chronicle destination must have ingestion labels. For example, if the logs are from a A10 load balancer, it must have the ingestion label A10_LOAD_BALANCER
. See Google Cloud’s Support log types with a default parser for a list of available log types and their respective ingestion labels.
環境変数を設定する
- Google Chronicle endpoint URL:
- Stored in the environment variable:
DD_OP_DESTINATION_GOOGLE_CHRONICLE_UNSTRUCTURED_ENDPOINT_URL
.
Destination の動作
イベントのバッチ処理
以下のいずれかのパラメーターを満たすと、イベントのバッチがフラッシュされます。詳細は イベントのバッチ処理 を参照してください。
Max Events | Max Bytes | タイムアウト (秒) |
---|
なし | 1,000,000 | 15 |