Stéphane Tailland
2a695da0dd
Prometheus, Loki and Tempo become tools the assistant can call, so the telemetry can be questioned rather than browsed — which is where the trace dashboard kept running out of road. Verified: LibreChat initialises the server in 168ms and loads its tool list. No oauth block, unlike every other server here. The others sit behind a Kong gateway enforcing openid-connect; this one is reached directly on the cluster network and authenticates to Grafana with a service account token of its own. LibreChat passes no user identity along, so there is no per-user scoping: every LibreChat user gets the same full read of all telemetry, including the Kong audit records and the LLM prompts now captured there. That is stated in the config rather than left to be discovered, and it is the reason to move this server behind a gateway like the others. allowedDomains gains the first http:// and first cluster-internal entry; without it LibreChat's SSRF protection refuses the address. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>