As per title, otel collector should be configured to send received traces to jaeger.svc. Not before T344253: jaeger is configured to receive traces from production is completed
Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T340551 distributed tracing epic | |||
| Open | None | T320549 distributed tracing v0 [minimum viable] | |||
| Resolved | fgiunchedi | T343302 otel collector is configured to send traces to jaeger |
Event Timeline
Change 946518 had a related patch set uploaded (by Filippo Giunchedi; author: Filippo Giunchedi):
[operations/deployment-charts@master] otel-collector: export traces to jaeger
Change 946551 had a related patch set uploaded (by Filippo Giunchedi; author: Filippo Giunchedi):
[operations/deployment-charts@master] aux: add grpc/http ports for jaeger collector
Change 946551 merged by Filippo Giunchedi:
[operations/deployment-charts@master] aux: add grpc/http ports for jaeger collector
Change 946518 merged by Filippo Giunchedi:
[operations/deployment-charts@master] otel-collector: export traces to jaeger
Change 954909 had a related patch set uploaded (by Filippo Giunchedi; author: Filippo Giunchedi):
[operations/deployment-charts@master] otel-coll: allow outbound 30443/tcp
Change 954909 merged by Filippo Giunchedi:
[operations/deployment-charts@master] otel-coll: allow outbound 30443/tcp
I've verified that test traces sent to otel-col in k8s show up in jaeger ui, resolving