Azure / Azure/azure-rest-api-specs

`Microsoft.Insights` - Unused properties can still be configured on Azure Portal

Open
#23,925 0 comments 0 reactions 0 assignees View on GitHub
Insights Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
3d 2h
Merged PRs (30d)
424

Description

### Question:
According to [this document](https://github.com/Azure/azure-rest-api-specs/blob/e129012901bbd9cc0f182ec5b539bccf2440ef4a/specification/applicationinsights/resource-manager/Microsoft.Insights/stable/2015-05-01/componentFeaturesAndPricing_API.json#L241), `WarningThreshold` and `StopSendNotificationWhenHitThreshold` are not used, but they can still be configured by users on Azure Portal. Could anyone help confirm whether these 2 properties take effect? If so, **the document needs to be updated**.

![image](https://github.com/Azure/azure-rest-api-specs/assets/76987228/b650770a-00ae-4d7a-b986-9cf82297150b)

Contributor guide

Open the contributing guide

Research direction

Start with specification/applicationinsights/resource-manager/Microsoft.Insights/stable/2015-05-01/componentFeaturesAndPricing_API.json at the referenced WarningThreshold and StopSendNotificationWhenHitThreshold definitions. Verify whether these properties take effect when configured through Azure Portal, then update the specification document if the documented unused status is incorrect.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.