Hi Amit, exactly, that's the real shift here. Once observability sits at the platform level instead of being something every team has to remember to add, it stops being a "did we remember" problem and just becomes enabled by default. The OpenTelemetry Collector is what makes that practical for something as varied as CI tooling: it's language-agnostic, so it doesn't matter what a team's workflow is written in, and receivers like the one this post covers mean a new telemetry source can be added without asking anyone to touch their own code. Teams can even contribute their own receiver to the OSS project if there's a source that doesn't exist yet.

Exactly. The “enabled by default” part is what makes this approach really scalable.

And I think there's another benefit: once telemetry is standardized at the platform level, teams can spend their time interpreting the signals rather than figuring out how to generate them.

That shift—from instrumentation as a team responsibility to observability as a platform capability—is where the real leverage comes in.