Frequently Asked Questions
Are multi-dimensional metrics supported?
Yes, every scraper supports scraping multi-dimensional metrics except for Azure Storage queues.
You can configure the dimension you are interested in via
azureMetricConfiguration.dimension.Name, for more information see
our ‘Metric Configuration’ page.
However, you can only use it with metrics in Azure Monitor that support this, for a complete overview we recommend reading the official documentation.
Is scraping multiple subscriptions supported?
No, we do not support scraping multiple subscriptions as of today as we consider that to be a security boundary.
However, you can deploy multiple instances of Promitor that each scrape another subscription.
We have it on our backlog to see if there is enough demand for it, feel free to give a :+1:. If that is the case, we will reconsider this limitation.
What Azure clouds are supported?
Germany Azure clouds.
This can be configured in the metric configuration under
For more information see our ‘Metric Configuration’ page.
What Helm version is supported?
Promitor supports deployments with Helm v3.0 for all versions.
What operating systems are supported?
We support running on both Linux & Windows platforms.
How does Promitor handle deleted resources?
The approach depends if you are using declarative metrics or resource discovery but we highly recommend to enable Prometheus metric timestamps in our runtime configuration to indicate how old the metric is.
When using declarative metrics
Promitor will scrape all resources that are configured and report the metrics accordingly. If that resource is deleted, we will still serve the metrics as long as we can until it is no longer available and exceptions will be thrown.
We recommend to update the metrics declaration when a resource is deleted to avoid polluting logs.
When using resource discovery
Promitor will automatically discover all matching resources which means that it will automatically scrape metrics for new/removed resources.
Removed resources will immediately stop being scraped by Promitor, but still be reported in Prometheus scrape endpoint.