TEMS dashboard not displaying live alarms – SaaS

Overview

If your TEMS dashboard is no longer updating or shows stale alarm data, the issue is typically related to the TEMS Monitoring Service or network latency between your visibility node and repeater systems.

Step-by-step troubleshooting

Check the TEMS Monitoring Service status
- Connect to the TEMS visibility server.
- Run the command:
```
systemctl status tems-monitor
```
- If the service is inactive or failed, restart it using:
```
systemctl restart tems-monitor
```
Confirm dashboard connectivity
- After restarting, refresh the TEMS dashboard.
- If alarms begin updating, no further action is required.
If the service is running but data is still stale
- Check latency or packet loss between the visibility node and repeater station.
- Ensure the network link monitoring process is active.
Still not resolved?
- Save the last 100 lines of the TEMS monitor log (/var/log/tems-monitor.log).
- Contact GTSC and attach the log for deeper analysis.

Expected behavior

During link interruptions, the TEMS dashboard may temporarily display no new alarms while retaining old entries. Once the monitoring link is restored, alarm flow resumes automatically without data loss.

When to escalate to GTSC

If:

The TEMS service is active but alarms remain frozen.
Latency tests show packet loss.
You’ve restarted the service twice within 24 hours without improvement.

GTSC will coordinate with the NOC to investigate potential latency or visibility-path issues.

Additional resources

Understanding TEMS Monitoring Architecture
Network Latency Troubleshooting Guide
Coordinating with the NOC for Alarm Feed Verification