OpenTelemetry Weekly Drop-In

Exploring the Future of OpenTelemetry Fleet Management

Summary: Henrik Thierry initiated a discussion on the anticipated OpenTelemetry Weekly Drop-In, focusing on the progression of OpenTelemetry Fleet Management from a read-only state to a full configuration management tool. They invited community members to share their thoughts on the current state and the evolution of the system. The post emphasizes the importance of community engagement in shaping the tool's development.
AI Summary

Hi everyone! As we anticipate the upcoming OpenTelemetry Weekly Drop-In, we're excited to dive into a vital area of discussion: the rollout plan for OpenTelemetry Fleet Management. Currently, the system is in a read-only state, with no full implementation available for managing configurations.

Discussion Prompt: What are your thoughts on the current state of OpenTelemetry Fleet Management as a read-only version? How do you envision its evolution to a fully functional configuration management tool? What steps do you think are crucial for this transition, and how should the community be engaged in this journey? In OTEL it is already(betea) a config engine nut just a readonly version - https://opentelemetry.io/docs/specs/opamp/

We're eager to hear your insights and experiences. Whether you're optimistic about the development or have specific concerns, your input will be invaluable as we aim to shape a tool that best serves our collective needs.

Looking forward to your thoughts!

0 comments