Skip to content
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

feat: add project idea for OpenTelemetry Collector Debug exporter #1137

Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions programs/lfx-mentorship/2024/01-Mar-May/project_ideas.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,6 +230,18 @@
- Zhongpei Qiao(@chivalryq, [email protected])
- Upstream Issue: https://github.com/kubevela/kubevela/issues/6435

### OpenTelemetry

#### OpenTelemetry Collector Debug exporter enhancements

- Description: The OpenTelemetry Collector's Debug exporter is not very configurable. Currently the only option is to define `verbosity` at one of three levels: `basic`, `normal`, `detailed`. Users might find it useful to switch certain parts of output on/off, as well as decide where the exporter's output should be sent (currently only `stderr`). Let's add options to the exporter that allow users to configure the exporter's output.
- Expected Outcome: Debug exporter's output can be configured
- Recommended Skills: Go
- Mentor(s):
- Andrzej Stencel ([@astencel-sumo](https://github.com/astencel-sumo/), [email protected])
andrzej-stencel marked this conversation as resolved.
Show resolved Hide resolved
- Juraci Paixão Kröhling ([@jpkrohling](https://github.com/jpkrohling), [email protected])
- Upstream Issue: https://github.com/open-telemetry/opentelemetry-collector/issues/9372

### Prometheus

#### Client_golang CI/CD improvements
Expand Down