filelog receiver
11 complete collector configs on this site use the filelog receiver. Each is a whole file, validated with otelcol-contrib v0.161.0.
- Tail a log fileShip an application log file to your backend, and keep your place in it across collector restarts.Logs
- Parse JSON log lines into attributesTurn each JSON log line into attributes you can filter and group by, keeping the original line as the body.Logs
- Parse nginx access logs into semantic conventionsTurn nginx combined-format access log lines into OpenTelemetry semantic-convention attributes, with typed status codes.Logs
- Parse Apache access logs into semantic conventionsTurn Apache combined-format access log lines into semantic-convention attributes, with typed status codes and sizes.Logs
- Parse key=value log linesTurn logfmt-style key=value lines into attributes, quoted values with spaces included.Logs
- Use the timestamp in the log line, in the right time zoneStamp each record with the time written in the line, not the time the collector read it - in the zone it was written in.Logs
- Map your log levels to OpenTelemetry severitySet severity_number from your level field, including names like warning, err and crit, so severity filters work.Logs
- Collect Kubernetes pod logs (DaemonSet)Every container's logs from every node, with namespace, pod and container read from the log path - one DaemonSet, no sidecars.Logs
- Parse IIS W3C access logs into semantic conventionsEvery IIS request as a structured log: method, path, query, status, sizes, time taken and user agent, with the request's own UTC timestamp.Logs
- nginx access logs to Elasticsearch, parsed into semantic conventionsTail nginx, parse every request into semantic-convention fields with typed status codes, and index it in Elasticsearch.Logs
- Kubernetes pod logs to Loki, enriched with deployment and clusterEvery pod's logs into Loki over OTLP, labelled with namespace, pod, container, deployment, node and cluster.Logs