You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dosubot[bot] left a comment (cozystack/cozystack#679)
Hi, @matthieu-robin. I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary:
• You suggested adding Loki and Tempo support to improve tracing and log aggregation in the monitoring stack.
• Maintainer tym83 acknowledged your request and planned to discuss it soon.
• User klinch0 shared information about existing VictoriaLogs integration and mentioned Tempo will be discussed in a community meeting.
• Maintainer kvaps noted that traces might be added as a separate application and logging features require further documentation.
• The issue remains unresolved with no recent updates.
Next Steps:
• Please let me know if this issue is still relevant to the latest version of the cozystack repository by commenting here.
• If I don’t hear from you within 7 days, this issue will be automatically closed.
Thank you for your understanding and contribution!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Timur Tukaev (@tym83) The user has confirmed this issue about adding Loki and Tempo support to the monitoring stack is still relevant and needs attention. Could you please assist with the next steps?
Update: the design for this landed as a proposal in cozystack/community#38 (distributed tracing via OTLP), now approved. Implementation is tracked in the epic #3761, and the first PR — a VictoriaTraces backend + Grafana traces datasource in the monitoring stack — is up as #3762.
On the Loki + Tempo ask specifically: the design makes the trace backend pluggable behind an OTLP + Grafana-datasource seam. VictoriaTraces (VictoriaMetrics' own Tempo-counterpart, already shipped by the operator) is the default, with Grafana Tempo a first-class selectable fallback — so this request is covered by the pluggable-backend design rather than hard-wiring Tempo. Leaving this open as the original request until tracing ships.
Activity
tym83 commentedon Mar 6, 2025
Thanks for request. We'll look at this on our meeting in 1-2 days and will come back with answers
klinch0 commentedon Mar 7, 2025
we have https://docs.victoriametrics.com/victorialogs/
Fow using it open Grafana -> Explore -> Choose Vlogs Generic
kubernetes_namespace_name: "cozy-system"or use builderklinch0 commentedon Mar 7, 2025
Regarding Tempo we will discuss it at the community meeting
kvaps commentedon Mar 25, 2025
We discussed to add traces as separate application
[-]Add logs and traces on monitoring stack[/-][+]Add traces on monitoring stack[/+]kvaps commentedon Mar 25, 2025
Logging feature should be described in documentation cozystack/website#113
dosubot commentedon Oct 20, 2025
Hi, Matthieu ROBIN (@matthieu-robin). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!
matthieu-robin commentedon Oct 20, 2025
dosubot commentedon Oct 20, 2025
Timur Tukaev (@tym83) The user has confirmed this issue about adding Loki and Tempo support to the monitoring stack is still relevant and needs attention. Could you please assist with the next steps?
valyala commentedon Dec 1, 2025
As for traces take a look at VictoriaTraces.
tym83 commentedon Dec 1, 2025
Thanks Aliaksandr Valialkin (@valyala)! We're looking at that since it was shown in public space. Is it already production ready?
scooby87 commentedon Aug 11, 2026
Update: the design for this landed as a proposal in cozystack/community#38 (distributed tracing via OTLP), now approved. Implementation is tracked in the epic #3761, and the first PR — a VictoriaTraces backend + Grafana traces datasource in the monitoring stack — is up as #3762.
On the Loki + Tempo ask specifically: the design makes the trace backend pluggable behind an OTLP + Grafana-datasource seam. VictoriaTraces (VictoriaMetrics' own Tempo-counterpart, already shipped by the operator) is the default, with Grafana Tempo a first-class selectable fallback — so this request is covered by the pluggable-backend design rather than hard-wiring Tempo. Leaving this open as the original request until tracing ships.