The following configuration example shows how to configure a Collector instance to accept FluentD events via the Fluent Forward protocol and ingest them as OTLP requests into Dynatrace.
See Collector Deployment and Collector Configuration on how to set up your Collector with the configuration below.
receivers:fluentforward:endpoint: 0.0.0.0:8006exporters:otlp_http:endpoint: ${env:DT_ENDPOINT}headers:Authorization: "Api-Token ${env:DT_API_TOKEN}"service:pipelines:logs:receivers: [fluentforward]processors: []exporters: [otlp_http]
Validate your settings to avoid any configuration issues.
For our configuration, we configure the following components.
Under receivers, we specify the fluentforward receiver as the active receiver component for our Collector instance and configure it to listen on specified ports.
Under exporters, we specify the default otlp_http exporter and configure it with our Dynatrace API URL and the required authentication token.
For this purpose, we set the following two environment variables and reference them in the configuration values for endpoint and Authorization.
DT_ENDPOINT contains the base URL of the Dynatrace API endpoint (for example, https://{your-environment-id}.live.dynatrace.com/api/v2/otlp)DT_API_TOKEN contains the API tokenUnder service, we assemble our receiver and exporter objects into a logs pipeline, which will listen on the configured address for FluentD logs and ingest the data into Dynatrace.
Logs are ingested using the OpenTelemetry protocol (OTLP) via the Dynatrace OTLP API and are subject to the API's limits and restrictions. For more information, see Ingest OpenTelemetry logs.