Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Sep 12, 2025

This PR fixes the inconsistency between cluster and database network metrics display formats.

Problem:
Database network metrics were showing throughput in "X of Y" format (e.g., "5.2 MB/s of 10.5 MB/s") while cluster network metrics show just the throughput value (e.g., "5.2 MB/s"). This inconsistency made the UI confusing for users switching between cluster and database views.

Solution:
Updated the database network metrics in DedicatedMetricsTabs.tsx to use the same formatter as cluster metrics:

  • Before: Used formatSpeedLegend({value, capacity}) showing "X of Y" format
  • After: Created formatNetworkThroughputLegend({value}) using formatBytes({value, withSpeedLabel: true}) - same as cluster

Result:
Both cluster and database now consistently display:

  • Utilization: Doughnut chart with percentage (unchanged, was already correct)
  • Throughput: Simple number with speed label (e.g., "5.2 MB/s")

The change is minimal and surgical - only affects the network throughput legend formatter while preserving all existing functionality including the doughnut chart visualization for utilization.

Fixes #2880.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

@astandrik astandrik closed this Sep 12, 2025
Copilot AI changed the title [WIP] fix: write network for db same as for cluster (utilization - dougnut, throughput - number, no of) fix: write network for db same as for cluster (utilization - doughnut, throughput - number) Sep 12, 2025
Copilot AI requested a review from astandrik September 12, 2025 13:44
Copilot finished work on behalf of astandrik September 12, 2025 13:44
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.

fix: write network info for tenant same as for cluster

2 participants