1. Home
  2. Alarms
  3. Alarm Logging to Private Sites

Alarm Logging to Private Sites

CloudReady can distribute alarms and alarm resolutions to sites that you have deployed behind the firewall. This feature can be used for integration with on-premise operations systems and consoles such as Microsoft System Center, Splunk, or Microsoft Operations Manager.

How to Enable

Private site alarm logging can be enabled by clicking on the Manage Private Sites link and then clicking ‘Edit’ for the site that you would like to enable logging for. In the edit page for a site, click the ‘Log Alarms to this Site’ checkbox.

You only need to enable alarm logging for one of your sites and then integrate that site into whatever system you have. All alarms are sent to all sites that have logging enabled. Even if you don’t have alarm logging enabled for a site, the sensors that are running on that site will still get alarms. The alarm and resolution data is distributed to the sites in near real-time.

How to Integrate

Currently the alarm data, with URLs and meta-data about the alarm and sensor, is written to an alarms.log file in the ‘C:\ProgramData\Exoprise\ExoSvcShell’ directory. The alarm data is written using the JSON format.

The alarms.log file is managed carefully so as not to fill up a disk. The log file will not grow larger than 10mb and one backup copy will be kept (alarms.log.bak).

NT Event Log Integration

You can also configure the alarm data to log to the local Application NT Event log where the private site is located. This can make integration with your on-premise alarm management systems very easy. Click ‘Log Alarms to the Windows Event Log’ to enable this feature.

See the NT Event Log Format

High-Availability for Alarm Logging

All alarms are sent to any site that is configured to receive alarm logs. If you would like to only send alarms to a single site but still have it fail-over to other sites in case you have a site outage, you can enable Prioritized Site Logging. Once you do this, alarms will only be logged to the first available site in the list. Available in this context means sites that are contacting our servers.

To configure Prioritized Site Logging:

  1. Configure multiple sites to receive alarms
  2. Go to Admin > Settings
  3. In the setting for Private Site Alarm Logging, click ‘Highest Priority Site Available’ and prioritize the site order

Now, when the alarms are rung the first available site that is set to receive the alarm distribution will get the alarm sent to it and it will be logged to the file or pushed into the NT Event log.

If you want to enable different collection methods on different sites, then don’t configure prioritized site logging, have the alarms go to multiple sites.

Related Articles