fleet/tools/telemetry
Roberto Dip b8b3ef02e4
add services to inspect traces and monitor a local server (#8597)
This adds tooling to debug and inspect traces locally, please refer to the README.md in this commit for more details.
2022-11-21 10:50:10 -03:00
..
docker-compose.yml add services to inspect traces and monitor a local server (#8597) 2022-11-21 10:50:10 -03:00
otel-collector-config.yaml add services to inspect traces and monitor a local server (#8597) 2022-11-21 10:50:10 -03:00
prometheus.yml add services to inspect traces and monitor a local server (#8597) 2022-11-21 10:50:10 -03:00
README.md add services to inspect traces and monitor a local server (#8597) 2022-11-21 10:50:10 -03:00

Telemetry tools

Running the services specified in the docker-compose.yml file will give you access to:

  • The Jaeger UI with both the /monitor (latency, errors, req/sec) and /search (traces) tabs ready to use.
  • A Prometheus server used by Jaeger with enhanced monitoring data provided by OpenTelemetry.

To get started:

  1. Start the necessary services by running docker compose up in this directory.
  2. Start the Fleet server with telemetry enabled and configured with this:
OTEL_SERVICE_NAME="fleet" \
OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4317" \
./build/fleet serve \
  --logging_tracing_enabled=true \
  --logging_tracing_type=opentelemetry \
  --dev --logging_debug

Afterward, you can navigate to http://localhost:16686/ to access the Jaeger UI.