-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traces do not get correctly exported to tempo when mysql-router is related to grafana-agent #195
Comments
Confirmed that the issue exists with
|
…#180) ## Issue We are unable to relay traces through grafana-agent due to canonical/grafana-agent-operator#195. However, in the meantime, we would like to update the charm tracing libs as they now reside in `tempo_coordinator_k8s` ## Solution Update location of charm tracing libs
Important to note that mysql-router is a subordinate charm. I just confirmed that in the same model, if you relate mysql charm to grafana-agent via |
It looks like tracing endpoint wasn't returned correctly in the tempo_ha branch of mysql-router. I've passed the required fixes to @shayancanonical, after the fixes traces get exported to tempo: |
Bug Description
Since mysql-router is a subordinate charm, we first relate grafana-agent with the principal charm (on the
juju-info
interface). Then, we relategrafana-agent:cos-agent mysql-router
. When we do so, I can see loki logs trickling through to grafana/loki. However, I am unable to see traces from mysql-router showing up in tempo.Upon further inspection, I noticed an error trace in the debug-logs, which I have included below
To Reproduce
feature/tempo_ha
in mysql-router (https://github.com/canonical/mysql-router-operator/tree/feature/tempo_ha)Environment
Juju: 3.5.4
LXD: 6.1
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: