| Deployment model | Customer-controlled Linux Core, one Universal Sensor software with Network, Infrastructure, Flow and Log roles, and Windows/Linux host Agents. Automatic Sensor selection, distributed pools and two-Core Active/Standby HA support the deployment. | Self-hosted Network Monitor and hosted service; Enterprise options for larger deployments. Documented · Source 1 ↗ Source 2 ↗ |
| Network / SNMP | Discovery, SNMP device/interface health, routing neighbors, overlays, network services, active paths and topology. Connect control-plane state, interface quality, service reachability and recent changes. | Network/device monitoring through SNMP and protocol sensors. Documented · Source 1 ↗ Source 2 ↗ |
| Flow analytics | NetFlow, IPFIX and sFlow ingestion with exporter, interface, application and site context. Traffic trends, conversations, top talkers and sampling quality feed investigation and capacity planning. | NetFlow, jFlow, sFlow and IPFIX sensors. Documented · Source 1 ↗ |
| Log monitoring / analytics | Syslog, structured logs and operational events with search, parsing, source identity and incident context. Connect logs to metrics, topology, flow and configuration changes under access and retention policies. | Syslog and Windows-event monitoring with filtering and alerts. Syslog Receiver is UDP-only; PRTG complements dedicated log-management/SIEM platforms. Documented · Source 1 ↗ Source 2 ↗ |
| OpenTelemetry / OTLP | Governed OTLP metrics, logs and bounded span evidence with resource identity, search and dependency context. Apply telemetry budgets, privacy rules and retention. The focus is operational observability across the estate. | OpenTelemetry compatibility is advertised; native OTLP ingestion and precise signal coverage require verification for the selected PRTG deployment. Not verified · Source 1 ↗ |
| Packet visibility / DPI | Bounded, incident-triggered packet evidence supports focused network diagnosis. Capture is governed by scope, duration, resource and privacy controls; it is not an always-on full-DPI platform. | Packet-sniffing sensors; collection location, classification and performance scope matter. Scope dependent · Source 1 ↗ |
| Network configuration | Separate AmrudAi NCM product: backup, version history, semantic diff, drift, golden-state and policy checks, controlled CLI, staged/canary execution and firmware workflows. Approval, pre/post-checks, audit and adapter-supported rollback keep privileged changes under control. | PRTG UVexplorer adds configuration management as a separately installed extension. Integration · Source 1 ↗ |
| IP address management | Prefix/subnet hierarchy, discovery reconciliation, address history, conflicts, DNS/DHCP context and utilization planning. Keep address identity and changes connected to the monitored inventory. | Authoritative IPAM lifecycle capability was not established in this review. Not verified · Source 1 ↗ |
| Infrastructure / cloud / Kubernetes | Host, endpoint, virtualization, storage/SAN, cloud-resource/network and Kubernetes monitoring. Connect Windows/Linux Agents and agentless collection with account, region, workload and dependency context. | Server, VM, hardware and cloud sensors; verify exact Kubernetes/container requirements. Scope dependent · Source 1 ↗ |
| Applications / databases | Database availability, sessions, waits/blocking, replication, query-change evidence and synthetic service checks. Connect database, host, storage and network prerequisites to service behavior; developer profiling and RUM are separate categories. | Database/application monitoring sensors; full tracing/APM depth requires separate evaluation. Scope dependent · Source 1 ↗ |
| AI investigation / root cause | Evidence-led RCA, learned correlation, adaptive baselines, graph-based context and AI Copilot assistance. Show competing hypotheses, supporting and contradictory evidence, next checks and human control over privileged actions. | Dependencies and unusual-behavior detection are documented; automated generative RCA equivalence not established. Scope dependent · Source 1 ↗ |
| Alerting / response | Telemetry trust, semantic health states, persistence/flapping controls, maintenance context, event grouping and contextual notifications. Cross-region and multi-vantage Sensor qualification distinguish local paths, collector faults and service impact. | Threshold/status/escalation/dependency alerts and multiple notification methods. Documented · Source 1 ↗ |
| Topology / dependencies | Temporal topology and service dependencies connect entities, paths, workloads, change history and business services. Reconstruct incident-time relationships and distinguish lost redundancy from actual service outage. | Maps; UVexplorer adds automated Layer 2 discovery/topology. Integration · Source 1 ↗ |
| MSP / tenant model | Shared multitenant and dedicated customer deployment models with tenant boundaries and provider workflows. Customer-specific access, branding, Sensors, service commitments, reports and HA support managed operations. | User/object access controls for MSP use; vendor distinguishes this from native tenant isolation. Scope dependent · Source 1 ↗ Source 2 ↗ |
| Disconnected operation | Customer-managed deployment, offline packaging and deterministic monitoring/investigation without a mandatory hosted LLM. Optional external connectors and hosted AI services use connectivity according to your policy. | Self-hosted operation and manual Enterprise activation supported with license/renewal conditions. Scope dependent · Source 1 ↗ |
| Extensibility | Capability Packs, MIB/API Studio, open telemetry, ITSM/CMDB, webhooks and service workflow integrations. Versioned connectors, identity reconciliation, approval boundaries and audit keep integrations accountable. | Custom sensors, scripts, REST-based integrations and API. Documented · Source 1 ↗ |
| Commercial model | Scope-based enterprise and MSP proposals covering the monitored estate, deployment, telemetry and support. Request a written proposal for entitlements, retention, services and commercial terms; no unverified price or savings is assumed. | Sensor-based subscription tiers; Hosted/Enterprise and UVexplorer pricing/licensing differ. Documented · Source 1 ↗ Source 2 ↗ |