Prtg Network | Monitor Digiboy

| Metric | Sensor | Average | Peak | Threshold | Status | |--------|--------|---------|------|------------|--------| | Response Time (Ping) | Ping | 2 ms | 15 ms | 50 ms | OK | | CPU Usage | CPU Load | 28% | 94% (spike) | 80% | Warning | | Memory Usage | Memory | 62% | 68% | 85% | OK | | Disk C: Free Space | Disk Free | 18 GB | 18 GB | <10 GB | OK | | Network Traffic (LAN) | Traffic | 4.2 Mbps | 38 Mbps | N/A | OK | | Packet Loss | QoS (Round Trip) | 0% | 2% | >1% | Warning |

| Time Triggered | Sensor | Condition | Action Taken | Acknowledged By | |----------------|--------|-----------|--------------|------------------| | [Date] 14:23 | CPU Load | >80% for 5 min | Email to Admin | [Name] | | [Date] 09:15 | Ping | 100% packet loss | Ticket #INC-42 | [Name] | prtg network monitor digiboy

The name DigiBoy evokes the idea of a digital sidekick—small, tough, and smart. In the context of PRTG, a DigiBoy is typically one of three things: | Metric | Sensor | Average | Peak

Why would you need a DigiBoy? Because standard monitoring assumes a static, wired server. But modern IT pros need to: Why would you need a DigiBoy

The DigiBoy solves this by putting PRTG in your backpack.

To build a PRTG Network Monitor DigiBoy, you will need three core components: a display, a brain, and a data source.