Skip to content
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

Y-axis does not scale to very small values #3084

Closed
candlerb opened this Issue Aug 16, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@candlerb
Copy link

candlerb commented Aug 16, 2017

What did you do?

With default install and default scraping config, browse the scrape_duration_seconds metric

What did you expect to see?

Nicely labelled graph

What did you see instead? Under which circumstances?

The Y axis labels are "0.00", "0.00", "0.00", "0.00"

image

Checking some data points, the labels here should be "0.001", "0.002", "0.003" and "0.004" (the largest data point is 0.00396 and is just below the 0.004 line)

Or perhaps these would be better rendered as 1.0m, 2.0m, 3.0m, 4.0m

Environment

  • System information:

      Linux 4.4.0-87-generic x86_64
    
  • Prometheus version:

    prometheus, version 2.0.0-beta.1 (branch: HEAD, revision: 4dcb465029f39a2a3030333a81753f8a40ec90ce)
      build user:       root@d3f9974fac5a
      build date:       20170811-12:12:36
      go version:       go1.8.3
    
  • Alertmanager version:

    n/a

  • Prometheus configuration file:

    unmodified default

  • Alertmanager configuration file:

    n/a

  • Logs:

    n/a

@gouthamve

This comment has been minimized.

Copy link
Member

gouthamve commented Sep 28, 2017

@yamatoya @grobie @beorn7 Can this be closed ref: #3184 ?

@beorn7

This comment has been minimized.

Copy link
Member

beorn7 commented Sep 28, 2017

Yes, this should be addressed in 1.7.2. @candlerb please re-open if that's not the case.

@beorn7 beorn7 closed this Sep 28, 2017

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.