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

Limiting the scrape scope per database or instance #74

Open
ulikl opened this issue Oct 15, 2020 · 0 comments
Open

Limiting the scrape scope per database or instance #74

ulikl opened this issue Oct 15, 2020 · 0 comments

Comments

@ulikl
Copy link

ulikl commented Oct 15, 2020

Hi Michael,

I find you exporter really awesome, especially the possibility to configure multiple databases.
I would like to have only very few instance on central servers, scraping a lot of databases.
But I have concerns that the scraping of all of these databases at once will take too long.
Using a separate exporter instance per database would need a lot of separate ports on the central servers.

It would be awesome, if the exporter could be extended -- analog to blackbox exporter(https://github.com/prometheus/blackbox_exporter) or exporter_exporter (https://github.com/QubitProducts/exporter_exporter) -- so that I can supply the database/instance to scrape as parameter.
The Prometheus scrape job could look like

- job_name: 'oracle-single-db'
    scrape_interval: 1m
    scrape_timeout: 55s
    metrics_path: /metrics
    params:
      instance: inst1
      database: db1
     ...

Only the metrics for databases matching the instance and/or database labels in the config file, should be queried and their metrics returned.

I'm looking forward to your opinion.

Kind Regards,
Ulrike

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

No branches or pull requests

1 participant