UNCLASSIFIED - NO CUI

Skip to content
Snippets Groups Projects
Commit 16e2a72f authored by Michael Martin's avatar Michael Martin
Browse files

update Tempo notes with the removal of the Tempo-Jaeger-UI

parent 43a3a3bb
No related branches found
No related tags found
1 merge request!5654tempo update to 1.16.0-bb.1
Pipeline #3875275 passed
......@@ -150,7 +150,7 @@ PLATFORM ONE LOKI WARNING:
{{- if and $.Values.jaeger.enabled .Values.tempo.enabled }}
PLATFORM ONE TRACING WARNING:
You have enabled both Jaeger and Tempo Tracing Engines. This is permitted during beta testing of Tempo.
After the beta period, only one Tracing engine will be supported at one time, with Tempo becoming the default supported engine over a direct Jaeger installation. Tempo will deploy with Tempo-Query, a Jaeger frontend with Tempo as the backend.
After the beta period, only one Tracing engine will be supported at one time, with Tempo becoming the default supported engine over a direct Jaeger installation. Grafana has a built-in Tempo data source that can be used to query Tempo and visualize traces.
{{- end }}
{{- if $.Values.addons.mattermost.enabled }}
......@@ -413,4 +413,4 @@ PLATFORM ONE THANOS WARNING:
PLATFORM ONE LOKI WARNING:
BigBang does not support the Loki Distributed deployment mode. For production deployments,
please set your strategy to "scalable" or "monolithic"
{{- end }}
\ No newline at end of file
{{- end }}
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment