Try it free

Stream logs with Cribl

  • Latest Dynatrace
  • How-to guide
  • 3-min read

You can send logs to the Dynatrace Log Ingestion API using Cribl Stream. Cribl Stream is a data pipeline that collects, processes, and routes logs, metrics, and traces between sources and destinations.

Prerequisites

  • A Dynatrace access token for log ingestion, either:
    • Platform token (recommended): with the openpipeline:logs:ingest scope. See Platform tokens.
    • Classic access token: with the logs.ingest (Ingest Logs) scope. See Dynatrace API - Tokens and authentication.
  • The URL of your Dynatrace environment:
    • https://{your-environment-id}.live.dynatrace.com
    • https://{your-activegate-domain}:9999/e/{your-environment-id} if you use an Environment ActiveGate.

These instructions apply to Cribl Stream version 4.20.

Deploy integration using OpenTelemetry

To send telemetry data to Dynatrace through Cribl Stream, follow these steps:

  1. On the top bar, select Products, then Cribl Stream. Under Worker Groups, select a Worker Group, then do one of the following:
    • To configure the destination through QuickConnect, go to Routing > QuickConnect, select Add Destination, and choose Dynatrace OTLP from the list.
    • To configure the destination through Routes, go to Data > Destinations, select Dynatrace OTLP, then select Add Destination.
  2. Configure destination general settings.
    • Output ID: enter a unique name to identify this output definition.
    • OTLP version is fixed at 1.3.1, and Protocol is fixed at HTTP using binary Protobuf encoding; JSON Protobuf isn't supported.
    • Endpoint type: select SaaS to send data to the Dynatrace SaaS endpoint, or ActiveGate if you're routing data through an Environment ActiveGate.
    • Endpoint: enter the full OTLP endpoint: https://{your-environment-id}.live.dynatrace.com/api/v2/otlp or https://{your-activegate-domain}:9999/e/{your-environment-id}/api/v2/otlp.
    • Auth token (text secret): create or select a Cribl stored text secret that contains your Dynatrace access token. See Prerequisites for the required token type and scope.
    • Optional settings include backpressure behavior (Block, Drop, or Persistent Queue), and tags to filter and group destinations on Cribl Stream's Manage Destinations page.
  3. Review processing and delivery settings.
    • Processing Settings let you define post-processing pipelines.
    • Retries: set Pre-backoff interval, Backoff multiplier, and Backoff limit (ms) for exponential backoff for retryable failed-HTTP status codes: 413, 502, 503, 504 (see Response codes).
    • Advanced Settings cover certificate validation, compression, request concurrency, and other transport options.
  4. Select Save, then Commit & Deploy.
  5. Use the Test tab in the destination's configuration modal to validate the configuration and connectivity.

Consult the Cribl product documentation for additional configuration details.

Deploy integration using HTTP and API

To send logs to Dynatrace through the Cribl Stream HTTP destination, follow these steps:

  1. On the top bar, select Products, then Cribl Stream. Under Worker Groups, select a Worker Group, then do one of the following:
    • To configure the destination through QuickConnect, go to Routing > QuickConnect, select Add Destination, and choose Dynatrace HTTP from the list.
    • To configure the destination through Routes, go to Data > Destinations, select Dynatrace HTTP, then select Add Destination.
  2. Configure destination general settings.
    • Output ID: enter a unique name to identify this destination definition.
    • Endpoint: select the type of Dynatrace endpoint to send data to:
      • Cloud: sends data to https://{your-environment-id}.live.dynatrace.com/api/v2/logs/ingest. Provide your {your-environment-id} (see Prerequisites section).
      • ActiveGate: sends data to https://{your-activegate-domain}:9999/e/{your-environment-id}/api/v2/logs/ingest. Provide your {your-environment-id} and {your-activegate-domain} (see Prerequisites section).
      • Manual: manually specify the full endpoint URL.
    • Configure optional settings.
      • Backpressure behavior: block, drop, or queue events when all receivers exert backpressure. Defaults to Block.
      • Tags: optionally add tags to filter and group destinations on Cribl Stream's Manage Destinations page. These tags aren't added to processed events.
  3. Configure authentication. Select Authentication from the sidebar, then select an Authentication type:
    • Auth token: provide your Dynatrace access token directly in the Token field. See Prerequisites for the required token type and scope.
    • Token (text secret): create or select a Cribl stored text secret that contains your Dynatrace access token instead.
  4. Review processing and delivery settings.
    • Processing Settings let you define post-processing pipelines.
    • Retries: set Pre-backoff interval, Backoff multiplier, and Backoff limit (ms) for exponential backoff for retryable failed-HTTP status codes: 429, 502, 503, 504 (see Response codes).
    • Advanced Settings cover certificate validation, compression, request concurrency, and other transport options.
  5. Select Save, then Commit & Deploy.
  6. Use the Test tab in the destination's configuration modal to validate the configuration and connectivity.

Consult the Cribl product documentation for additional configuration details.

Related tags
Log Analytics