influxdata / influxdata/telegraf

Enhance Azure Monitor input plugin to allow collecting dimension specific metrics

Open
#15,024 4 comments 3 reactions 0 assignees View on GitHub
area/azure feature request upstream
Dominant language
Go
Stars
17.8k
Forks
5.8k
Avg merge
1d 20h
Merged PRs (30d)
161

Description

### Use Case

The current Azure monitor telegraf input plugin supports providing resource_id, metrics and aggregation. Azure also provides the option to filter these metrics based on [dimensions](https://learn.microsoft.com/en-us/cli/azure/monitor/metrics?view=azure-cli-latest#az-monitor-metrics-list) . An example use case could be where the resource is a database server and Azure provides visibility into database level metrics through dimensions but we are unable to get the database level granularity due to lack of dimension support.

### Expected behavior

Once the feature is implemented, we should be able to specify the dimension name (eg being "DatabaseName") and the value of the database name and only get metrics for that particular database through the input plugin.

### Actual behavior

Currently thee is no dimension support so we cannot get dimension level metrics.

### Additional info

It looks like we are using https://github.com/logzio/azure-monitor-metrics-receiver/blob/master/azure_monitor_metrics_receiver.go for the metric receiver code and we would need to change that to include dimension as well before we are able to call this from the plugin code.

Contributor guide

Open the contributing guide

Research direction

Start by reading azure_monitor_metrics_receiver.go in the linked azure-monitor-metrics-receiver project and the Telegraf Azure Monitor input plugin entry point, tracing how resource_id, metrics, and aggregation are passed. Done means the plugin accepts a dimension name and value and collects only metrics matching that dimension; verify the behavior with the plugin's existing validation or integration checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, go
Domain
cloud, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.