# Remote Agents In Short
Remote Agents allow EasyDCIM to distribute infrastructure-local tasks away from the main EasyDCIM App. In EasyDCIM 1.25.0+, the Remote Agent is managed as a Docker-based service by easydcim-control.
The communication between the main platform and the Remote Agent is based on HTTP/HTTPS. In the default deployment model, the agent service listens on 8080/8081, while the rest of the stack is handled by Docker containers on the host.
# Do I need a Remote Agent?
By default, a local Remote Agent is installed together with the main EasyDCIM stack when you run:
easydcim-control app install --key 'LICENSE_KEY'
If you have only one location or your network configuration allows it, the local Remote Agent is often enough.
If you have multiple locations spread around the world, you should install an additional Remote Agent for each location. Each agent can then be responsible for:
- operating system installation,
- polling and data collection,
- IPMI proxy operations,
- other infrastructure-local automation tasks.
# Remote Agent Summary
Each Remote Agent has a summary view in the EasyDCIM backend. Use this view to check the current operational state of the agent and to quickly identify polling or queue problems.
The summary may include:
- Connection state - shows whether EasyDCIM can communicate with the agent.
- Polling freshness - shows whether the agent has recently completed its polling cycle.
- Queue / Horizon health - shows whether background workers are processing agent tasks correctly.
- Last poll time - shows when the last polling cycle was completed.
- Polled devices count - shows how many devices were processed by the agent.
- Polling duration - shows how long the latest polling cycle took.
If polling becomes stale or the queue is not healthy, EasyDCIM may also show important notifications and System Verifier warnings. These warnings should be reviewed before graph, monitoring, or provisioning issues are diagnosed at the device level.
For detailed polling troubleshooting, see Remote Agent Polling.
# Requirements
Remote Agents are responsible for executing the Polling Process, which runs every 5 minutes and collects data directly from physical infrastructure (e.g., switches, servers).
- Polling can be I/O- and CPU-intensive, especially with a large number of network devices.
- These agents must operate reliably without introducing delays to data collection.
Recommended specs:
- OS: Debian 12 "bookworm" or Debian 13 "trixie"
- CPU: 4 cores / 8 threads or more
- RAM: At least 8 GB
- Storage: SSD or NVMe
- Network: Direct access to monitored devices; must allow communication with the EasyDCIM server