OpenTelemetry Monthly Update: March 2020
March’s update is somewhat short, both because last month’s update was posted so recently, and because of the beta announcement taking place on Monday. As always, this month’s topics were discussed at the monthly community meeting, which you can find on the community calendar.
Beta on Monday
We are ready for beta! Final touchups are being made to the Go, Java, JavaScript, and Python SDKs, as well as the collector. The Erlang SDK and Java auto-instrumentation agent will also be going beta on Monday, and the .Net SDK will not be far behind.
This is an exciting time for everyone involved in OpenTelemetry, and for developers who have been waiting to start evaluating OpenTelemetry within their organizations or to begin producing integrations for it. An especially big thank-you is needed for the maintainers and contributors for each component going Beta — we couldn’t have done it without you!
Dev Stats
Andrew walked attendees of the monthly community meeting through the CNCF’s developer stats dashboard, which presents information like the time to engagement or time to merge aggregated across each CNCF project’s pull requests. There’s a lot to explore here, and we can use information like this to track the health of our community.
If you’re interested in how this information is generated, the code is available in the CNCF’s devstats repository.
Registry
In addition to hosting a project description and documentation, our website also hosts the OpenTelemetry registry, which lists the SDKs, agents, integrations, exporters, and other components that operate within the OpenTelemetry ecosystem. The registry is especially useful for finding components that aren’t included in the main repositories — for example, a developer might search for ‘JavaScript’, ‘Express’, and ‘Prometheus’ to find the components that they need to analyze HTTP latency for their JavaScript application in Prometheus.
Adding a component to the registry is simple and involves adding a ~15 line markdown file to the website repository. If you maintain a component of OpenTelemetry that isn’t already present in the registry, please add it today!
Logs SIG
Tigran created an OpenTelemetry logs SIG that aims to add logging functionality to OpenTelemetry. We’re currently completing a proposal for the SIG’s purpose, intended work, and spec / API / SDK / Collector requirements which we’ll share out next week.
The Logs SIG meets each Wednesday, alternating between 10:00 AM PT and 4:00 PM PT, and the meetings are listed on the community calendar. Please join if you’re interested in this subject and aren’t already included!
