Azure / Azure/azure-rest-api-specs

[BUG] Missing properties for Azure Monitor DataCollectionRules

Open
#33,019 0 comments 0 reactions 0 assignees View on GitHub
bug customer-reported Mgmt Monitor question Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
3d 2h
Merged PRs (30d)
424

Description

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/monitor/resource-manager/Microsoft.Insights/stable/2023-03-11/dataCollectionRules_API.json

### API Spec version

2023-03-11

### Describe the bug

Currently the API spec is missing almost all of the supported `kind` values that are described in the Microsoft documentation here that should be available with this version. [DCR Structure](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/data-collection-rule-structure)

The Spec should be updated to include those values and potentially other missing properties. I believe there are more missing values for example in the KnownExtensionDataSourceStreams and KnownDataFlowStreams misses `Microsoft-ConfigurationChange`

### Expected behavior

Availability of all described `kind` values and general update to include all the missing values in the spec.

### Actual behavior

Only Windows and Linux are available for `kind` in the current spec

### Reproduction Steps

See for the missing kinds issue [Direct kind example](https://learn.microsoft.com/en-us/rest/api/monitor/data-collection-rules/create?view=rest-monitor-2023-03-11&tabs=HTTP#create-or-update-data-collection-rule-with-embedded-ingestion-endpoints)

### Environment

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the linked specification/monitor/resource-manager/Microsoft.Insights/stable/2023-03-11/dataCollectionRules_API.json and compare its kind values and stream definitions with the linked Azure Monitor documentation and example. Update the missing supported values and properties, then validate the revised API specification against the documented examples.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
api, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.