Hello, Hola, Ciao, Hej, Hallo, Witam, مرحباً بكم, שלום everyone! 
Below are the team’s updates for weeks 15 to 18 of 2025. First, as always, let’s introduce the fantastic team and what we’re building.
The Team
The Observability Core team at Canonical consists of Leon (Manager), Jose, Luca, Mike, and Sina.
Together with the Tracing and Profiling and Service Mesh teams, we form the full Observability team, managed by Simme.
The Work
Here’s the main progress we made this pulse:
- (
new) Node-exporter snap is now on the snap store - ( new) Docs for migrate from Grafana-agent to Opentelemetry-collector
- ( new) How to integrate COS Lite with uncharmed applications now mentions:
- How to obtain the CA cert for gagent snap to use
- How to reflect that in the gagent config
- ( new) Opentelemetry-collector TLS
- ( new) Unified Nginx config in coordinated worker charms
- ( new) Deployment validation with juju-doctor
- (
wip) Feature parity with grafana-agent-k8s charm - ( wip) Opentelemetry-collector config best practices
- ( wip) Opentelemetry-collector Loki log forwarding
- ( wip) Spec for charm logging and logging levels
- ( wip) Custom Opentelemetry-collector processor architecture and redaction processors
- ( wip) Doc improvement for migrating from LMA to COS
- ( wip) cos-proxy is creating duplicate alerts on
config_changedevent. - ( wip) all observability charms will soon have a track
2in addition to track1which will replace thelatesttrack. - (
bug) Prometheus alerts not cleared · Issue #196 · canonical/cos-proxy-operator · GitHub - ( bug) Forward internal telemetry with own topology · Issue #30 · canonical/opentelemetry-collector-k8s-operator · GitHub
Feedback welcome
As always, feedback is very welcome! Feel free to let us know your thoughts, questions, or suggestions either here or on our Matrix channel.
That’s all for this time! See you again in two weeks! 
See also