Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parameters in Metrics #1155

Closed
AndrewSmithRS opened this issue Jan 6, 2021 · 3 comments
Closed

Parameters in Metrics #1155

AndrewSmithRS opened this issue Jan 6, 2021 · 3 comments
Assignees

Comments

@AndrewSmithRS
Copy link

Is it currently possible to use parameters to populate metric settings? I can choose a parameter for the Metric (e.g. using cpu_percent) however even though the parameter seems to be correct I'm unable to select an Aggregation. I'm not clear how this would work with multiple parameters either.

I was attempting to duplicate the functionality of Database Resource Utilization in Azure SQL Elastic Pools.

@gardnerjr
Copy link
Contributor

@ericajlin can comment on the things that support parameters in metrics.

@ericajlin
Copy link
Contributor

Hi @AndrewSmithRS,
Yes, metrics can be used with parameters. To do this, your parameter value needs to be the full metric ID. For example, the metric ID for storage account availability metric is microsoft.storage/storageaccounts-Transaction-Availability.

The easiest way to get the metric ID is the following:

  1. Using the regular metric pill control, pick the metric(s) you are interested in
  2. View the results in Grid visualization format
  3. Switch the Format option to Row per Metric
  4. Copy the metric ID under the Metric ID column
  5. Use this metric ID value in your parameter, and reference your parameter in the metric drop down picker

Hope this helps!

@ericajlin
Copy link
Contributor

Closing this issue, please re-open if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants