Collecting statistics about dropped spans
- Dominant language
- Gherkin
- Stars
- 427
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
As described in [this spec](https://github.com/elastic/apm/blob/master/specs/agents/handling-huge-traces/tracing-spans-dropped-stats.md), agents should collect statistics on dropped spans.
## Spec issue
- [x] https://github.com/elastic/apm-server/issues/5851
## Agent issues
- [x] https://github.com/elastic/apm-agent-java/issues/2084 
- [x] https://github.com/elastic/apm-agent-dotnet/issues/1476 
- [x] https://github.com/elastic/apm-agent-go/issues/1113 
- [x] https://github.com/elastic/apm-agent-php/issues/536 
- [ ] https://github.com/elastic/apm-agent-ruby/issues/1150 
- [ ] https://github.com/elastic/apm-agent-nodejs/issues/2302 
- [x] https://github.com/elastic/apm-agent-python/issues/1310
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked tracing-spans-dropped-stats.md specification, then review the unchecked Ruby and Node.js agent issues listed here. Compare their status with the checked agent issues and the completed spec issue; done means the remaining agent work is addressed and the corresponding checklist entries can be marked complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, node.js, php, python, ruby
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100