Learn about an alert, types of alerts and how to view and close alerts.
Alerts notifies user of important events occurring in VHQ. The user can specify the type of alerts and the method of notification (e-mail message or status screen). Some alerts are available, only if the specific module is implemented, such as Diagnostics or Content Management modules.
There are alerts generated by, VHQ Server, VHQ Agent and applications. All these alerts can be individually configured as Enable/Disable in the VHQ UI.
EXAMPLE:
When the VHQ Server determines that an active device has not sent any heartbeat message for more than 24 hours, then it raises the Device Missing alert for this device.
The alerts generated by the VHQ Agent in the device can be individually configured as ON/OFF based on the value of the alert mask that is specified in the VHQ Agent configuration file. Alerts have a severity level associated with them (High/Medium/Low), and the severity levels for these alerts can be configured from the VHQ GUI. Only High severity alerts will spawn a visual notification on the top most panes of the VHQ GUI. E-mail notification for all types of alerts can be configured on a per-user basis.
The Alerts chart displays information about alerts that were generated during the past seven days. If no alerts are generated during the past seven days, then the status message No Alerts found is displayed. The No Alerts found status message is displayed when the VHQ GUI is unable to avail chart data to be sent by the VHQ server.
The table lists the various Alert types:
Alert Type |
Description |
Application Alert |
Generated when an application in a device reports an event to VHQ Agent. The VHQ Agent in turn communicates this alert to the VHQ Server. |
Blacklisted Device Contacting |
The alert notifies that a backlisted device is contacting. The alert is generated when the blacklisted device tries to connect to the server. |
Content Replace Failed |
The alert notifies the content replacement failure. The alert is generated when a scheduled content cannot be replaced with the existing content or fails to send response of content replacement in the device within the specified threshold limit. |
Deleted Device Contacting |
The alert notifies that a deleted device is contacting. The alert is generated when the deleted device tries to connect to sever. |
Device Missing |
The alert notifies the missing device. The alert is generated when the device fails to communicate with the VHQ Server within the specified threshold limit. |
Device Moved |
The alert notifies the device moved. The alert is generated when the device is identified at different location. |
Device Reboots |
The alert notifies rebooting of the device. The alert is generated when the device is restarted. |
Device Re-Registration Success |
The alert notifies the registration of the device with the server. The alert is generated when the device successfully re-registers. |
Device Tampered |
The alert notifies when user tries to tamper the device. The alert is generated on unauthorized access to the hardware or software of the device. |
Device Unable to Register |
The alert notifies device registration failure. The alert is generated when the device fails to register. |
Download Failed |
The alert is triggered when the software package cannot be downloaded successfully or fails to send response to the server within the specified threshold limit. |
Install Failed |
The alert notifies the software download failure to the device. The alert is generated when the software package cannot be downloaded successfully or fails to send response to the server within the specified threshold limit. |
Invalid Device IP Contact |
The alert notifies the device contacting with an invalid IP address. The alert is generated when a device contacts with unspecified IP Range. |
Low RAM Memory |
The alert notifies the low RAM memory of the device. The alert is generated when the device memory has run out of space. |
Low Flash Memory |
The alert notifies the low flash memory of the device. The alert is generated when the device memory has run out of space. |
Low Battery |
The alert notifies the low battery of the device. The alert is generated when the battery charge of the device reaches low and critical levels. |
Multiple Device Reboots |
Notifies when a device gets rebooted specified number of times during a specified period. This alert is generated on the basis of the Multiple Device Reboots Counter and Multiple Device Reboots Threshold configuration where the administrator configures the value of the user preference in the VHQ system. The alert is generated whenever reboot count of a device exceeds Multiple Device Reboots Counter value in specified Multiple Device Reboots Threshold duration. The Multiple Device Reboots alert can be either enabled or disabled by the administrator and will continue to apply on user preference. |
Unauthorized Device Swap Request |
Whenever a device is replaced with a different device and is not enabled for swap-out the alert is generated. The alert notifies the unauthorized device swap. The alert is generated when a device is replaced with a different device when it is not enabled for swap-out. |
The Open Alerts option can be used to generate a report of all open alerts in the VHQ system, and it also has an option to close one or more of these open alerts.
This report has a filter condition for the Alert Type field. To generate all types of alerts, the value All Alert Types must be selected from the Alert Type drop-down list, else the required alert type should be selected from the Alert Type drop-down list.
The supported alerts are:
The following alerts are supported only if the VHQ Diagnostic module is licensed. To create custom alerts, contact VHQ Support.
NOTE: Alerts that are in the OPEN state will get automatically purged from the VHQ system after 90 days have elapsed from the date these alerts were generated. This purge duration is a configurable value and you should check with your VHQ administrator if you want to change this duration or if you want to verify the current purge duration for alerts in the OPEN state.
To view open alerts:
When an alert is initially generated, it will be in the OPEN state. Once a VHQ user has reviewed the generated alerts and has taken the required action (if applicable), then the user must mark these alerts as CLOSED from the Open Alerts screen.
Before you use the Open Alerts Report, ensure that you have set the correct device search criteria from the Device Search.
NOTE: If you have set your device filter to the hierarchy Verifone >> South >> Texas >> Dallas in the Device Search tab, then the data in the Open Alerts Report will be for the devices that are in the hierarchy Verifone >> South >> Texas >> Dallas.
The data from the Open Alerts Report can be exported to an Excel file by clicking the Export to Excel icon.
NOTE: Click on the Device Serial link for an individual alert to view the Device Profile of the relevant device.
There are two ways to close an alert:
To view and close an alert:
NOTE: An alert is generated to the user based on the configuration set (Enabled/Disabled). The alert cannot be assigned to the severity levels (High/Medium/Low), as reported by the application. Automatic Close:
• If set to Disabled (Default), VHQ will generate alerts whenever Device reports application alerts, even if one open alerts exists.
• If set to Enabled, VHQ will generate alerts whenever a Device reports application alerts even if one open alerts exists. You can view the alert information under the following screens under Description column. Hover over the description to view the details. Dashboard Screen, Alert History Screen, Open Alerts Screen and Edit User Screen.
To view and close an alert:
To view and close alert(s):
The Alert History Report can be used to generate a report of all alerts in the VHQ system. The following filter conditions are available in this Report.
NOTE: Alerts that are in the CLOSED state are automatically purged from the VHQ system after 30 days have elapsed from the date these alerts were generated. Alerts that are in the OPEN state will get automatically purged from the VHQ system after 90 days have elapsed from the date these alerts were generated. Once alerts are generated, it should be reviewed by VHQ users and the status of these alerts should be marked as CLOSED from the Open Alerts screen in the VHQ GUI.
The purge durations given above are configurable values. You can contact VHQ Administrator if you want to change these values or if you want to verify the current purge duration for alerts.
To view alert history:
NOTE: If you have set your device filter to the hierarchy Verifone >> South >> Texas >> Dallas in the Device Search, then the data in the Alert History Report will be for the devices that are in the hierarchy Verifone >> South >> Texas >> Dallas.
NOTE:
Severity of an alert - The severity of the alert can be configured through Administration > Alert Administration option sequence.
Alert notification - An alert notification email can be configured through Administration > User Administration > User Profile option sequence.
Subscribe alerts - At the top-right corner, logged in user can view their details. The Profile option is selected in order to display the User Profile window. To configure email, click Edit Profile and Subscribed Alerts. Enter your email address and then click Save.
The user can edit the following alert parameters:
For more details on how to edit an alert parameters, refer to the Alert Administration section.