Skip to content

app/vmui: add a span volume by service chart to Trace Explorer - #275

Open
arturminchukov wants to merge 2 commits into
masterfrom
vtui-service-volume-chart
Open

arturminchukov wants to merge 2 commits into
masterfrom
vtui-service-volume-chart

Conversation

@arturminchukov

Copy link
Copy Markdown
Member

Related issue: #263

Returned hits bar chart. Now the visualization section has a tab menu to navigate between different types of charts.
image
image

@arturminchukov
arturminchukov requested a review from jiekun October 8, 2026 10:43

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 45 files

Click Fix with cubic on a comment, or reply @cubic-dev-ai fix this, and cubic writes the fix.

Turn on auto-fix | Re-trigger cubic

Comment thread app/vmui/packages/vmui/src/pages/TraceExplorer/charts/HeatmapChartPanel.tsx Outdated
@arturminchukov
arturminchukov marked this pull request as draft October 8, 2026 11:08
@arturminchukov
arturminchukov force-pushed the vtui-service-volume-chart branch from 122a63a to 91a8379 Compare October 8, 2026 12:31
@jiekun

jiekun commented Oct 8, 2026

Copy link
Copy Markdown
Member

Hi Artur if it's ready for review you can update the status. I saw that it's draft for now but requested for a review.

@arturminchukov

Copy link
Copy Markdown
Member Author

Hi Artur if it's ready for review you can update the status. I saw that it's draft for now but requested for a review.

Yeah, it's my mistake to add reviewers before it's ready for review. I will update the status when I finish fixing the comments from a cubic, and it will be ready for review.

@arturminchukov
arturminchukov force-pushed the vtui-service-volume-chart branch from 91a8379 to 0a4f5f7 Compare October 8, 2026 13:43
@arturminchukov
arturminchukov marked this pull request as ready for review October 9, 2026 06:51

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 46 files

Reply with feedback, questions, or to request a fix.

Turn on auto-fix | Re-trigger cubic

Comment thread app/vmui/packages/vmui/src/components/Chart/BarHitsChart/BarHitsLegend/style.scss Outdated
Comment thread app/vmui/packages/vmui/src/pages/TraceExplorer/hooks/useChartMode.ts Outdated
The new UI dropped the hits chart from the old logs-style page, so there
was no way to see ingestion spikes or how spans split across services.
The chart comes back as a Heatmap / Volume tab above the traces table,
with charts registered in one list so adding another one is local.
@arturminchukov
arturminchukov force-pushed the vtui-service-volume-chart branch from 0a4f5f7 to f1c4d52 Compare October 9, 2026 08:15
@arturminchukov
arturminchukov requested a review from Loori-R October 9, 2026 09:19
@AndrewChubatiuk

Copy link
Copy Markdown
Contributor

what about making tab name more generic, not Volume by service and allow user to select field(s) name by which distribution should be done?

@jiekun

jiekun commented Oct 12, 2026

Copy link
Copy Markdown
Member

As far as I remember this bar chart was for streams. @AndrewChubatiuk 's suggestion sounds good to me, but it's fine to keep the design in this pull request and iterate to customizable (stream) fields. I'll leave the planning stuffs to @arturminchukov .

And it's also fine to not adopt it. I wish to provide useful but clean features on VTUI and leave other complex visualization to Grafana. WDYT?

Signed-off-by: Zhu Jiekun <jiekun@victoriametrics.com>
@arturminchukov

Copy link
Copy Markdown
Member Author

As far as I remember this bar chart was for streams. @AndrewChubatiuk 's suggestion sounds good to me, but it's fine to keep the design in this pull request and iterate to customizable (stream) fields. I'll leave the planning stuffs to @arturminchukov .

Let's keep this PR as is. I think it is already too complex to review. So it will be better to do it in a separate PR if we want to implement it.

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.

3 participants