You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Query export is an useful tool for monitoring our applications. We like it very much and want to introduce it to our teams.
According to the document, except that the databases can be read from other files, section of metrics and queries must be written in the same file, and query exporter can only read one configuration file at a time.
In our case, we will only set up one query export and share it with multiple teams.
Different teams may use the same database, but queries and metrics will be different, this scenario will cause a large configuration file eventually.
Also, from the point of view of collaborative work, when someone needs to add or modify these settings, they must modify the same file which might not be so efficient and also cause conflict when integrating all the changes.
So, my suggestion is that is it possible to develop a new feature that read the metrics and queries section from other sources for better maintenance practice, like supporting reading the settings from the config.yml file?
The text was updated successfully, but these errors were encountered:
Query export is an useful tool for monitoring our applications. We like it very much and want to introduce it to our teams.
According to the document, except that the
databases
can be read from other files, section ofmetrics
andqueries
must be written in the same file, and query exporter can only read one configuration file at a time.In our case, we will only set up one query export and share it with multiple teams.
Different teams may use the same database, but
queries
andmetrics
will be different, this scenario will cause a large configuration file eventually.Also, from the point of view of collaborative work, when someone needs to add or modify these settings, they must modify the same file which might not be so efficient and also cause conflict when integrating all the changes.
So, my suggestion is that is it possible to develop a new feature that read the metrics and queries section from other sources for better maintenance practice, like supporting reading the settings from the config.yml file?
The text was updated successfully, but these errors were encountered: