Add Opentelemetry integration to export monitoring data to third-party APM platforms
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 502
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 715
Description
### Problem
- Currently, https://github.com/apache/maka/blob/main/packages/cli/README.md does not mention any functionality integrated with Opentelemetry.
- For example, https://github.com/anomalyco/opencode will automatically check the following environment variables. Of course, this is in `bash`.
```bash
export OTEL_EXPORTER_OTLP_HEADERS=".........."
export OTEL_EXPORTER_OTLP_ENDPOINT="................"
export OTEL_RESOURCE_ATTRIBUTES="user.name=$(whoami)"
```
- Early discussions can be found at https://x.com/linghengqian/status/2090453772862656944?s=20 .
### Desired outcome
- Add Opentelemetry integration to export monitoring data to third-party APM platforms like https://github.com/apache/skywalking or https://github.com/elastic/apm .
### Alternatives or workarounds
- Uncertain.
Contributor guide
Research direction
Start with packages/cli/README.md and inspect the CLI's existing monitoring or telemetry entry points; the issue does not identify implementation files or tests. Determine how OTEL_EXPORTER_OTLP_HEADERS, OTEL_EXPORTER_OTLP_ENDPOINT, and OTEL_RESOURCE_ATTRIBUTES should be handled, then verify that monitoring data reaches a third-party APM platform such as SkyWalking or Elastic APM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100