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
I have ~250 different GCP projects, with different needs. In some projects I just only need to scrape Composer metrics, in the other projects I need to scrape only BigQuery metrics, or only Compute metrics. Sometimes I need to scrape i.e. Composer+Bigquery, or Compute+Loadbalancing metrics.
I don't want to scrape all the metrics just to catch few metrics that I need in a particular projects. This is cost inefficient (pay per request) and results in throttling by GCP (by the way caused by uncontrollable parallelism).
My workaround is to run simultaneously many exporters with different command line parameters - but it's difficult to maintain.
Is it possible to add ability to configure stackdriver_exporter using .yml file? i.e.
This is unnecessary because the exporter supports selecting different data via the collect param. Similar to how node_exporter and other modular exporters work.
additionally, with such yaml file, will be simplier (in future) to i.e. add ability to use different SA/keys for different projects, using ONE stackdriver_exporter instance.
I have ~250 different GCP projects, with different needs. In some projects I just only need to scrape Composer metrics, in the other projects I need to scrape only BigQuery metrics, or only Compute metrics. Sometimes I need to scrape i.e. Composer+Bigquery, or Compute+Loadbalancing metrics.
I don't want to scrape all the metrics just to catch few metrics that I need in a particular projects. This is cost inefficient (pay per request) and results in throttling by GCP (by the way caused by uncontrollable parallelism).
My workaround is to run simultaneously many exporters with different command line parameters - but it's difficult to maintain.
Is it possible to add ability to configure stackdriver_exporter using .yml file? i.e.
The text was updated successfully, but these errors were encountered: