Hi everyone!
Below are the team updates for the Tracing & Profiling part of the amazing Observability team. We’re back from Frankfurt where we all gathered to plan out the next 6 months (did you see the Engineering Sprint recap?). We’ve already started on some of the most exciting stuff.
We are 
What we’ve done
- we extended grafana-cloud-integrator with tracing support. Now you can use it to send traces to Grafana Cloud!
- if you integrate a charm with more than one unit over tracing with grafana-agent, you shouldn’t see relation-related errors anymore.
- whitespace characters in parca-scrape-target config won’t cause errors anymore
- k8s service url is now advertised by tempo-coordinator, helping with scaling the coordinator
- we’ve extracted cos-coordinated-workers as a separate project and a pypi package. We’re using it as a common shared package and a pattern for all our HA charms.
- @mmkay went to GrafanaCON 2025 where he presented using the Canonical Observability Stack on a home server to gather signals from airplanes, ships and Meshtastic devices. Stay tuned for a recording that should be available soon on Grafana’s social media!
Sneak peeks
We’re collaborating with the great Charm Tech team on integrating charm tracing capabilities in ops. Juju topology labels are now in ops[tracing] and we’re working on providing a smooth experience for anyone transitioning from charm_tracing library to ops[tracing].
We’re also starting work on Charmed Pyroscope which is the OpenTelemetry-focused, HA tool for profiling by Grafana. More to follow in near future!