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

Rounding problem with Y axis labels #3118

Closed
candlerb opened this Issue Aug 26, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@candlerb
Copy link

candlerb commented Aug 26, 2017

(Relates to #3084)

What did you do?

Collect data from apcupsd-exporter

In the console, entered apcups_time_left_seconds/60 as the metric expression to graph

What did you expect to see?

A graph with battery remaining time in minutes rather than seconds

What did you see instead? Under which circumstances?

The graph is OK but the Y axis labels are broken.

image

The data points are 20.5, 21, 21.5 (the raw data points are 1230, 1260, 1290)

Labels should be:

  • 21.6
  • 21.4
  • 21.2
  • 21.0
  • 20.8
  • 20.6
  • 20.4

However the actual labels displayed are:

  • 21.6
  • 00000000002
  • 00000000003
  • 00000000004
  • 00000000004
  • 20.6
  • 00000000002

Environment

  • System information:

    Linux 4.4.0-87-generic x86_64

  • Prometheus version:

    prometheus, version 2.0.0-beta.2 (branch: HEAD, revision: a52f082939a566d5269671e98be06fc6bdf61d09)
      build user:       root@41a0740ea598
      build date:       20170818-08:16:50
      go version:       go1.8.3
    
  • Alertmanager version:

    N/A

  • Prometheus configuration file:

default plus:

  - job_name: apcupsd
    scrape_interval: 60s
    static_configs:
      - targets: ['nuc2.example.com:8080']
  • Alertmanager configuration file:

    N/A

  • Logs:

    N/A

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Sep 28, 2017

Is this still happening with 1.7.2?

@candlerb

This comment has been minimized.

Copy link
Author

candlerb commented Sep 28, 2017

I have only been using 2.0.0 train - the report was for 2.0.0 beta 2, and I am now on 2.0.0 beta 5. If the fix is in beta 5 I can try to reproduce.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Sep 28, 2017

It hasn't made it to the 2.0 branches yet.

@grobie

This comment has been minimized.

Copy link
Member

grobie commented Nov 12, 2017

Should be fixed, please re-open otherwise.

@grobie grobie closed this Nov 12, 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.