Details

    • New Feature
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Billing
    • None

    Description

      For now, observium bills "what is greater" of in and out traffic on the interface(s).

      Would be nice, if it would be possible to select direction of traffic for billing for each interface in bill, with following options:

      • bigger (as it works now)
      • in
      • out
      • in+out (sum of both)
      • in-out (deduction out from in)
      • out-in (reverse)

      Attachments

        Activity

          [OBS-4709] traffic directions in billing

          I forgot to add most inportant for us feature - deduction of two interfaces.

          For example, we have sw1:e1/1 and sw2:e1/2 interfaces. Resulting value in bill should be equal sw1:e1/1_out_95pct minus sw2:e1/2_in_95pct

          ugenk Evgeniy Kozhuhovskiy added a comment - I forgot to add most inportant for us feature - deduction of two interfaces. For example, we have sw1:e1/1 and sw2:e1/2 interfaces. Resulting value in bill should be equal sw1:e1/1_out_95pct minus sw2:e1/2_in_95pct

          General questions and device support can be discussed in our Discord channel, click here to join.


          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            adama Adam Armstrong
            ugenk Evgeniy Kozhuhovskiy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: