Skip to content
← Welcome to Paessler User Voice!

Settings and activity

1 result found

  1. Dynamic Interface Naming with ifIndex-Based Port Identification for SNMP Traffic Sensors

    13 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Sensors  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Gathering Feedback  ·  AdminBenjamin Hackenberg (Admin, Paessler) responded

    Hi there,


    Great news! Your idea has been approved and moved to the next stage on Paessler.


    Before we can commit to developing this idea, we need more input from the community. Your idea has the potential to significantly impact our users, and getting broader feedback will help us understand its full scope and prioritize it effectively.


    Here's how you can help:

    • Share your idea: Encourage other Paessler users to view, comment on, and vote for your idea.
    • Elaborate on your suggestion: Add more details, use cases, or examples to your idea description.
    • Engage with comments: Respond to questions and suggestions from other users.


    The more engagement your idea receives, the better its chances of being fully implemented.


    Thanks for your continued collaboration in making Paessler even better!


    Best regards,

    The Paessler Product Team

    An error occurred while saving the comment
    Joshua Moore commented  · 

    I will add that we have been told by Paessler support that if a description is not present in the SNMP OID on initial SNMP Traffic sensor creation then future description updates on the device will not work without deleting the SNMP Traffic sensor and adding it back again. We don't understand why this logic is necessary and much rather prefer to always scan for description from the device and update PRTG's sensor if it's different in PRTG.

    Joshua Moore supported this idea  · 
    An error occurred while saving the comment
    Joshua Moore commented  · 

    I will also add that interface status (up or down administratively or operationally) should not have any bearing on this feature. PRTG should always poll and update regardless of interface status.

    Joshua Moore shared this idea  ·