Auto‑Attach Relevant Sensors Based on Service Detection
As a PRTG user, I want discovery and port workflows to detect the services a device offers (e.g., HTTP/S, LDAP/S, SSH, SNMP, databases) and automatically add the most relevant sensors with sensible defaults—so setup is faster and cleanup is minimal.
Hi there,
Thank you again for submitting your idea to Paessler. We truly appreciate you taking the time to share your feedback.
After careful consideration by our team, we've decided to decline this idea at this time. This decision was made based on several factors, which may include:
- It doesn't align with our current product roadmap or strategic priorities.
- The resources required for implementation outweigh the current projected benefits for our user base.
- There are technical limitations that prevent us from moving forward.
- A similar feature is already available or planned in a different way.
While this particular idea won't be moving forward, please don't be discouraged! Your input is incredibly valuable, and we encourage you to continue sharing your thoughts and ideas with us.
Thanks for your understanding and for helping us shape the future of Paessler.
Best regards,
The Paessler Product Team
-
Nabila
commented
i would also appreciate to have flexible template assignment, with clear description what added and what not, to know if there is any blockers for the discovery
-
billy.cole@pheaa.org
commented
Since auto-discovery or even post creation of a port sensor, could attempt to use openssl to get the SSL certificate of the port, be able to create a SSL Certificate sensor for the auto-discovery open port or for post created port sensors.
-
As a systems administrator, I would like to use PRTG's autodiscovery feature to detect the network and its various protocol capabilities. The discovery mechanism should be more detailed, including username and password, to avoid triggering the SIEM system with random connection attempts.