Lucas Manuel Rodriguez
f674cf145c
Had to use `tools/telemetry` to smoke test https://github.com/fleetdm/fleet/pull/49957. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Enhancements** * Updated telemetry collection to use the standard OpenTelemetry Collector image. * Improved trace forwarding to Jaeger and added clearer diagnostic output. * Reworked span-to-metrics processing for more reliable telemetry metrics. * Updated telemetry endpoints and pipeline routing for improved connectivity. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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:
- Start the necessary services by running
docker compose upin this directory. - 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
Afterwards, you can navigate to http://localhost:16686/ to access the Jaeger UI.
Alternatives
For a more full-featured observability platform that includes traces, metrics, and logs in a single UI, see SigNoz.