4 results found
-
PRTG: Native MFA for Local PRTG Accounts
Priority: High (KRITIS-relevant, multiple customer requests)
Description:
Customers require native Multi-Factor Authentication (MFA) for local PRTG accounts without dependency on external Identity Providers (Azure AD, Okta).Current State:
MFA only available via SSO/SAML with external IdP
No native MFA for local user accounts in PRTG Network Monitor/Enterprise MonitorCustomer Requirements:
Security-by-design instead of reactive implementation via third-party providers
Digital sovereignty – avoid dependency on US hyperscalers (Azure AD)
KRITIS compliance without additional infrastructure (IdP)4 votes -
Auto-Map Network Topology Using LLDP/CDP Discovery Data
As a Network Engineer, I want PRTG to automatically map network devices and their interconnections on maps using LLDP/CDP neighbor data — including port-level connection details — so that I can maintain an accurate, up-to-date network topology visualization without manual effort, and leverage the same discovery data to automatically configure device dependencies.
Should also be great if this can be used together with autodiscovery. But adding device to a map will auto connect to the devices in this same map with port info.
1 vote -
Deep Search Across Monitored Sensor Values for Asset Identification
As a Systems Engineer, I want to search across current (and historical) sensor values — such as SNMP-learned data and custom sensor results — so that I can quickly identify a device in PRTG using identifiers like a serial number or asset tag, without needing to know the hostname or IP address.
Request: Please add an advanced search option that can search across current (and ideally historical) sensor values, including SNMP and custom sensor results.
Use case: We often only have a serial number / asset tag from inventory or field service and need to quickly identify the corresponding device…
1 vote -
Dynamic Device Naming via SNMP sysName with Customizable Name Templates
As a Network Engineer,
I want PRTG to automatically populate and update device names based on SNMP sysName (OID 1.3.6.1.2.1.1.5.0) — with support for customizable name templates similar to the existing Port Name Templates —
so that device names in PRTG always reflect the actual configured hostnames on my devices, eliminating the need to maintain naming in two separate places.2 votes
- Don't see your idea?