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

az monitor diagnostic-settings categories list incorrectly always returns an empty list #10719

Closed
jurjenoskam opened this issue Oct 2, 2019 · 4 comments · Fixed by #12020
Closed
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Diagnostic Settings
Milestone

Comments

@jurjenoskam
Copy link

(On azure-cli 2.0.74 using the Cloud Shell; I did not try any other versions)

az monitor diagnostic-settings categories list always returns an empty list of categories, even though the resource does have categories. This happens with every resource type I tried. Example:

azureuser@Azure:~$ az monitor diagnostic-settings categories list --resource ${RESOURCE_ID}
{
  "value": []
}
azureuser@Azure:~$ az rest --method get --uri ${RESOURCE_ID}/providers/microsoft.insights/diagnosticSettingsCategories?api-version=2017-05-01-preview --query"value[].[name,properties.categoryType]" --output tsv
This command is in preview. It may be changed/removed in a future release.
VMProtectionAlerts      Logs
AllMetrics      Metrics
azureuser@Azure:~$

I would expect the first command to return the same list of categories as the second command.

I believe this is caused by az monitor diagnostic-settings categories list using an incorrect API call, based on the following command output when adding --debug:

  [...]
urllib3.connectionpool : https://management.azure.com:443 "GET [resource-id-redacted]/providers/microsoft.insights/diagnosticSettings?api-version=2017-05-01-preview HTTP/1.1" 200 None
  [...]

As you can see, it requests diagnosticSettings instead of what I believe to be correct: diagnosticSettingsCategories.

@maggiepint maggiepint added customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Diagnostic Settings Service Attention This issue is responsible by Azure service team. labels Oct 2, 2019
@ghost
Copy link

ghost commented Oct 2, 2019

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Dalubash

1 similar comment
@ghost
Copy link

ghost commented Oct 2, 2019

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Dalubash

@nkiest
Copy link

nkiest commented Oct 10, 2019

@asheniam can you route this to an engineer to investigate?

@haroldrandom haroldrandom added customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Diagnostic Settings Service Attention This issue is responsible by Azure service team. labels Oct 25, 2019
@yonzhan yonzhan added this to the S165 milestone Jan 26, 2020
@yonzhan
Copy link
Collaborator

yonzhan commented Jan 26, 2020

add to S165.

@asheniam asheniam removed the Service Attention This issue is responsible by Azure service team. label Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor - Diagnostic Settings
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants