Setting recommended ingester settings from grafana Github, cleaning up values, adding queryUI templates
Noticing some slight inconsistencies between traceIDs showing up attached to Loki logs and actually being available to view in Tempo.
-
Addressing those reliability issues with an NP to allow ingress on
tempo:9411in namespace (to recieve traces from each apps istio-proxy sidecars). -
Enabling zipkin endpoint listener on
0.0.0.0:9411 -
Enabling searching via tempoQuery (so it's actually used) which turns out to be JaegerUI itself.
-
Adding in values/templates/networkPolicies to facilitate external connections through istio to tempoQuery(Jaeger) UI via
https://tracing.bigbang.dev -
Cleaning up comments in values file that we control
Reviewing their documentation pages and recommended configuration on Github, making sure our helm chart makes use of their recommendations.
exporting of traces is a lot better with this configuration, but still seeing magnitudes more of traces in Loki compared to Tempo.
Merge request reports
Activity
added statusdoing teamXForce tempo labels
assigned to @ryan.j.garcia
added 22 commits
-
b43fd00a...5f77b45a - 19 commits from branch
main - 8b7c1e7a - Setting recommended ingester settings from grafana Github
- 59b2b4d2 - Pushing up some otel changes
- 4accd139 - Rebasing off main
Toggle commit list-
b43fd00a...5f77b45a - 19 commits from branch
added 1 commit
- 1318644c - re-enabling zipkin ingester because it was there b4
added 1 commit
- fb82a896 - Some recs for prod, VS addition, query-ui enabled by default
added 1 commit
- 7314cd6c - Adding 9411 zipkin ingress NP similar to jaeger
added kindbug statusreview labels and removed statusdoing label
requested review from @michaelmartin
requested review from @echuang and @micah.nagel
mentioned in commit 664fd20b
