Bulk action codes in the audit logs

Breakdown of the bulk action codes in the audit logs

Use the below codes to read and understand the bulk actions in the audit logs:
Bulk Action
Codes
Threshold Profile
0
Location Profile
1
Notification Profile
2
User Alert Groups
3
Check Frequency
4
IT Automation
5
Activate Monitor
6
Suspend Monitor
7
Delete Monitor
8
Upgrade Server Monitoring Agent(s)
9
Server Logs Needed
11
Resource Check Profiles
12
Associate Monitor Groups
16
Disassociate Monitor Groups
20
Tags
19
Plugin Execution Timeout
21



    • Related Articles

    • Bulk action to auto-discover VMware resources

      You can enable autodiscovery to monitor all the VMware virtual machines (VMs), datastores, resource pools, and snapshots in bulk at the associated VMware ESX/ESXi host level. Simply choose Yes next to your preferred resources and select the VMware ...
    • How can I perform bulk actions on the performance counters?

      You can perform bulk actions, like Suspend, Activate, and Delete, on: Multiple performance counters across several devices with the same device template. Multiple performance counters associated with a single device. Note You can perform bulk actions ...
    • Filtering Windows event logs before uploading

      You can filter Windows event logs in the agent side before uploading them to Site24x7. You can configure to eliminate the unwanted event IDs, so that you can skip them while uploading.  You can set these field configuration while Adding a Log Type, ...
    • Where are the Network Monitoring logs located?

      The default directories for installing the On-Premise Poller are: Windows: C:\Program Files(x86)\Site24x7OnPremisePoller Linux: /opt/Site24x7OnPremisePoller On-Premise Poller logs If you've installed the On-Premise Poller in the default directory ...
    • How to collect Applications and Services Logs from Windows event logs

      Site24x7 AppLogs uses the Windows Management Instrumentation (WMI) query on the Site24x7 Server Monitoring agent to fetch event logs. The WMI module requires the registry entry below to read the event logs from the Applications and Services Log ...