Open topic with navigation
An important role of Analytics is to alert you when key resources within your GIS infrastructure stop functioning. For key servers or services, you can configure alarm notifications to be sent directly to phones via SMS or email so that you can act quickly to restore systems that are down.
Alarm notifications are optional and configurable but all alarms always appear in the Reports application.
The Summary tab of the Reports application is arranged specifically so that you see the most urgent alarms when you first open the application. Most of the data in the Status tab is also arranged by resource and level of urgency to help you troubleshoot and get to the root cause of any problems within your system.
Similarly, the navigation, links and interactivity of each part of the Reports application is designed to make it easy to drill down deeper into your GIS system to quickly get to detailed information about an alarm and it's source.
An alarm and an error in Analytics are not equivalent, but have a very specific meaning based on how the information is collected.
When you are troubleshooting an alarm, you are likely to respond with a sequence of actions similar to those outlined below. The example is not an exact procedure but gives some sense of the steps you can take to find the source of a problem.
If you are set up to receive alarm notifications on your phone or email, you are likely to begin the process after you receive either a text message (SMS) or an email notifying you of the alarm.
An example of how to investigate an alarm:
Open the Reports application and examine the Summary tab.
Notice that it shows an alarm for ArcGIS Server. Something is obviously wrong.
Click the orange Alarm block.
The Status tab opens showing the Content Panel where the ArcGIS Server Alarms and the Services Alarms are listed in table Content Panels.
First check the ArcGIS Service Alarms to see if there is an issue with the ArcGIS Server itself. In this case, there are no alarms on the Server itself.
Next, check the Services Alarms. In this case, there is an alarm on a service.
The source of the alarms could be one of several possibilities.
The response from the service took longer than expected to check if the service is available.
You can remove the response time criteria from the alarm altogether so that an alarm only fires when a service is unreachable.
To go to the corresponding ArcGIS Service, click the link listed in the table for that alarm entry. The icon beside the link indicates that the link goes to an external web page.
If the content page in ArcGIS Service opens in a new browser tab, it indicates that the Service is working and it is likely the source is slow or the service is not configured to collect data correctly.
If the content page does not open, it is likely that the service is not available.
Even if the ArcGIS map service page loads successfully, it may load in an invalid state, for example, the exported map image is broken. A broken map indicates that something is wrong with the service on ArcGIS Server, and you need to investigate the service itself.
In Geocortex Analytics you can do any of the following with Alarms:
Silence an alarm for a specific period: Silences an alarm for the period that you specify.
The alarm icon changes to show that the alarm is silenced:
Once the silenced time period is over, the alarm returns to the no-alarm state:
If the probe fires and the alarm condition remains, the alarm fires again and the alarm icon shows that the alarm has triggered again:
You can also silence an alarm to prevent it firing if you know of an alarm condition ahead of time and do not want it to fire. The options to silence an alarm are present even if the alarm has not fired.
When you clear or silence an alarm in the System Active Alarms table, it disappears from the table rather than shows as a silenced alarm. If the alarm persists, then the alarm appears in the Active Alarms table once more once Analytics fires the alarm again.
If you silence an alarm in an alarm state and you then enable it, it returns to a non-alarm state
until another alarm is triggered. So when the silence period expires, the alarm does not return to the Active Alarms table until another alarm is fired.
To clear an alarm:
To clear an alarm once, click the down arrow beside the alarm icon, and then click Clear Alarm.
The alarm disappears from the Active Alarms list.
To silence or enable an alarm:
To silence an alarm for a specific time period, click the down arrow beside the alarm icon, and then select a time period that you want the alarm silenced.
The alarm icon changes to show that the alarm is silenced.
To enable a silenced alarm, click the down arrow beside the silenced alarm icon.
The pop-up shows you how much time remains of the silenced state.
Click Enable Alarm.
The alarm returns to the no-alarm state:
If the alarm conditions persists when Analytics fires again, the alarm returns to the alarm state:
Analytics does not, and should not, fire service alarms that have been deliberately disabled. Analytics alarms do distinguish if a service is intentionally disabled not unintentionally down. The alarm is checking for the services that are unintentionally down and will only fire alarms on services that are supposed to be up but are not.
Referenced services alarms and content alarms are not enabled by default and so no information about them is collected unless the service is manually enabled and the alarms configured on the Services Settings tab in Configuration. If the service has not been enabled, the disabled icon is shown in the first column of the table in the alarms panel.
Alarms for the following Status panels must be manually configured if you want alarms to be fired on their services or content:
ArcGIS Online - Content Alarms
Portal for ArcGIS instance - Content Alarms
Essentials Site - Referenced Services Alarms
Geocortex Application instance - Referenced Services Alarms
Web Applications - Referenced Services Alarms
To manually enable an alarm in the Service Settings:
To manually disable an alarm in the Service Settings table: