Hello,

I'm planning to leverage Linux TC queues to be able to implement trafic from/to a specific IP address in Centreon.

My primary idea is to be able to graph each iSCSI multipath connection independently.

I plan to rely on this project extending SNMPd with custom OID providing metrics per TC queue:

https://github.com/mum4k/tc_reader/

It provides two modes, one showing metrics for a single queue and another one aggregating two queues together to emulate input/output.

Format is described like this:

myOID data will be in this hierarchy:
myOID.1 - tcIndexLeaf                   - Stores integers, the SNMP indexes assigned to Qdiscs and Classes.
myOID.2 - tcNumIndexLeaf                - Stores an integer, the count of indexes assigned to Qdiscs and Classes.
myOID.3 - tcNameLeaf                    - Stores strings, the names of Qdiscs and Classes. Names are in the form "eth0:2:3", which means interface eth0, Qdisc 2, Class 3.
myOID.4 - sentBytesLeaf                 - Stores counter32, the sent bytes for each tcIndex.
myOID.5 - sentPktLeaf                   - Stores counter32, the sent packets for each tcIndex.
myOID.6 - droppedPktLeaf                - Stores counter32, the dropped packets for each tcIndex.
myOID.7 - overLimitPktLeaf              - Stores counter32, the over limit packets for each tcIndex.

You can further configure user names, by assigning two specific tcNames to user names. One as upload and the other one as download direction. If this is configured, the output will further contain:
myOID.8 - tcUserIndexLeaf               - Stores integers, the SNMP indexes assigned to the configured user names.
myOID.9 - tcUserNumIndexLeaf            - Stores an integer, the count of indexes assigned to the configured user names.
myOID.10 - tcUserNameLeaf               - Stores strings, the names of the configured user names.
myOID.11 - tcUserDownBytesLeaf          - Stores counter32, the downloaded bytes for each tcUserIndex.
myOID.12 - tcUserDownPktLeaf            - Stores counter32, the downloaded packets for each tcUserIndex.
myOID.13 - tcUserDownDroppedPktLeaf     - Stores counter32, the dropped packets in download direction for each tcUserIndex.
myOID.14 - tcUserDownOverLimitPktLeaf   - Stores counter32, the over limit packets in download direction for each tcUserIndex.
myOID.15 - tcUserUpBytesLeaf            - Stores counter32, the uploaded bytes for each tcUserIndex.
myOID.16 - tcUserUpPktLeaf              - Stores counter32, the uploaded packets for each tcUserIndex.
myOID.17 - tcUserUpDroppedPktLeaf       - Stores counter32, the dropped packets in upload direction for each tcUserIndex.
myOID.18 - tcUserUpOverLimitPktLeaf     - Stores counter32, the over limit packets in upload direction for each tcUserIndex.

This project also includes some Cqacti configuration files to see how everything links together:

https://github.com/mum4k/tc_reader/tree/master/cacti_templates/snmp_queries

So… The question is: Is that possible to use centreon-plugins to build such query or do I need a custom plugin to implement that ?

If so, can you point me to the proper plugin so I can try myself to play with parameters?

Regards, Adam.