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.

Sign up for GitHub

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

Jump to bottom

[BUG] Missing properties for Azure Monitor DataCollectionRules #33019

Open
maxilampert opened this issue Mar 5, 2025 · 0 comments
Open

[BUG] Missing properties for Azure Monitor DataCollectionRules #33019

maxilampert opened this issue Mar 5, 2025 · 0 comments
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@maxilampert
Copy link

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

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

Environment

No response
@maxilampert maxilampert added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Mar 5, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@maxilampert