-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Displaying units on charts #16610
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
Dear bot, I believe this feature would still be a great addition and hasn't been implemented yet in current |
My use case is - I want to display bytes (how much memory my applications are using) and now it is misleading when it format it like |
I want to display bytes (how much size an s3 prefix is using) and now it is misleading when it format it in billion or trillion like 900B or 1.5T which isn't accurate. |
is there any workaround? |
We are moving a few of our monitoring charts from Grafana to Superset dashboards and would like to see proper support for units like Grafana has. At the moment we can’t for example show Terrabytes or Gigabytes. |
@GerbenvdHuizen I was able to show Terrabytes or Gigabytes in one of our line charts using Y-Axis format as shown in this snippet. Hope this helps. |
@mdeshmu Whilst that technically answers a specific version of this question it's not really comparable to Grafana, where pretty much all units you'll ever need are all present and easily selectable (and you can also add a custom unit if need be). |
There is a concept of |
Prefix/suffix for currencies has been added to many charts. We can potentially add more options to make it more generic, e.g. having "Currencies" be one option, alongside others (e.g. filesize, measurements, arbitrary string, etc) |
Wondering if that came up in design discussions for the prefix/suffix control @kgabryje |
Howdy, folks - I'd be happy to take a stab at this, at least for the Big Number control. As a first time contributor, where and what types of changes would I be looking to do? Particularly looking for where the various number formats/prefixes/suffixes are defined. |
Vote for this feature!!! Our clients are world wide. This is a high demand feature from our internal customers to switch unit, i.e. from imperial to metric. It will be very cumbersome to work around and implement such conversion in a converted dataset in the same dashboard for >100 tables. Such unit conversion feature has been frequently brought up from our internal customers in the past 2 years. |
Also vote for this feature. This is really missing and would help a lot. |
Is your feature request related to a problem? Please describe.
When creating a chart, I would like to be able to specify the unit of the numbers plotted. For example to add the unit
°C
to the Y-axis values of a temperature over time chart created with theTime Series Line
chart.Currently when customising numbers on charts it’s only possible to change the
NUMBER FORMAT
orY/X AXIS FORMAT
, which is limited to features built-in in the d3-format. This formatting doesn't allow for pre/suffixes. So in my situation I can chose to display 37 or 37.6, but I can't display 37.6 °C.Would it be possible to introduce an additional option, which would allow to add a prefix and/or suffix to the numbers on charts? This would be useful for the static numbers and when hovering over the chart, also in most of the current existing charts.
Describe the solution you'd like
Most convenient from my perspective would be to define the unit for specific columns at database level by adding an additional box in the
Edit Dataset
pop up (just like it's already the case for the time dimensions). That would allow to automatically see the pre/sufix without repeating the process on each chart.Describe alternatives you've considered
Another solution would be to specify prefix and/or suffix alongside the D3 number formatting. This could be using the same input box, via a syntax like <my_prefix>{actual D3 formatting}<my_suffix> (e.g. {,.2f} °C).
The text was updated successfully, but these errors were encountered: