[AVM Question/Feedback]: DCR possible to add support for creating kind: Direct as API supports it?

[o-l-a-v]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Description

Context

When creating an DCR for use with the Log Ingestion API

• https://learn.microsoft.com/en-us/azure/azure-monitor/logs/logs-ingestion-api-overview

One is asked to create a Microsoft.Insights/dataCollectionRules of kind: "Direct".

• https://learn.microsoft.com/en-us/azure/azure-monitor/logs/logs-ingestion-api-overview#data-collection-rule-dcr
• https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/data-collection-rule-overview#direct-ingestion

Latest Bicep for DCR does not have this value available for kind:

• https://learn.microsoft.com/en-us/azure/templates/microsoft.insights/datacollectionrules

Neither does AVM:

• https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/insights/data-collection-rule

But the API supports it, I just created a DCR of kind: 'Direct' with it:

• https://learn.microsoft.com/en-us/rest/api/monitor/data-collection-rules/create?view=rest-monitor-2023-03-11

It's not in the API specifications though:

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

Ask

Can features be added to AVM if the ARM API supports it, even though regular Bicep / ARM templates does not have support for it yet?

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

[AlexanderSehr]

Hey @o-l-a-v,
I just assigned the module's owner manually to take it from here. I'd recommend to always use the issue type "module issue" for module-specific questions as this will ensure the owner is automatically assigned 🙂

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

[microsoft-github-policy-service]

Caution

**This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-bicep) immediate attention as it hasn't been responded to within 6 business days. **

Tip

• To avoid this rule being (re)triggered, the "Needs: Triage 🔍" and "Status: Response Overdue 🚩" labels must be removed when the issue is first responded to!
• Remove the "Needs: Immediate Attention ‼️" label once the issue has been responded to.

[AlexanderSehr]

Hey @krbar,
please give this issue a triage spin once you get a moment :)