Anras573 / Anras573/AIchemist-UI
Connect to external otel receiver
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 10m
- Merged PRs (30d)
- 9
Description
The current approach to traces might not be adequate in every situation, and since at least one of the agent SDKs support connecting to an external otel receiver, the implementation should be straight forward.
The optimal solution would also include a docker (or podman) compose file with jaeger, so the developers can easily spin up jaeger and test the otel features.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the current trace implementation and the agent SDK integration in the TypeScript/Electron application. Check how the application can target an external OTEL receiver, then review the proposed Docker or Podman Compose setup with Jaeger. Done means traces can be sent to the external receiver and developers can run Jaeger locally to verify the OTEL features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, electron, typescript
- Domain
- desktop, devops, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100