Getting traceloop qualified on Elastic
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 11
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Hello we noticed that Elastic was not on your list of supported and tested destinations. We offer native OTel support, and are now heavy contributors to OTel (ECS donation, Profiling agent donation, and more). We don't require a specific SDK or collector. You can instrument directly with standard Otel (python, java etc) and set the endpoint with auth to an elastic stack. Traces, metrics etc all show up natively in our APM capabilities.
https://www.elastic.co/observability-labs/blog/tag/opentelemetry
https://www.elastic.co/observability-labs/blog/getting-started-opentelemetry-instrumentation-sample-app
https://www.elastic.co/observability-labs/blog/auto-instrumentation-python-applications-opentelemetry
https://www.elastic.co/observability-labs/blog/manual-instrumentation-python-apps-opentelemetry
and more.
What can we do to help you get us supported on your list?
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
No file, test, or entry point is named. Start by locating the repository's supported and tested destinations list, then review the linked Elastic OpenTelemetry resources and the unresolved discussion. Done means the required qualification evidence and scope are agreed and the documentation reflects the decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- documentation, observability-sre
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100