You can send logs, metrics, and traces to Dynatrace using Cribl Stream via OpenTelemetry Protocol (OTLP) or send only logs using Cribl Stream via HTTP and API ingestion.
The Dynatrace Collector offers various ingestion and transformation capabilities, making it a versatile tool for processing log data from a variety of sources.
Key Features
Multiple Endpoint Types: Connect to Dynatrace Cloud (SaaS), ActiveGate, or specify a manual endpoint URL.
Secure Authentication: Uses Dynatrace API tokens for secure data transmission.
Persistent Queue: Buffers data during connectivity issues to prevent data loss.
Custom HTTP Headers: Add tracking information or metadata to your log transmissions.
Forwarding Logs, Metrics, and Traces: Send all telemetry data types to Dynatrace.
Deploy Integration Using OpenTelemetry
Setting up a direct integration of telemetry data via Cribl Stream OTLP Destination takes just a few simple steps:
Get API key to ingest telemetry data.
Generate a new token with the appropriate scope. Refer to Dynatrace documentation for details.
Configure Cribl Stream OTLP Destination.
In Cribl Stream, navigate to Data > Destinations and add a new Dynatrace OTLP destination.
Configure your Dynatrace endpoint (SaaS or ActiveGate).
Provide your Dynatrace environment ID and API access token.
Route your telemetry data.
Create routes in Cribl Stream to direct your telemetry data to the Dynatrace OTLP Destination.
Deploy your configuration to start sending data.
Process incoming data with Dynatrace OpenPipeline.
Enrich and contextualize data.
Extract metrics, or create business events from logs, metrics, and traces.