From eef5590302f3261957eac2d39492b118b2c8b793 Mon Sep 17 00:00:00 2001 From: Evan Morris Date: Thu, 3 Oct 2024 17:36:21 -0400 Subject: [PATCH] fixing endpoints and adding namespace (#101) --- docs/deployment-guide/monitoring.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/docs/deployment-guide/monitoring.md b/docs/deployment-guide/monitoring.md index 160686c..ee11eed 100644 --- a/docs/deployment-guide/monitoring.md +++ b/docs/deployment-guide/monitoring.md @@ -35,12 +35,17 @@ Translator tools should send telemetry data to shared backend applications deplo Translator applications (clients) should configure their kubernetes deployments to send telemetry data to one of the following, and it should work for CI, test, and prod. -HTTP -jaeger-otel-collector:4318 +The namespace of the collector must be specified (.sri) for applications that aren't deployed to the sri namespace. -gRPC -jaeger-otel-collector:4317 +For some instrumentation libraries, when using the HTTP protocol, it may be necessary to append "/v1/traces" to the collector endpoint. +#### HTTP +http://jaeger-otel-collector.sri:4318 + +#### gRPC +http://jaeger-otel-collector.sri:4317 + +#### Jaeger UI To view telemetry data, the Jaeger UI can be accessed with the following links: * [CI Jaeger](https://translator-otel.ci.transltr.io/search) * [Test Jaeger](https://translator-otel.test.transltr.io/search)