When the portal opens, click on the Subscriptions option (as indicated by Figure 3).įigure 3 : Clicking on the Subscriptions optionįigure 4 that appears next will list all the subscriptions that have been configured for the target Azure AD tenant. To know the ID that maps to the target subscription, do the following: Specify the GUID which uniquely identifies the Microsoft Azure Subscription to be monitored. The host for which the test is to be configured. Output of the test: One set of results for the configured SUBSCRIPTION ID Configurable parameters for the test Parameters Target of the Test: A Microsoft Azure Subscription Follow the steps discussed in Configuring the Activity Log to be Sent to a Log Analytics Workspace to achieve this: To avoid this, before configuring this test, make sure that the Activity log is configured to be sent to at least one Log Analytics Workspace. If the Activity log is not sent to any Log Analytics Workspace, then this test will only report the value 0 for all its measures. This test reports valid metrics on events by reading data from these Log Analytics Workspaces only. Typically, to consolidate log entries, correlate log data, and perform complex analysis, the Activity log is often sent to one/more Log Analytics Workspaces. Detailed diagnostics provide additional problem insights to administrators, thereby easing troubleshooting. In the process, the test notifies administrators every time a problem condition is captured by the log.
This test monitors the Activity log and reports the count of events logged per severity/category.
This is exactly what the Azure Activity Logs test does!
To promptly, and sometimes proactively, capture problem conditions, resolve bottlenecks, and avert potential disasters, administrators need to be alerted as soon as a critical/warning event, a serious health issue, or a crucial operational failure is logged in the Activity log. Events of varying severity levels - eg., critical events, warning events, information events - and events of different categories - eg., administrative, service health, resource health etc. This includes such information as when a resource is modified or when a virtual machine is started. The Activity log is a platform log in Azure that provides insight into subscription-level events.
0 kommentar(er)
