You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?
Monkey365 console log shows a large number of 404 errors when querying resources for Azure Diagnostic Settings.
How to reproduce it
Steps to reproduce the behavior:
Execute Monkey365 in a subscription with resources that do not have support for diagnostic settings.
See console log errors
Expected behavior
Monkey365 should try to get information from diagnostic settings if the resource supports it.
From where are you running Monkey365?
Please, complete the following information:
Resource: Docker container, workstation
OS: Windows and Linux
PowerShell Version: All PowerShell versions
Monkey365 Version: latest
Additional context
The latest version of Monkey365 is using a json file with well-know resources that do not have support for diagnostic settings. Logic must be redesigned in order to be able to discover which resource is supporting diagnostic settings, and which resources not.
More information regarding available operations per resource can be seen here.
The text was updated successfully, but these errors were encountered:
What happened?
Monkey365 console log shows a large number of 404 errors when querying resources for Azure Diagnostic Settings.
How to reproduce it
Steps to reproduce the behavior:
Expected behavior
Monkey365 should try to get information from diagnostic settings if the resource supports it.
From where are you running Monkey365?
Please, complete the following information:
Additional context
The latest version of Monkey365 is using a json file with well-know resources that do not have support for diagnostic settings. Logic must be redesigned in order to be able to discover which resource is supporting diagnostic settings, and which resources not.
More information regarding available operations per resource can be seen here.
The text was updated successfully, but these errors were encountered: