Repository navigation
Conversation
OpenTelemetry log severity text can arrive with provider-specific casing such as Info while the web UI controls and API filters use uppercase values like INFO. That mismatch caused severity filters to exclude visible rows and badges to fall back to the unknown gray style even for known severities. Compare stored log severities case-insensitively, normalize severity groups and facets to uppercase, and render web severity badges from an uppercase display value. This keeps API return values untouched while making filters, stats, facets, and badges consistent across mixed-case inputs.
The previous log view made trace navigation implicit by linking the log body, which blurred the difference between inspecting a log and jumping into its trace context. Trace details also competed for space with a narrow side rail, making dense waterfalls harder to scan while correlating span metadata, events, and logs. Introduce a shared expandable log table with explicit Open in trace actions, URL-backed trace log selection, and collapsible log details. This makes log inspection, trace navigation, and reloadable deep links behave predictably while keeping the active span and tab context intact. Move span detail into a bottom inspector and make the waterfall label column responsive, so the waterfall keeps its horizontal working area and still exposes overview data, attributes, event metadata, and correlated logs. The result is a tighter debugging workflow with clearer navigation and better DX across page widths.
endalk200
changed the title
kitlangton
added a commit
that referenced
this pull request
Sep 2, 2026
Apply the isolated backend severity-casing fix from #12. Match and group ASCII severity variants consistently while preserving original stored and returned log text, and add a matching NOCASE index with filtering, aggregation, facet, and query-plan regressions.
Owner
|
Landed the isolated backend severity-casing fix in #19, with mixed-case search, stats, facet, and persisted-text regressions. I also added a matching NOCASE index to keep direct severity lookups indexed. The full suite passes, including the real-TUI tests. Thanks for including this fix. Leaving this PR open for the UI redesign and badge changes, which were not included in the backend patch. |
Owner
|
The isolated backend severity fix is now published in v0.2.8. Fresh registry installs pass mixed-case search, both statistics paths, facets, and indexed lookup checks while preserving the original log text. The UI redesign and badge changes remain outside this release. Thanks again for including the backend fix in this contribution. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR improves the web UI for inspecting logs, traces, and span-correlated telemetry.
It first fixes severity filtering for logs whose OpenTelemetry severity text arrives with provider-specific casing, such as
Info, while the UI filters use uppercase values likeINFO. Log severity filters, stats, facets, and badges now behave consistently across mixed-case inputs.It then overhauls the trace and log detail workflow. The old log view made trace navigation implicit by linking the log body, and the trace detail view used a narrow side panel that competed with the waterfall for horizontal space. The new flow introduces a shared expandable log table, explicit
Open in traceactions, URL-backed trace log selection, and a bottom span inspector that preserves waterfall width while exposing span metadata, events, attributes, and correlated logs.Changes
Verification
bun run typecheckbun test