Files
compliance-scanner-agent/otel-collector-config.yaml
Sharang Parnerkar c61497420a Add OpenTelemetry tracing and log export via OTLP
Shared telemetry init module in compliance-core (behind `telemetry` feature)
sets up OTLP/gRPC export for traces and logs when OTEL_EXPORTER_OTLP_ENDPOINT
is set. Falls back to console-only output when unset.

Both agent and dashboard now use the shared init. Docker Compose includes
an OTel Collector service with a config template for SigNoz, Grafana
Tempo/Loki, Jaeger, etc.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-07 23:51:08 +00:00

53 lines
937 B
YAML

receivers:
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4317
http:
endpoint: 0.0.0.0:4318
processors:
batch:
timeout: 5s
send_batch_size: 1024
exporters:
# Log to stdout for debugging
debug:
verbosity: basic
# Configure your backend below. Examples:
#
# SigNoz:
# otlp/signoz:
# endpoint: "signoz-otel-collector:4317"
# tls:
# insecure: true
#
# Grafana Tempo (traces):
# otlp/tempo:
# endpoint: "tempo:4317"
# tls:
# insecure: true
#
# Grafana Loki (logs):
# loki:
# endpoint: "http://loki:3100/loki/api/v1/push"
#
# Jaeger:
# otlp/jaeger:
# endpoint: "jaeger:4317"
# tls:
# insecure: true
service:
pipelines:
traces:
receivers: [otlp]
processors: [batch]
exporters: [debug]
logs:
receivers: [otlp]
processors: [batch]
exporters: [debug]