4 ms·
As a maintainer and end-user, my answer to this is...yes and no. It's important to clarify that, stability - something mentioned in the article - has several ma
by phillipcarter 3y ago
As a maintainer and end-user, my answer to this is...yes and no. It's important to clarify that, stability - something mentioned in the article - has several major definitions:
- Stability in the specification
- Stability in semantic conventions
- Stability in the protocol representation
- Stability in SDKs that can generate data
- Stability in the Collector that can receive, process, and export that data
Unfortunately, for many people, they may interpret "stable" in one of those categories as "stable for everything", and then get really annoyed when they find their language doesn't actually have stable support (or any support!) for that concept.
What I'm most proud of in 2023 is all of the little things we made progress on with components that engineers have to materially deal with. On the website, we documented what feels like a million little things and clarified tons of concepts that people told us were confusing. Across all the SDKs, we fixed tons of little bugs, added more and more instrumentations, and completed the unsexy work to make metrics generation stable across most of our 11+ languages. The Collector added oodles and oodles of support for different data sources, and OTTL went from a neat component to a rock-solid general-purpose data transformation tool.
There's so much more work to do, but I'm really happy about the progress.