CER - Cisco Emergency Responder

Overview

Cisco Emergency Responder supports emergency-calling location and routing functions integrated with CUCM.

Monitoring

Method

SNMP Exporter plus the cer-exporter CLI collection path through cer-prometheus.

Metrics Collected

• CER service state
• CPU, memory, storage, and interface health
• Emergency Responder application status
• Exporter and scrape health

Grafana Dashboards

• WxCDI CER Detail
• CER SNMP and exporter dashboards are also recorded in the audit.

Logging

Log Source

CER publisher and subscriber nodes send VOS syslog; trap support must be verified against live configuration.

Splunk Index

vos_syslog; the audit does not consistently record a trap index for CER.

Key Log Queries

index=vos_syslog device_type="cer" device_name="<device_name>"

Alerting

Grafana Alert Rules

Alert Name	Severity	Description
CER service health	Varies	Application and platform health conditions.
Scrape down	Critical	Detects loss of CER collection.

Splunk Alerts

Alert Name	Severity	Description
CER VOS events	Varies	Emergency Responder and platform events in vos_syslog.

Notification Flow

CER → Grafana/Splunk → EMS (KeepHQ) → [notification channels]

Inventory

• Repository: VOS inventory
• Update Method: Generated from the managed VOS/Ansible inventory.
• Update Cadence: On CER inventory change through pull request.