The goal is to configure grafana-agent in such a way that, when CMR'd with a Tempo backend (for example in cos-lite), grafana will forward any traces it receives to Tempo.
Now you can push any otlp/grpc traces you like to [gagent IP]:4317 and they should show up in Tempo.
TODO:
[ ] - Verify TLS works
[ ] - find out why the HTTP receiver on gagent isn't working (gives me a 404)
[ ] - (grafana-agent): add tracing protocol interface to cos-agent lib:
[ ] - requirer (principal charm) should request a list of protocols much like the tracing requirer
[ ] - provider (gagent itself) should reply with all currently enabled protocols much like tempo does
[ ] - grafana-agent-k8s: implement tracing requirer and provider
The goal is to configure grafana-agent in such a way that, when CMR'd with a Tempo backend (for example in cos-lite), grafana will forward any traces it receives to Tempo.
Testing Instructions
Deploy this bundle on a lxd model:
And this bundle on a k8s model:
Then
juju relate gagent tempo1
Now you can push any otlp/grpc traces you like to
[gagent IP]:4317
and they should show up in Tempo.TODO: [ ] - Verify TLS works [ ] - find out why the HTTP receiver on gagent isn't working (gives me a 404) [ ] - (grafana-agent): add tracing protocol interface to cos-agent lib: [ ] - requirer (principal charm) should request a list of protocols much like the tracing requirer [ ] - provider (gagent itself) should reply with all currently enabled protocols much like tempo does
[ ] - grafana-agent-k8s: implement tracing requirer and provider