Fill in span name conventions for known spans
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- observability
Research direction
Start with the linked CON-43 follow-up, the Develop docs, and existing Sentry conventions to build a complete list of known span operations. Compare each operation with OpenTelemetry conventions and current SDK behavior, then identify spans such as ui that need new low-cardinality conventions. Done means the complete operation list is captured as subtasks and agreed naming guidance is documented.
Written by the indexing model from the issue text.
Description
Follow-up to CON-43. We need to fill in conventions for all known spans! This is a lot of work, and has a few aspects:
- Discovering all the current known spans. The easiest way to do this is probably to refer to our own documentation (in the Develop docs and in our own conventions) as well as fetching a sampling of
opfields from Sentry usage - Documenting how to create a
namefor each known span operation. This can be done through some combination of checking OpenTelemetry conventions, and checking what current SDKs are doing - Creating and agreeing on conventions for spans that don't have an OpenTelemetry equivalent (e.g.,
uispans). We'll need to come up with sensible low-cardinality names for these spans.
- figure out a complete list of span operations and add them as sub-tasks
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 6
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 63
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 getsentry/sentry-conventions
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
getsentry/sentry-conventions#732 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
getsentry/sentry-conventions#731 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
getsentry/sentry-conventions#730 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
getsentry/sentry-conventions#709 · 1 comment ·
Maintainers usually reply within 1 day
-
Span SpecificationsOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
getsentry/sentry-conventions#659 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/sentry-conventions
Similar issues
-
frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ranxianglei/billion-context#4172 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
awslabs/threat-composer#362 ·
Maintainers usually reply within 1 day
-
Area/Cloud Needs Triage Type/Bug
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
wso2/product-integrator#2847 ·
Maintainers usually reply within 1 day