Hello, Hola, Ciao, Hej, Hallo, Witam, مرحباً بكم ,درود, שלום everyone! 
Welcome to another pulse report by the one and only Observability Core
team! Here are some of the works of our team from weeks 10 and 11 of 2026, corresponding to pulse 5.
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
A Cos Tool issue occurring due to an unexpected character error is fixed!
In Script Exporter, the prometheus_config_fileis now optional instead of mandatory.
A fix has been implemented to the way the Opentelemetry Collector machine charm allows setting the port for the internal metrics endpoint.
To support our OTLP-related work (see items below), we had to implement a minor fix in cos-lib, related to the OfficialRuleFileFormatfor rules.
All charms that rely on Cos Tool have bumped their Cos Tool version.
As promised in our last pulse report, we’ve implemented a fix in the Opentelemetry Collector machine charm which enables dynamic port allocation for Node Exporter.
A major point of focus for us during pulse #5 was finalizing our work on the OTLP interface and moving it to the Charmlibs mono-repo. This was successfully accomplished during pulse #5 and version 0.1.0 of the OTLP interface is now available. Many thanks to @james-garner for the help in reviewing the work!
With the OTLP interface released, the machine and Kubernetes charms for Opentelemetry Collector now support OTLP sending and receiving telemetry over OTLP, as well as forwarding alerting and recording rules for telemetry sent using this protocol.
With the continued help of @yanisa-hs, we are progressing with our efforts into revamping of our charm/stack documentation, aligning on README and CONTRIBUTING templates, and generally exploring ways to up our docs game. Thanks Yanisa for your help with this work!
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! We’ll see you again in two weeks with exciting updates! ![]()