Skip to content

Feature/timeline diagram#2887

Open
ramonsmits wants to merge 1 commit intomasterfrom
feature/timeline-diagram
Open

Feature/timeline diagram#2887
ramonsmits wants to merge 1 commit intomasterfrom
feature/timeline-diagram

Conversation

@ramonsmits
Copy link
Member

@ramonsmits ramonsmits commented Mar 14, 2026

Adds a timeline view as an alternative to the sequence diagram. This is based on the traces view of jaeger, application insights, zipkin, etc.

However, this nicely only shows the messages processing durations which is a nice highlevel view. It can show the queue time and also see how message are changed if needed.

It also has a tooltip showing a bit of message information. Messages are clickable and will navigate to that message.

Screencast From 2026-03-14 00-58-37

Reviewer Checklist

  • Components are broken down into sensible and maintainable sub-components.
  • Styles are scoped to the component using it. If multiple components need to share CSS, then a .css file is created containing the shared CSS and imported into component scoped style sections.
  • Naming is consistent with existing code, and adequately describes the component or function being introduced
  • Only functions utilizing Vue state or lifecycle hooks are named as composables (i.e. starting with 'use');
  • No module-level state is being introduced. If so, request the PR author to move the state to the corresponding Pinia store.

@ramonsmits ramonsmits force-pushed the feature/timeline-diagram branch from 754f91b to 344f8d1 Compare March 14, 2026 00:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant