-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC: Telemetry in Headlamp with OpenTelemetry #2799
Comments
Hi @illume, this sounds great . I am eager to contribute to the project ! |
Hello @illume , |
Hey, @illume "I’m excited to contribute to integrating OpenTelemetry into Headlamp, leveraging my experience with Golang, TypeScript, and observability tools like Prometheus. I’m eager to enhance Headlamp’s debugging and monitoring capabilities while delivering thorough documentation and outreach materials." |
@illume While going through the OpenTelemetry documentation, I came across various metrics and traces that can be collected. I wanted to ask: What are the most critical metrics or traces we should prioritize for the backend (Golang) and frontend (TypeScript) to ensure the telemetry implementation provides the most value to Headlamp users? |
Hey, @illume, I hope you’re doing well. I came across the OpenTelemetry implementation project for Headlamp and found it really interesting. Given my background in Go and DevOps, I believe this would be a great learning opportunity for me while also contributing meaningfully to the project. I’d love to work on integrating OpenTelemetry, implementing metrics, and documenting the process. Please let me know if I can take this up for the upcoming LFX Term 1. Looking forward to your thoughts! |
Hey everyone, I'm Sonal! Recently, I've been contributing to the OTEL Collector and OTEL Collector Contrib. I'm really excited about this project and believe there's so much to learn from it. By the way, are there any upcoming meetings or briefings about the project? I'd love to contribute more! |
Hey @illume , @yolossn , and @knrt10 ! I’m excited about this project and have submitted my application for LFX 2025. OpenTelemetry integration in Headlamp looks like a great opportunity to apply my skills in Golang, TypeScript, and observability tools. I’m eager to learn, contribute, and work with the community. Looking forward to your guidance! |
Hello everyone. Anyone who wants to apply for LXF project should see this and apply through here: https://mentorship.lfx.linuxfoundation.org/project/d961bfc7-00e1-4c05-bf1a-f9c7ddf1756a cc @Priyanshi763 @harshita9104 @btwshivam @vickybesra @sonalgaud12 @infinity1729 |
@btwshivam wrote:
Good question. I think iterating on the project, and asking the community for feedback will give the best answer. Also looking at what other similar projects find valuable would give some valuable insights. |
Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.
The lack of integrated telemetry in Headlamp makes it challenging to monitor and analyze application performance and behavior. This feature is crucial for identifying issues, optimizing performance, and ensuring a smooth user experience.
Describe the solution you'd like
Implement OpenTelemetry in Headlamp to collect and analyze telemetry data. This includes:
What users will benefit from this feature?
Operators deploying and running Headlamp will be able to debug any problems with Headlamp and see if it is running ok.
Are you able to implement this feature?
No, I can help.
Additional context
The implementation will be broken down into three phases:
Preparation and Learning (3 weeks)
Implementation (6 weeks)
Documentation and Outreach (3 weeks)
The text was updated successfully, but these errors were encountered: