Skip to content
Discussion options

You must be logged in to vote

Hey @salacr, thank you for clarifying. 👍

Yeah, the database auto-discovery is not implemented or planned for the time being, as it's non-trivial given the database-agnostic direction this utility has. Given this constraint, I'd rather keep it outside of the scope, so the configuration is user's responsibility.

It's possible to render the templated configuration, and then use the /reload endpoint to let sql_exporter utilise the updated config. One of the users previously mentioned operating sql_exporter using reload to dynamically manage query configuration on a large scale with over 500+ databases. Maybe this would work for you.

UPD: Your problem could be also potentially solved with jobs

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@salacr
Comment options

@burningalchemist
Comment options

Answer selected by burningalchemist
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants