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

Invalid metric name #2281

Closed
talhakabakus opened this Issue Dec 14, 2016 · 8 comments

Comments

Projects
None yet
3 participants
@talhakabakus
Copy link

talhakabakus commented Dec 14, 2016

What did you do?
Just configured a scrape to monitor my web app located at http://localhost:8080/testapp.

What did you expect to see?
The various analysis of my web server

What did you see instead? Under which circumstances?
No result is displayed

Environment
Ubuntu 16.04 LTS

  • System information:
    Linux 4.4.0-31-generic x86_64

  • Prometheus version:

prometheus, version 1.4.1 (branch: master, revision: 2a89e87)
build user: root@e685d23d8809
build date: 20161128-09:59:22
go version: go1.7.3

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

    external_labels:
    monitor: 'codelab-monitor'

rule_files:

scrape_configs:

  • job_name: 'payara'
    metrics_path: '/testapp'

    static_configs:

    • targets: ['localhost:8080']
@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Dec 14, 2016

Can you share the metric name that was problematic?

@talhakabakus

This comment has been minimized.

Copy link
Author

talhakabakus commented Dec 14, 2016

That's all the configuration I have done @brian-brazil, when I enter Prometheus -> Status -> Targets, I see the error I shared in the previous post.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Dec 14, 2016

You application is producing an invalid metric name. This is a bug in the application, can you indicate which client library you're using?

@talhakabakus

This comment has been minimized.

Copy link
Author

talhakabakus commented Dec 14, 2016

I use Payara application server that hosts a Java EE web app.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Dec 14, 2016

@talhakabakus

This comment has been minimized.

Copy link
Author

talhakabakus commented Dec 14, 2016

Ok @brian-brazil, just figured out the reason of the error - something related with my security restrictions. Thanks for your guidance.

@srikanthdixit

This comment has been minimized.

Copy link

srikanthdixit commented Jun 8, 2017

Hello Brian-brazil,

This is my prometheus configuration file.

my global config

global:
scrape_interval: 15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
evaluation_interval: 15s # 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:

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:
      • "10.93.1.134:9100"
      • "10.9.64.47:9100"

Issue: In prometheus dashboard i can see the target servers are showing DOWN not sure what would be the issue. I might be doing something wrong. Any help would be greatly appreciated. Please find attached screeen shot is what i'm facing
screen shot 2017-06-08 at 11 07 53 am

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