Support for tail based sampling?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- java
- Domain
- observability
Research direction
No files, tests, or entry points are named. Start by reviewing the existing sampling and telemetry behavior in ApplicationInsights-Java, then clarify how tail-based rules should handle slow dependencies and failed spans or traces before implementation can be considered done.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
We want to have more control over sampling in our application.
- Don't record dependencies that are less than 100ms(successpath), but record everything that is >100ms. (numbers are arbitrary)
- Record 100% failed telemetry(span/trace/etc) as described here https://github.com/microsoft/ApplicationInsights-Java/issues/3511 . Recording only exception doesn't give much context if everything surrounding it is sampled.
We want to lower our costs but also have useful telemetry, I believe having tail based sampling would greatly help us.
Describe the solution you would like
Add support for tail based sampling to have more control?
Describe alternatives you have considered
Describe any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
- Dominant language
- Java
- Stars
- 327
- Forks
- 222
- Avg merge
- 22h 34m
- Merged PRs (30d)
- 14
Contributor guide
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.
More from microsoft/ApplicationInsights-Java
-
microsoft/ApplicationInsights-Java#4851 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/ApplicationInsights-Java#4817 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/ApplicationInsights-Java#4770 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/ApplicationInsights-Java#4729 · 121 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in microsoft/ApplicationInsights-Java
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cryptomator/hub#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
johanhaleby/occurrent#1120 ·