Hello, Hola, Ciao, Hej, Hallo, Witam, مرحباً بكم ,درود, שלום everyone! 
Here are some of the works of the mighty Observability Core team during pulse 11 of 2026.
The Team
As always, a quick reminder on our team members! On the Core team we have:
Together with the Tracing and Profiling and Service Mesh teams, we combine to create the greater Observability team, managed by Simme.
The Work
Fix: Grafana long DB name issue. This issue resulted in Grafana’s readonly replica of its Postgresql DB to not be created successfully. We have started using a different DB naming strategy to avoid this issue.
To help users easily refresh their Grafana charms without losing data (see the item above), we have also added a doc!- Fix: Loki workload tracing issue. Loki upstream version 3.7.1 currently has a regression which makes workload tracing unable to start. We have an upstream contribution in review. Until that fix is implemented, we have patched our rock to enable workload tracing.
- Fix: Mimir worker restart loop due to coordinator writing some fields out of order. The Mimir coordinator is responsible for writing the worker configuration to relation data. Any change in relation data causes a restart in the worker. Due to a small bug related to ordering, fixed in this pulse, the coordinator would sometimes write new relation data to relation data, causing an unnecessary restart.
- Fix: Remove constraints for Otelcol suborinate charm. This fix has also been backported to track 2.
- Doc items concerning moving our docs from Charmhub Discourse to our RTD site across all of our charms. See Alertmanager as an example.
- Fix: Correct hook names for certain relation hook events.
Feature: we have added TF support for TF Juju Provider v2 and also Juju 4 across our different charms. See Alertmanager as an example.
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! 