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

QA:Do jmx_prometheus_httpserver scrapy data from jmx server proactively when without prometheus? #876

Closed
hanson2021 opened this issue Sep 12, 2023 · 5 comments

Comments

@hanson2021
Copy link

When i only start jmx_prometheus_httpserver ,whether it will proactively scrapy data or not? If it will, is there any configure to control frequency?

@fstab
Copy link
Member

fstab commented Sep 12, 2023

No, it's just callbacks waiting for the Prometheus server to scrape. If the metrics endpoint is not called, nothing will happen.

@mustajibmk
Copy link

Can we have an option to enable active scraping at certain intervals? That way we can remove the dependency on the Prometheus server and jmx_exporter be used as a standalone tool.

@fstab
Copy link
Member

fstab commented Sep 12, 2023

I think I don't understand your question. What are you trying to achieve? You need a Prometheus server to do Prometheus monitoring, right?

@mustajibmk
Copy link

Most of the time, yes we would have a Prometheus server which would do it for us. I was referring to the case where jmx_exporter was not being called by the Prometheus server but rather by custom Java code/application.

@dhoard
Copy link
Collaborator

dhoard commented Sep 12, 2023

The JMX exporter exposes a REST API to collect metrics from JMX MBeans. Each REST API call collects metrics and returns a metrics response.

The application (Prometheus, custom application, etc.) calling the REST API doesn't matter.

The scraping interval is a function of the application calling the REST API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants