Skip to content
← Welcome to Paessler User Voice!

Settings and activity

1 result found

  1. SNMP Custom Table Sensor: Enable String Value Handling in Channels

    2 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

    1 comment  ·  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  ·  AdminIsidora Jeremic (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
    Heinz Meyer commented  · 

    This is absolutely true. Especially when it comes to monitoring stacks and their members, an SNMP Custom Table Sensor really shines when it’s created by using a device template—for instance: Based on the table indexes, it determines how many sensors need to be created and then dynamically generates them for each stack member. However, it’s also a fact that many (including large) manufacturers, such as Aruba, now return the necessary information about status and so on as a plain string. The named OID's are perfect examples.
    And that effectively rules out the SNMP Custom Table Sensor. The alternatives would be statically created SNMP string sensors, which would either have to be created manually for each stack member, or you would have to come up with complicated workarounds to obtain every relevant table index by other means.

    Heinz Meyer supported this idea  ·