Skip to content

fix master database behavior #334

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 5 commits into from
Nov 19, 2019
Merged

fix master database behavior #334

merged 5 commits into from
Nov 19, 2019

Conversation

sfalkon
Copy link
Contributor

@sfalkon sfalkon commented Nov 11, 2019

  • Fix problem: 329;
  • Feature: added new field "master" to queries.yaml. Now you can change behavior of query. If "master" is true, query will be call only on once database in instance;
  • Change queries.yaml for work with autoDiscoveryDatabases options: added current database name to metrics becase any database in cluster maybe have same table names; added "master" field for query instance metrics.

@sfalkon sfalkon mentioned this pull request Nov 11, 2019
Closed
@coveralls
Copy link

Coverage Status

Coverage increased (+0.7%) to 65.17% when pulling 1d6d0a6 on sfalkon:fix_master_behavior into 852ec5d on wrouesnel:master.

@wrouesnel wrouesnel merged commit c4508ff into prometheus-community:master Nov 19, 2019
@wrouesnel wrouesnel mentioned this pull request Nov 19, 2019
Closed
@ktosiek ktosiek mentioned this pull request Jun 30, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@sfalkon @coveralls @wrouesnel