You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve the code coverage for observability in the LitmusChaos components
Description
Enhancing observability across key components, including chaos-runner, chaos-operator, and litmus-go. By adding distributed tracing(span, span attributes, and error tracking) and exporting logs to the Open Telemetry Collector
Prerequisites (preferred but not mandatory)
It would be great if applicants had experience with LitmusChaos and Open Telemetry
What you will do
Instrument Chaos Components with OpenTelemetry
Add instrumentation to chaos-runner and chaos-operator using the OpenTelemetry Go SDK.
Define Span Details
Add span attributes, errors, and events to the litmus-go, chaos-runner, and chaos-operator repo
Configure OpenTelemetry Exporters
Export logs and traces to the Open Telemetry Collector.
Hi, I’m really excited about this project! I’ve been exploring LitmusChaos and have already set up the repository. I have experience working with Go and Java, and in my previous role as a Java developer, I worked on enhancing observability and debugging for a microservices-based application. While I haven’t directly used OpenTelemetry, I’ve worked with similar tools for logging and monitoring, and I’m confident I can quickly get up to speed with OpenTelemetry. I’d love to contribute to instrumenting the chaos-runner, chaos-operator, and litmus-go components. Could you provide more details about the specific metrics or traces you’d like to focus on? Looking forward to contributing!
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!
Hello everyone,
I'm Rashid. I have been contributing to many CNCF projects and improving different codebases. Right now, I am learning about OpenTelemetry (OTEL) and have already contributed to the OTEL Go project.
I think this mentorship will help me understand OTEL better and also give me a chance to contribute to the Litmus project. I would like to apply for this mentorship.
If there are any follow-up steps or requirements for the selection, please let me know.
Thank you!
Title
Improve the code coverage for observability in the LitmusChaos components
Description
Enhancing observability across key components, including chaos-runner, chaos-operator, and litmus-go. By adding distributed tracing(span, span attributes, and error tracking) and exporting logs to the Open Telemetry Collector
Prerequisites (preferred but not mandatory)
It would be great if applicants had experience with LitmusChaos and Open Telemetry
What you will do
Mentors
@namkyu1999
@Adarshkumar14
The text was updated successfully, but these errors were encountered: