Server map

The Overview shows a dot-matrix world map of your servers on the left, and the list of services and servers on the right.

What the map showsCopy Anchor Link

• One marker per server: green, yellow or red for OK, warning or down; it blinks while the server is down. The master is a blue diamond: click it to see the agents that report to it, its monitors, outages and requests.
• Dashed lines are the report links from the agents to the master.
• Request flows: arcs from countries to your servers. The more requests, the thicker the line, and the dots move at the real request rate. The top left lists the countries with the most requests in the last minute. Hover a line to see "country → server: number of requests".
• The list on the right switches between services and servers, can be searched, and groups can be collapsed or located on the map. Hovering a row highlights its server on the map. The servers tab also lists the 3R Monitor master itself.

Click any server (a marker, a row in the list or a card below the map) to open its side panel: CPU, memory, disk, load, bandwidth, requests and request sources (last minute and 24 hours), charts of the last 30 minutes, services and software. Full details opens the details page.

Map controlsCopy Anchor Link

Where request sources come fromCopy Anchor Link

Every 3 seconds the agent reads the new lines of the server's Apache and Nginx access logs, counts the requests per IP and sends the counts to the master. Once a minute it also sends the paths and User-Agents of the 100 most active IPs.

• The usual log locations on Debian, RHEL, aaPanel, cPanel, Plesk and XAMPP are found automatically. For other locations, set access_logs in /etc/3rmonitor/agent.conf (comma-separated, wildcards allowed), or off to turn request statistics off on that server.
• The master maps IPs to countries offline, with the DB-IP country database included in the package and updated monthly (you can turn the update off in Settings → Map). IPs are never sent to any third party. Per-IP statistics stay on the master (30 days by default), for the Traffic page and the blocklist.
• Requests that come through Cloudflare only show Cloudflare's nodes, and are marked "Via Cloudflare", unless the origin server restores the real visitor IP. See Cloudflare tips.

Server positionsCopy Anchor Link

Each server is placed, in this order of preference:

1. the city or coordinates set in Servers → Settings → Map location;
2. the country of its public IP;
3. its time zone;
4. the master's position (for the agent that runs on the master).

The master's position is set in Settings → Map: choose a Master city (it fills in the latitude and longitude) or enter the coordinates, and optionally a Master display name. If you leave the coordinates empty, the master is placed in the country of its own public IP, which it finds the same way agents do, or else at the main city of the panel's time zone (Settings → General).

Linking a monitor to a server (Runs on server, in the monitor) highlights that server on the map when you hover the monitor.

Labels and notesCopy Anchor Link

• Each location has a label card. The first line is the server name and IP; the second is its note, set in Servers → Settings → Note, for example "Main site · AWS".
• Several servers in the same city share one card; above 8 servers it shows "N more…". Cards move apart so they never overlap, with leader lines to their markers. Click a row in a card to open that server.
• The IP shown is the public IP: the one set by hand in Servers → Settings → Displayed IP, otherwise the public source address the master sees, otherwise the public IP the agent detects (network interfaces, cloud metadata and, only as a last resort, a query to 1.1.1.1). Private addresses are shown separately as "LAN …".
• Share links only show IPs when Show details is ticked.

Map outlines: Natural Earth (public domain). IP country data: DB-IP IP to Country Lite (CC BY 4.0).