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

Support for enabling alerting on custom metric dimensions #3545

Open
automagic opened this issue Aug 28, 2024 · 1 comment
Open

Support for enabling alerting on custom metric dimensions #3545

automagic opened this issue Aug 28, 2024 · 1 comment
Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). customer/feedback Feedback from customers impact/missing-api kind/enhancement Improvements or new features

Comments

@automagic
Copy link

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

It is currently possible to enable alerting on custom metric dimensions via the GUI and also via ARM templates to an application insights component, but the feature is undocumented in the Azure RM OpenAPI spec.

An example:

"CustomMetricsOptedInType": "WithDimensions"

This is also documented similarly here:
hashicorp/terraform-provider-azurerm#6901

And the issues around documenting the fields in the Azure API:
Azure/azure-rest-api-specs#16511
MicrosoftDocs/azure-docs#54745

Affected area/feature

https://www.pulumi.com/registry/packages/azure-native/api-docs/insights/component/

@automagic automagic added customer/feedback Feedback from customers kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Aug 28, 2024
@thomas11 thomas11 added impact/missing-api awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). and removed needs-triage Needs attention from the triage team labels Aug 29, 2024
@thomas11
Copy link
Contributor

Thank you for logging this issue, @automagic. I have marked it as awaiting upstream since we can't do much without the API spec being correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). customer/feedback Feedback from customers impact/missing-api kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants