on 19 Aug 2025 12:00 PM
This troubleshooting article will help resolve some common issues faced while ingesting logs into Dynatrace via Fluent Bit.
logs.ingest
(Ingest Logs) scope.kubectl get pods -n <namespace>
kubectl edit configmap fluent-bit -n <namespace>
[OUTPUT]
name http
match *
header Content-Type application/json; charset=utf-8
header Authorization Api-Token {your-API-token-here}
allow_duplicated_headers false
host {your-environment-id}.live.dynatrace.com
Port 443
URI /api/v2/logs/ingest
Format json
json_date_format iso8601
json_date_key timestamp
tls On
tls.verify On
kubectl logs <fluent-bit pod-name> -n <namespace> | grep {your-environment-id}
You'll get similar logs like this repeating.[timestamp][ info] [output:http:http.2] {your-environment-id}:443, HTTP status=204
An HTTP status of 204 means the request was accepted.
Other possible responses include '401 Unauthorized' if you used a bad token, or any of the responses listed here.
If none of the steps in this article resolved the issue, open a chat or support ticket and provide the following details:
kubectl logs <fluent-bit pod-name> -n <namespace> > pod-logs.txt
kubectl describe pod <fluent-bit pod-name> -n <namespace> > pod-describe.txt
kubectl get configmap <fluent-bit configmap-name> -n <namespace> -o yaml > configmap.yaml