ISP Dude: monitoring, maps, and network operations

Scope

ISP Dude inventories network devices and services, monitors reachability, collects SNMP metrics, and organizes them into operational maps. Each device retains identity, check settings, links, current state, ping history, and the latest SNMP sample.

It complements UISP, cnMaestro, Proxmox, and Radius. Provider details are opened only when brand, MAC, module, and permissions allow it.

Environments

An Environment is an isolated ISP Dude instance containing maps, devices, nodes, links, discovery, queues, and history. Create one per POP or data center that needs independent inventory and monitoring.

Set name, engine, reference Agent, interval, private-IP inclusion, notification delivery, and map style. One Edge Agent serves one ISP Dude Environment and cannot be assigned to two.

Edge Agent or classic monitoring

Use Edge Agent for new environments: it performs ping, TCP/HTTP, SNMP, discovery, and SSH from the private network. Classic MikroTik monitoring remains for compatibility and requires RouterOS API address, port, user, and password.

The choice is explicit and stable. Removing MikroTik credentials does not delete maps, devices, or history, but affected environments must be migrated first.

Create a device

Enter a recognizable name, icon, optional Warehouse brand and normalized MAC, internal and operational descriptions, IPv4 address or FQDN, check type, and service port. ICMP checks host reachability; TCP confirms the selected port; HTTP and HTTPS verify the configured web service. The separate panel port is only a navigation shortcut and does not change monitoring.

Use the real inventory brand when provider integrations depend on it, and do not reuse a host or MAC without a documented reason. After saving, run a controlled check and wait for historical samples before tuning alerts.

Ping and stable state

Edge Agent performs several closely spaced probes, calculates latency and packet loss, and retains results until the server acknowledges them. Offline state is confirmed only after the configured consecutive failed rounds; one transient failure does not necessarily produce a transition.

Manual Ping creates prioritized requests that run sequentially until stopped. Use it for immediate diagnosis, then compare 24-hour uptime, average latency, loss, and sample history. A successful manual ping does not erase an earlier incident and is not a substitute for continuous monitoring.

Network Map

The map contains devices, static nodes, submaps, and links. Context actions create items, open details, and expose UISP, cnMaestro, or SSH when available. Classic, Professional, NOC, and Topology templates render the same data for different operational needs.

Maps and site documentation

Map Management builds a hierarchy inside one Environment. A map can contain devices and child maps; changing its parent changes navigation. Before moving or deleting it, inspect nodes, links, submaps, public-link entry points, and dependent content.

The site panel stores physical address, responsible contact, telephone, operational notes, and images of cabinets, antennas, power systems, or cabling. Keep this field documentation current, avoid unnecessary personal data, and remove obsolete images that could mislead an intervention.

Controlled discovery

Discovery is operator-triggered, requires 2FA, and accepts IPv4 /20 through /32 up to 4096 addresses. The Agent uses ports, reverse DNS, SNMP name, HTTPS certificate, and local ARP MAC to suggest type and icon.

Results are temporary. Operators filter, ignore, import, or drag them into the map; no device becomes permanent automatically.

Problems and notifications

The problem board records incidents and recoveries for each Environment even without delivery recipients. It keeps one open problem per source key, presents active incidents first, retains resolved history for 30 days, and combines open counts in the global badge.

Settings define the consecutive-failure threshold and WhatsApp, email, ISP App push, or Telegram recipients. Telegram accounts must first be linked from their profile. Test buttons send a real message, so choose the intended recipient. Internal history, state threshold, and external delivery are separate controls.

Public links

A public link can be restricted to one IPv4 address, tied to a specific Environment, opened on a selected initial map, and rendered with an inherited or dedicated template. Give it a recognizable administrative label so its purpose and owner remain clear.

Regenerate creates a new token and invalidates the old URL. Disable preserves configuration while preventing access. Review last access, revoke unused links, apply the IP restriction where possible, and ensure shared maps contain no private notes or sensitive technical details.

Checklist

• Separate POPs and data centers into correct Environments
• Use an appropriate Edge Agent for new private networks
• Configure engine, interval, thresholds, and notifications per Environment
• Store the real host, check type, brand, and normalized MAC
• Validate monitored ports independently from panel shortcuts
• Use historical samples rather than one manual ping
• Maintain map hierarchy and site documentation
• Start discovery only with the correct network and 2FA
• Review every temporary result before import
• Select and test notification recipients deliberately
• Restrict, review, and revoke public links