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

Configuration Help - No timeseries returned #2767

Closed
jpatwary opened this Issue May 24, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@jpatwary
Copy link

jpatwary commented May 24, 2017

What did you do?
I have four instances running on Amazon EC2. I ssh'd into one of my Amazon EC2 instances and set up the following configuration in prometheus.yml using the access and secret access keys I got from my AWS Iam role with EC2ReadOnly permissions attached.

What did you expect to see?
I expect to see all four of my EC2 instances up and running under consoles/prometheus.html with the timeseries tables returned.

What did you see instead? Under which circumstances?
Three out of my four EC2 instances are labeled as No under the Up column in the table. There are no Ingested samples, time series, or memory listed for any of them. The fourth EC2 instance (the one I connected to and installed and configured prometheus on) is labled as Yes under Up and does have Memory specified, but Ingested Samples and Time Series are left as blank. If I click on any of these instances, there is no time series returned in any of the data.

I'm not getting data returned for my EC2 instances (though I am getting data and timeseries returned for my localhost). Any help on this matter is greatly appreciated!

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

  # Attach these labels to any time series or alerts when communicating with
  # external systems (federation, remote storage, Alertmanager).
  external_labels:
      monitor: 'codelab-monitor'

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  # - "first.rules"
  # - "second.rules"

# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
  - job_name: 'node'
    static_configs:
      - targets: ['localhost:9100']
  # 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']
    ec2_sd_configs:
      - region: us-east-1
        access_key: ACCESS_KEY
        secret_key: SECRETY_ACCESS_KEY
        port: 9100

~
~

@shencan

This comment has been minimized.

Copy link

shencan commented Jun 13, 2017

the same case

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jun 13, 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.