Notification schedules can be deleted any time as needed.
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
3. |
For details on OS versions supported for server monitoring, see the Technical Specifications guides.
NOTE: For Agent-based monitoring to work on an RHEL device running Security-Enhanced Linux (SELinux), SELinux must be either turned off or switched to "permissive mode." You can change the SELinux mode by modifying the file /etc/selinux/config and rebooting the device. For further information about enabling or disabling SELinux on Red Hat Enterprise Linux, go to https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html. |
You can bind multiple profiles to a device if there are multiple logs you want to monitor. | |
With the default monitoring profiles and with profiles you can set up, your appliance can provide:
In addition, you can use Log Enablement Packages (LEPs) to provide:
The appliance comes with monitoring available for 200 servers with your standard license, and you can obtain a license to expand that number. To see how many servers your system is licensed to manage, click on the icon at the top-right corner of the page and then click the icon. The line for Management Capacity Usage displays Monitored Servers, with the number of devices that currently have monitoring enabled compared to the total number of devices that could be monitored under the existing license.
Alerts appear in the Administrator Console, where you can review and dismiss them after they have been dealt with. The appliance provides additional capabilities. Among other things, you can:
The appliance has a number of functions that make working with alerts more efficient:
• |
Alert consolidation (repeat counts): To prevent notification spam, the appliance analyzes the alerts for uniqueness, and uses repeat count for identical alerts to indicate the number of times the alert has been generated. |
• |
Alert storm mitigation: To prevent too much repeated data from streaming in, the appliance limits the collection for any one device to 50 alerts in a single collection. The appliance then composes a generic alert indicating that there is abnormal activity that needs attention. |
• |
Grooming: A user can dismiss (hide from view, but keep in the database) alerts, or delete alerts manually or automatically after a set number of days. However, the appliance automatically limits a device to storing 2000 alerts before the appliance begins deleting alerts from the database. |
Only Agent-supported operating systems are supported for Monitoring.
The appliance provides two methods for enabling monitoring.
When a server is enabled, an icon in the Status column on the Device page in the Inventory section indicates the enabled status, and whether monitoring is active or paused:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center