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

recording rules show different data from raw PromQL #3279

Closed
i19 opened this Issue Oct 11, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@i19
Copy link

i19 commented Oct 11, 2017

What did you do?
I scrape metrics every 10 seconds, and run rules every 10 seconds too.
The raw data is an counter, which is used to counter the request counts, aka QPS
I use grafana to graph the data points for the last 1 hour, with step as 10 seconds
below is my graph
image

What did you expect to see?
The two lines should be the same at most times.

What did you see instead? Under which circumstances?
The graph generated by recording rules had a lot square, lost some details

Environment

  • System information:

    Linux 3.10.0-327.28.3.el7.ttm.x86_64 x86_64

  • Prometheus version:

    prometheus, version 1.7.1 (branch: release-1.7, revision: dd38135)
    build user: i19@Mac
    build date: 20170922-09:42:16
    go version: go1.8.3

  • Prometheus configuration file:

global:
  scrape_interval:     10s
  evaluation_interval: 10s
  scrape_timeout:      5s

rule_files:
  - "recording.rules"

scrape_configs:
  - job_name: ucs_raw
    metrics_path: '/raw'
    honor_labels: true
@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Oct 11, 2017

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

@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.