zmuxuny opened a new issue, #6748:
URL: https://github.com/apache/rocketmq-dashboard/issues/6748

   ### Before Creating the Bug Report
   
   - [x] I have searched the [open 
issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository 
and believe that this is not a duplicate.
   
   - [x] This is a defect in RocketMQ Studio, not a usage question and not a 
defect in another Apache RocketMQ repository.
   
   - [x] I can reproduce this on the current `master` branch, or I have stated 
the exact version I am running below.
   
   
   ### Studio Version
   
   rocketmq-studio a92c23144408cdf5729707050e9ecd9b75f1bad0
   
   ### Runtime Environment
   
   Linux, Node24.19.0, Vitest/jsdom; real MetricsExplorer component with 
controlled metric responses.
   
   ### Connected RocketMQ Cluster
   
   No live cluster needed for reproduction. Any valid fractional metric result, 
including low rates or custom PromQL durations in seconds.
   
   ### Build Toolchain
   
   _No response_
   
   ### Describe the Bug
   
   The shared formatMetricValue formatter hard-caps output at two decimal 
places. Nonzero scalar values below 0.005 render as zero in graph labels, the 
latest-value legend and series details, hiding meaningful measurements.
   
   ### Steps to Reproduce
   
   1. Return a valid scalar series with values 0.001 and 0.004 at different 
timestamps.
   2. Observe the Y-axis labels and latest-value legend.
   3. Open series details, which use the same formatter.
   
   ### What Did You Expect to See?
   
   Preserve useful precision or scientific notation so small nonzero values are 
distinguishable from zero and one another.
   
   ### What Did You See Instead?
   
   All three distinct nonzero Y-axis ticks read 0, and the legend reads 0 
messages/s. A real-component regression fails because three distinct tick 
values collapse to one displayed label.
   
   ### Additional Context
   
   Source: web/src/components/MetricsExplorer.tsx formatMetricValue 
around103–104, used by axis/legend/details. All-state issues/PRs searched for 
metrics precision/decimal/round/formatMetricValue. #6429/#6434 concern invalid 
blank samples parsed as zero; #6650 concerns backend TPS integer truncation. 
This is an independent UI formatting loss on already-valid fractional values.
   
   ### Are You Willing to Submit a Pull Request?
   
   - [x] Yes, I am willing to submit a pull request.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to