telemetry: log records emitted without SeverityText
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 7m
- Merged PRs (30d)
- 6
Description
The Recorder.Info and Recorder.Error methods in telemetry/log.go call r.log(ctx, log.SeverityInfo, ...) and r.log(ctx, log.SeverityError, ...), which sets SeverityNumber on the record but leaves SeverityText empty.
The OTel log data model has both fields for a reason — SeverityNumber is the normalized enum used for querying and filtering, while SeverityText is the human-readable label displayed by backends. Display tooling (e.g. BetterStack) renders the text field as the level badge and ignores the number for display purposes.
Since we choose the severity directly, both fields should always be set together:
rec.SetSeverity(severity)
rec.SetSeverityText(severity.String())
The fix belongs in the r.log helper in telemetry/log.go.
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.
Research direction
The severity is handled by the r.log helper in telemetry/log.go; start there and inspect how Recorder.Info and Recorder.Error reach it. Ensure emitted records contain matching numeric and text severity fields, then verify the record exposes both values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100