Data exchange between Managed clusters and Mission Control

All DESK Managed clusters exchange information with DESK Mission Control, at least once, or periodically. You may want to opt-out of certain communications, such as allowing DESK to proactively access your clusters and environments. However, some messages are mandatory and can't be switched off. The purpose of this topic is to transparently document the data that DESK receives from and pushes to your clusters. Note that all communication between clusters and Mission Control is encrypted and always cluster-initiated only. DESK isn't able to initiate a connection to customer clusters.

Installation

Frequency: Once during installation and during every upgrade
Cluster request: License key
Mission Control response: Account name, license name, OneAgent installation flag (true/false), OneAgent download URL

Registration

Frequency: Once (after first startup)
Cluster request: License key, cluster ID
Mission Control response: Registration status, username, password

License

Frequency: Once every 5 minutes
Cluster request: -
Mission Control response: License status, cluster ID, license key, license details, license model

Health check

Frequency: Once every 5 minutes
Cluster request: Cluster ID, privacy settings, time zone, traffic size, update/maintenance window. Each cluster node adds technical details including OS name and version, number of CPU cores, CPU load, total RAM, free RAM, total disk storage, used storage, server state, master node flag (true/false), and startup time stamp. Each Cluster ActiveGate adds its version, OS name and version, status, certificate issuer, and type (e.g., beacon forwarder).
Mission Control response: Health status, message

Consumption

Frequency: Once each hour
Cluster request: Cluster ID, consumption timeframe. Each environment adds the number of new problems, RUM sessions, synthetic monitors. Every host adds a category, a list of monitored technologies, and monitoring timeframes. For each synthetic monitor, the ID, description, type, success count, failure count and action count are transmitted.
Mission Control response: Status, remaining RUM sessions, consumed RUM overage, host units overage, remaining synthetic monitors, consumed synthetic monitors overage. For each environment, its ID, consumed RUM sessions, consumed synthetic monitors, and host units are returned.

Heartbeat

Frequency: Once each minute, or every 5 minutes if remote access is disabled.
Cluster request: Cluster ID, node ID, source type (e.g., server)
Mission Control response: Remote UI request flag (true/false), Websocket URLs

Updates

Frequency: Once each hour
Cluster request: n/a
Mission Control response: For cluster updates: version, description, download URL, size. For OneAgent and JavaScript tag updates: label, version, download URLs. For ActiveGate updates: label, version, download URLs