adityamparikh opened a new pull request, #262: URL: https://github.com/apache/solr-mcp/pull/262
## What Every HTTP-mode `docker run` in the docs now sets `OTEL_TRACES_URL`, `OTEL_METRICS_URL` and `OTEL_LOGS_URL`. The Compose and Kubernetes examples in `dev-docs/DEPLOYMENT.md` point them at a collector host. The observability guide explains the Docker case. ## Why The OTLP endpoints default to `http://localhost:4318/v1/{traces,metrics,logs}`, which suits `java -jar` and `bootRun` next to the `lgtm` container. Inside a container, `localhost` is the container itself, so the documented commands exported nowhere and logged a connection error on each export attempt: an `ERROR … Failed to export logs` stack trace about every 10 seconds, plus span and metric failures. On Linux, `host.docker.internal` also needs `--add-host=host.docker.internal:host-gateway`, and LGTM has to be started with `OTLP_BIND=0.0.0.0`, because `compose.yaml` publishes 4318 on loopback only. The observability guide says so. ## Verified On Docker Desktop (macOS), the `solr-mcp` image run with these three URLs against `docker compose up -d lgtm` delivered the `CollectionService#checkHealth` trace to Tempo, its WARN log to Loki under the same trace ID, and `http_server_requests_milliseconds_count` to Prometheus, with no export errors. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
