Understanding Device Pollers

Device pollers are a fundamental component of Server Scout's monitoring architecture, allowing you to monitor network devices that cannot run the monitoring agent directly. This guide explains how pollers work and how to implement them effectively.

What is a Device Poller?

A device poller is an existing monitored server in your Server Scout setup that performs double duty. Whilst it continues to monitor itself using the standard agent, it also polls nearby network devices on your behalf. These devices might include switches, routers, printers, IoT devices, or any other network-connected equipment that cannot run the Server Scout agent directly.

The poller acts as a bridge between your network devices and the Server Scout monitoring platform, collecting vital metrics and health data from devices that would otherwise remain unmonitored.

Why Are Pollers Necessary?

Network devices present unique monitoring challenges:

• Agent limitations: Most network devices cannot run monitoring agents due to hardware constraints or operating system restrictions
• Network accessibility: Devices may be located behind firewalls or in network segments that cannot directly communicate with external monitoring services
• Protocol diversity: Different devices use various protocols (SNMP, HTTP, custom APIs) that require local network access to poll effectively
• Latency considerations: Direct polling from external services may introduce unacceptable delays or timeouts

By using a local server as a poller, you overcome these limitations whilst maintaining comprehensive monitoring coverage across your infrastructure.

Assigning a Poller When Adding Devices

When adding a new device to Server Scout, you must specify a poller_id that references an active server currently running the Server Scout agent. This assignment is crucial for proper device monitoring.

The poller selection should consider:

1. Active status: The poller server must be online and running the agent
2. Network connectivity: The poller must have reliable network access to the target device
3. Resource capacity: Ensure the poller has sufficient resources to handle additional polling tasks

Once configured, the assigned poller will automatically begin monitoring the device according to its polling schedule.

The 60-Second Polling Cycle

Server Scout operates on a standardised 60-second polling cycle for devices. During each cycle:

1. The poller checks for updated configuration
2. Polls each assigned device according to its monitoring profile
3. Collects and processes the retrieved data
4. Transmits results back to the Server Scout platform

This consistent interval ensures timely detection of issues whilst maintaining reasonable network overhead.

Configuration Management

The devices plugin automatically fetches its configuration from /api/device-config.php during each polling cycle. This endpoint provides:

• Device connection parameters
• Monitoring profiles and thresholds
• Authentication credentials
• Polling intervals and timeouts

This dynamic configuration system allows for real-time updates to monitoring parameters without requiring agent restarts or manual intervention.

Authentication with Per-Device API Keys

Server Scout implements per-device API keys for secure authentication between pollers and the monitoring platform. Each device receives a unique API key that:

• Restricts access to device-specific data
• Enables detailed audit trails
• Allows for granular permission management
• Facilitates key rotation without affecting other devices

These keys are automatically managed through the configuration API, ensuring secure communication throughout the polling process.

Best Practices for Poller Placement

Effective poller deployment requires careful consideration of network topology and performance requirements:

Same Subnet Deployment

Position pollers within the same subnet as their target devices when possible. This approach:

• Minimises network latency
• Reduces dependency on routing infrastructure
• Simplifies troubleshooting

Low Latency Requirements

Select pollers with consistently low latency to target devices. High latency can cause:

• Polling timeouts
• Inaccurate performance metrics
• False alerts

Redundancy Planning

Consider implementing poller redundancy for critical devices:

• Deploy backup pollers in different network segments
• Monitor poller health alongside device metrics
• Establish clear failover procedures

Resource Management

Monitor your pollers' resource utilisation:

• CPU usage during polling cycles
• Memory consumption for data buffering
• Network bandwidth utilisation

By following these practices, you'll establish a robust and reliable device monitoring infrastructure that scales with your organisation's needs.