Provide capability to scrape multiple resources under on metrics, aggregated with labels per resource
See original GitHub issueWe want to be able to use Prometheus labels on our metrics. We are currently using Azure Metrics Exporter. If we scrape two databases for their DTU consumption using a metric called dtu_consumption_percent_percent_average, it will label them with resource_group and sub_resource_name. This allows us to aggregate these metrics with PromQL queries.
As far as I know, Promitor currently does not allow you to re-use the same metric name or use labels. This leaves us having to add suffixes to metrics, which can’t be aggregated. e.g.:
- name: promitor_db_dtu_percent_my_database
description: "DTUs consumed"
resourceGroupName: my_group
resourceType: Generic
resourceUri: Microsoft.Sql/servers/my_server/databases/my_database
filter: ""
azureMetricConfiguration:
metricName: dtu_consumption_percent
aggregation:
type: Average
Specification
- Allow us to define Prometheus labels in metric configurations
- Allow duplicate metric names if the label values are different
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:36 (31 by maintainers)
Top Results From Across the Web
Aggregate statistics across resources - Amazon CloudWatch
You can aggregate the metrics for AWS resources across multiple resources. Metrics are completely separate between Regions, but you can use ...
Read more >Advanced features of Metrics Explorer - Azure Monitor
The resource scope picker allows you to view metrics across single resources and multiple resources. The following sections explain how to use ...
Read more >Using Amazon CloudWatch metrics math to monitor and ...
Metric math enables you to query multiple CloudWatch metrics and use ... provide a single view of your resources and aggregate information ...
Read more >Select metrics when using Metrics Explorer
In the Resources menu, select the resource from which the metric data is captured. When a metric isn't written against a resource, select...
Read more >Confluent Cloud Metrics API: Reference Documentation
The new /available endpoint allows determining which metrics are available for a set of resources (defined by labels). This endpoint can be used...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

As things keep on getting delayed I’m introducing #646 which allows us to version metrics declaration. If this feature does not make it for v1.0 we can still easily provide this in v1.x without breaking changes.
I think I’ll move it out for now and can still make it more flexible later on if people really want to (although I think we shouldn’t)