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

[Azure Monitor] Update Data Collection Rules to 2021-09-01-preview #21640

Closed
herreraj-ms opened this issue Mar 14, 2022 · 2 comments · Fixed by Azure/azure-cli-extensions#4716
Assignees
Labels
Auto-Assign Auto assign by bot feature-request Monitor az monitor

Comments

@herreraj-ms
Copy link

Resource Provider

  • RP: Azure Monitor Control Service
  • Resources:
    • Data Collection Rules
    • Data Collection Rule Associations
    • Data Collection Endpoints

Description of Feature or Work Requested

Minimum API Version Required

  • 2021-09-01-preview

Swagger Link

Target Date

  • April 2022

Support for load payload from file

  • Currently the customer must express a complete rule in a flatten schema, example.
az monitor data-collection rule create --resource-group "________" --location "westus2" --name "myCollectionRule" --data-flows destinations="ertyuifjftdghf" streams="Microsoft-Perf" streams="Microsoft-Syslog" streams="Microsoft-WindowsEvent" --log-analytics name="ertyuifjftdghf" resource-id="/subscriptions/_____________________________________/resourceGroups/________________________/providers/Microsoft.OperationalInsights/workspaces/ertyuifjftdghf" --performance-counters name="cloudTeamCoreCounters" counter-specifiers=\\Processor(_Total)\\% Processor Time counter-specifiers=\\Memory\\Committed Bytes counter-specifiers=\\LogicalDisk(_Total)\\Free Megabytes counter-specifiers=\\PhysicalDisk(_Total)\\Avg. Disk Queue Length sampling-frequency=15 transfer-period="PT1M" streams="Microsoft-Perf" --performance-counters name="appTeamExtraCounters" counter-specifiers=[\\Process(_Total)\\Thread Count](file://process%28_total%29/Thread%20Count) sampling-frequency=30 transfer-period="PT5M" streams="Microsoft-Perf" --syslog name="cronSyslog" facility-names="cron" log-levels="Debug" log-levels="Critical" log-levels="Emergency" streams="Microsoft-Syslog" --syslog name="syslogBase" facility-names="syslog" log-levels="Alert" log-levels="Critical" log-levels="Emergency" streams="Microsoft-Syslog" --windows-event-logs name="cloudSecurityTeamEvents" transfer-period="PT1M" streams="Microsoft-WindowsEvent" x-path-queries="Security!" --windows-event-logs name="appTeam1AppEvents" transfer-period="PT5M" streams="Microsoft-WindowsEvent" x-path-queries="System![System[(Level = 1 or Level = 2 or Level = 3)]]" x-path-queries="Application!*[System[(Level = 1 or Level = 2 or Level = 3)]]"
az monitor data-collection rule create  --resource-group "_" --location "_" --name "_" --rule-file "C:\samples\dcrEx1.json"
@ghost ghost added Auto-Assign Auto assign by bot Monitor az monitor labels Mar 14, 2022
@ghost ghost assigned kairu-ms Mar 14, 2022
@ghost ghost added this to the Backlog milestone Mar 14, 2022
@yonzhan
Copy link
Collaborator

yonzhan commented Mar 14, 2022

monitor

@kairu-ms
Copy link
Contributor

Hi @herreraj-ms, we still use flatten schema this time. In our next generation of CodeGen tool, we can support entire payload as a parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot feature-request Monitor az monitor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants