Heartbeat Monitoring

Overview

ACS Monitor instances send periodic heartbeat reports to the licensing server. These heartbeats serve as health checks, usage reports, and license validation confirmations. Understanding the heartbeat system helps you monitor your deployment health and troubleshoot connectivity issues.

What is Reported

Each heartbeat from your ACS Monitor instance includes:

Heartbeat Frequency

Heartbeats are sent automatically by your ACS Monitor instance at a regular interval (typically every few minutes). You do not need to configure anything — heartbeats start automatically after installation.

Offline Threshold

If the licensing server does not receive a heartbeat within 10 minutes, the server's status is shown as "offline" in your dashboard. This threshold is configurable by the platform administrators but defaults to 10 minutes.

Heartbeat Response

When the licensing server receives a heartbeat, it responds with the current license status, tier, cap, and whether the instance is within its usage limits. This ensures your ACS Monitor instance always has up-to-date license information, including any cap changes from tier upgrades.

Troubleshooting

Server Showing Offline

If your server shows as offline but your ACS Monitor instance is running normally:

• Check that the server can reach acsmon.com over HTTPS (port 443)
• Verify DNS resolution is working on the server
• Check if a firewall is blocking outbound HTTPS traffic
• Review the ACS Monitor application logs for any heartbeat errors

If your server continues to show as offline after checking the above, contact support@acsmon.com for further assistance.