Types of Alert

The types of thee alerts are as follows:

  • Application Alert - ADC specific Application actions executed from AppViewX (Control Center or Dashboards) will be raised as an alert captured in the alerts inventory. These alerts are focused on the behavior and performance of applications being delivered through the ADC.

    ADC Application alerts include:
    Event Type Description Scenario Message
    Statistics The statistics data collection to monitor the historic statistics for object level. device statistics failure Statistics collection for the device <"device name"> configured in alerts/alert <"alert names"> failed due to <"error reason">.
    Restore/Rollback Restore or rollback of an object configuration to a previous state. Object Restore

    Successful : Object <object name> restore action successful for the workorder <workOrderId>
    Dashboard import Status of the Dashboard import. Dashboard import <ObjectsName> association to <dashboardName> failed, as they are not associated to <deviceName>
    Any action Any action performed at the application level. The actions include:

    • Enable

    • Disable

    		 GTM sync setting (gtm flush) Action Enable executed successfully on object <ObjectDisplayname> by the user admin. GTM sync setting is enabled and hence the action is executed on the Master device <device name>. The actual triggered Peer device is <device name>

    For configuring Application alert notification, see Configuring an Application Alert Notification.

  • Device Alert - ADC specific Device actions executed from AppViewX (Control Center or Dashboards) will be raised as an alert captured in the alerts inventory. The administrator receives notifications for events performed at the device level.

    ADC Device alerts include:
    Event Type Description Scenario Message
    Status change Device status changes between any of the following:

    • Managed

    • Unmanaged

    • Failed

    • Unresolved

    Other status changes of the device are also captured under this event type. For example, modification of the Device status from x to y.

    		 Device status change (Managed ->Unmanaged, Failed, Unresolved) Device status modified from Manged to "Unmanaged/ Failed /Unresolved" on device:<device name>
    Auto-detect Automatic detection of the secondary Device status. Device auto-detect failure Secondary device auto detect failed for the device <device name> due to <error message>
    State change Success/failure message for the Device state. Device state flip Device flip action was sucessfull on device < device name>. Modified properties{} via syslog
    Device import Success/failure message for the Device import. Device import failure Device Import from the file <fileName> failed due to <error message/ invalid column headers>
    DNS_lookup A scheduled reverse lookup for the objects that contain an IP address in it and persists the DNS name of the objects. DNS lookup DNS Reverse lookup failed for device <deviceName> due to <reason>
    Any Action Any action performed at device level. The actions include: SSL Handshake failure (key exchange) Communication failed for device <deviceName> due to <SSL handshake error>
    Backup Creation of the device backup. Device backup success Backup/Scheduled Backup has been generated successfully for the device <deviceName>
    Restore/Rollback Device-level to overwrite the complete device config. Device Rollback

    Successful : Device <device name> rollback action successful for the workorder <workOrderId>
    Ihealth iHealth report generation for the device. Ihealth generation success IHealth Report for <deviceName> is generated successfully
    Statistics The statistics data collection to monitor the historic statistics for devices. Device statistcs failure Action <Updating live statistics> on <device Name> failed due to error <errorMessage>

    For configuring Device alert notification, see Configure a Device Alert Notification.

  • Threshold Alert - notification or warning generated by an ADC when a statistic threshold of application/device. threshold or limit is exceeded. These alerts are designed to inform administrators about certain conditions that may require attention or action. This alert helps the administrator to take proactive measures to monitor and prevent outages or application issues. The administrator receives alert notifications based on the configured settings in the Threshold alert settings.

    Threshold alerts include:
    Event Type Description Scenario Message
    Statistics The conditions that will generate an alert notification. Threshold Statistics collection Threshold level reached for the object <object name>. <Statistics name – current value> is <operator> the threshold <configured value> AND < Statistics name – current value > is <operator > the threshold <configured value>.

    For configuring Threshold alert notification, see Configuring Threshold Alert Notification.

  • Syslog Alert - a notification or warning generated by an ADC that is sent as a log message to a Syslog server. These alerts are designed to provide information about specific events or conditions related to the ADC's operation, performance, or security. Any changes occurring in the device can be detected and patterned through Syslog alerts.

    Some examples of Syslog alerts include:
    • Syslog based updates for Object state change eg: Enabled, Disabled etc.,
      • Real time updates are supported only for F5. The other vendor object state will be updated at an interval of 15 mins.
    • Syslog based updates for Object status change eg: Available, Offline etc.,
      • Real time updates are supported only for F5. The other vendor object status will be updated at an interval of 15 mins.
    • Syslog based updates for Device failover state within 5 to 10 mins (Active, Standby) -
      • Applicable only for F5 and Citrix devices.
    • Syslog based updates for Creation/Modification/Deletion of Primary objects eg: WideIP, Virtual Server, etc., and Secondary objects eg: Monitor, Profile, etc., at an interval of 15 mins in light weight config sync (Grok filters not restricted to particular object type but configurable)
      • When there are configuration updates on the objects like a new member added/removed/modified, it will be automatically reflected in AppViewX database with respective object mapping.
      • If those hierarchy objects are configured in ACL/Dashboard, the permission and actions will be automatically assigned respectively.

For configuring Syslog alert notification, see Configuring Syslog Alert Notification.