Ensure `gen_ai.*` ops are deprecated or have a corresponding `gen_ai.operation.name`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 50/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- observability
Research direction
The issue names no files, so begin by searching the repository for gen_ai. attribute and operation definitions, and compare them with the gen_ai.operation.name values in the OTel GenAI conventions. Deprecate the ops that have no matching operation name and add the matching values as enum entries. Add a test that asserts every gen_ai.* op maps to an operation name or is deprecated. Done when the test passes and the one existing comment's questions are answered.
Written by the indexing model from the issue text.
Description
Deprecate any that do not have a corresponding gen_ai.operation.name in Sentry's conventions or in OTel GenAI conventions.
If the corresponding gen_ai.operation.name exists in OTel conventions, add the value as a possible enum value.
Create a test to maintain the invariant.
The pattern for GenAI ops is that they consist of the value of the gen_ai.operation.name attribute appended to the literal gen_ai..
- 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
-
Span SpecificationsOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
getsentry/sentry-conventions#659 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
getsentry/sentry-conventions#523 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/sentry-conventions
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
diegosouzapw/OmniRoute#17386 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
area/dashboard kind/bug kind/bug-qa QA/dev-automation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vybestack/llxprt-code#3917 · 1 comment ·
Maintainers usually reply within 1 day
-
api-parity
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
IBM/carbon-components-ember#1157 ·
Maintainers usually reply within 1 day