[iris]: link aggregated job log lines to originating task#5174
Merged
Conversation
In the job dashboard's aggregated log view, each line now starts with a T<N> link that navigates to the originating task's detail page. Uses LogEntry.key, which the log store already populates with the task path.
Contributor
rjpower
approved these changes
Apr 25, 2026
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
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.

Job Logs, each line now starts with aT<N>link to the originating task's detail pageLogEntry.key1, already populated by the log store — no backend changestaskIdset and not itself a task path); single-task and system-log views are unchangedFootnotes
entry.sourceis what the producer writes and is typically empty for task logs;entry.keyis the storage key (<taskId>:<attemptId>) set by the duckdb store on read inlib/iris/src/iris/cluster/log_store/duckdb_store.py. ↩