Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Debug event level is rendered with red fallback color in issue lists

Closed Beginner friendly
  • Is something wrong?
#4,527 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start by locating the frontend Level type and the ErrorLevel color mapping mentioned in the issue, then inspect how the issue-list severity indicator uses them. Verify the existing issue-list or severity tests if present, and confirm that a debug event keeps its Level: Debug tooltip while the indicator uses an explicit non-error color.

Written by the indexing model from the issue text.

Description

Stale Waiting for: Community
Image
Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

  1. Send an event with the event level set to debug.

    Example:

    {
  "level": "debug"
}

  2. Open a view that renders the issue list, for example the Release details page.

  3. Locate the debug-level issue and hover over the severity indicator.

  4. Observe that the tooltip correctly displays Level: Debug, while the vertical severity indicator is rendered red.

Expected Result

Events with level = "debug" should be recognized as a supported event level by the frontend and should not use the red fallback/error color.

Ideally, debug should have an explicit severity color mapping, for example the same low-severity/accent color currently used for info / sample.

The tooltip should continue to display Level: Debug.

Actual Result

The tooltip correctly displays Level: Debug, but the severity indicator is rendered red.

The apparent root cause is that debug is missing from the frontend Level type and from the ErrorLevel color mapping.

The frontend type is:

export type Level =
  'error' | 'fatal' | 'info' | 'warning' | 'sample' | 'unknown';

debug is missing.

This makes a valid debug-level event visually appear as a high-severity/error event.

The backend itself recognizes debug as a valid log level.

Product Area

Issues

Link

No response

DSN

No response

Version

26.6.0 (Source inspection indicates that the same frontend behavior is still present in 26.9.0. I have reproduced the issue on 26.6.0; the 26.9.0 statement is based on source inspection.)

Dominant language
Shell
Stars
9.6k
Forks
2k
Avg merge
1d 20h
Merged PRs (30d)
26

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/self-hosted

All issues in getsentry/self-hosted

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.