Pinger

← Back to Docs

Cloud Sync Guide

Understanding cloud sync features, benefits, and how it works

What is Cloud Sync?

Cloud sync connects your local Pinger agent (desktop app or Docker) to Pinger's cloud service. Your agent checks in every 30 seconds, reporting device status and receiving configuration updates. This enables remote monitoring, automatic alerts, and internet outage detection.

Key Features

🌐

Internet Outage Detection

The cloud expects to hear from your agent every 30 seconds. If your agent stops checking in for 90 seconds, the cloud knows your location's internet is down and sends you an alert.

This works even when your local system can't reach you - the cloud handles the alerting.

📧

Automatic Email Alerts

No SMTP configuration needed. The cloud handles all email delivery automatically with mobile-optimized templates.

  • Device down/recovery alerts
  • Agent offline/online alerts
  • Smart batching to prevent spam
  • Critical device priority
📊

Remote Access Dashboard

Access your monitoring dashboard from anywhere at ping.wbmtek.com

  • View all agents and devices
  • Real-time status updates
  • Alert history and trends
  • Manage devices remotely
🏢

Multi-Location Management

Manage unlimited agents from one dashboard. Perfect for organizations with multiple buildings or remote sites. Each location reports independently, and you see everything in one place.

🔄

Bidirectional Sync

Changes made in the web dashboard sync to your agents automatically. Add devices, update settings, or configure alerts from anywhere - your agents receive updates within 30 seconds.

📈

Alert History & Analytics

All alerts are stored in the cloud for 30 days (free tier). Review past incidents, identify patterns, and track uptime trends over time.

How It Works

1

Agent Monitors Locally

Your agent pings devices on your local network every 15-30 seconds. This happens locally and doesn't require internet.

2

Heartbeat to Cloud

Every 30 seconds, your agent sends a "heartbeat" to the cloud with device status updates. The cloud records this and resets a 90-second timeout timer.

3

Cloud Processes Changes

The cloud compares device status with previous state. If a device went down or came back up, the cloud sends email alerts according to your alert rules.

4

Config Sync Back

The heartbeat response includes any configuration changes from the dashboard. Your agent receives new devices, updated settings, or alert rules automatically.

5

Timeout Detection

If your agent stops checking in (internet down, power out, etc.), the 90-second timer expires. The cloud marks your agent as offline and sends an "agent offline" alert.

Cloud Sync vs Standalone

FeatureStandaloneCloud Sync
Local device monitoring
Email alertsSMTP required✓ Automatic
Remote access
Internet outage detection
Alert historyLocal only30 days cloud
Multi-location management
Cloud monitors (HTTP/TCP/DNS)
Account requiredFree account

Privacy & Security

✓ What's Sent to Cloud

  • Device names and IP addresses
  • Device status (ALIVE or DEAD)
  • Agent metadata (name, location, version)
  • Timestamp of last check

✗ What's NOT Sent

  • Network traffic or packet contents
  • Device credentials or passwords
  • Personal data or files
  • Detailed network topology

🔒 Security

  • All communication over HTTPS/TLS
  • API key authentication
  • Data encrypted at rest and in transit
  • OAuth 2.0 for user authentication

When to Use Standalone

Choose standalone mode if:

← Docker GuideGet Started →