Data was changed when I refresh the Graph

[lwhile]

What did you do?
I viewed the metrics at the build in web graph

What did you expect to see?
I want the Prometheus to give me correct data

What did you see instead? Under which circumstances?
The graph's history data was changed when I refresh it

Environment

• System information:

  Darwin 17.4.0 x86_64

• Prometheus version:

prometheus, version 2.2.1 (branch: HEAD, revision: 
bc6058c81272a8d938c05e75607371284236aadc)
build user:       root@149e5b3f0829
build date:       20180314-14:21:40
go version:       go1.10      

• Prometheus configuration file:

# my global config
global:
  scrape_interval:     1s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
  evaluation_interval: 10s # Evaluate rules every 15 seconds. The default is every 1 minute.
  # scrape_timeout is set to the global default (10s).

# Alertmanager configuration
alerting:
  alertmanagers:
  - static_configs:
    - targets:
      # - alertmanager:9093

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  # - "first_rules.yml"
  # - "second_rules.yml"

# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
  # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
  - job_name: 'prometheus'

    # metrics_path defaults to '/metrics'
    # scheme defaults to 'http'.

    static_configs:
      - targets: ['localhost:9090']

  - job_name: '{my_job}'

    static_configs:
      - targets: ['localhost:20120']
    metrics_path: '/{mypath}'

After clicking several times of Execute button

Once again

[brian-brazil]

Every time you run the query you're executing it at a different time, so might get a different result. Thus different results do not innately indicate any bug.

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.

[lwhile]

@brian-brazil Sorry, I thank this is a bug. The result cannot produce such a big difference like the image 1 and image 2. The time between two queries just one second. And the query does not use any aggregation operators

[brian-brazil]

There is insufficient information here to indicate a bug, and if there was a bug of this nature it would have been spotted long ago. You have provided no information such as the query you are running or its step.

[lock]

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.