Help to ignore/drop Index values

[kommuri-bharath]

Hi Team,

I am new to SNMP Exporter and still trying to learn on how to use the tool effectively. In this process, I would like your help on how to write the code to ignore a Index. For Ex:

HELP jnxIkeTunMonDPDDownCount The number of times that the remote peer is detected in a dead (or down) state. - 1.3.6.1.4.1.2636.3.52.1.1.2.1.27
TYPE jnxIkeTunMonDPDDownCount counter
jnxIkeTunMonDPDDownCount{jnxIkeTunMonIndex="16776278",jnxIkeTunMonRemoteGwAddr="169.254.198.25"} 0
jnxIkeTunMonDPDDownCount{jnxIkeTunMonIndex="20557681",jnxIkeTunMonRemoteGwAddr="125.19.241.146"} 0
jnxIkeTunMonDPDDownCount{jnxIkeTunMonIndex="20567738",jnxIkeTunMonRemoteGwAddr="114.143.226.250"} 0
jnxIkeTunMonDPDDownCount{jnxIkeTunMonIndex="20575658",jnxIkeTunMonRemoteGwAddr="197.159.210.99"} 0
jnxIkeTunMonDPDDownCount{jnxIkeTunMonIndex="20586429",jnxIkeTunMonRemoteGwAddr="159.148.32.10"} 0
jnxIkeTunMonDPDDownCount{jnxIkeTunMonIndex="20611667",jnxIkeTunMonRemoteGwAddr="62.119.80.113"} 0

From the above output I want to ignore the "jnxIkeTunMonIndex" and only receive "jnxIkeTunMonRemoteGwAddr" values in the output.

I wrote the code like below:
lookups:
- source_indexes: [jnxIkeTunMonRemoteGwAddr]
lookup: jnxIkeTunMonIndex
overrides:
jnxIkeTunMonIndex:
ignore: true

I am able to achieve what I wanted (at least not able vanish "jnxIkeTunMonIndex" values but able to get NULL values). But, I see there are two entries for jnxIkeTunMonRemoteGwAddr OID and when there is no value for "jnxIkeTunMonIndex".. these two entries are shown as duplicate and curl is throwing an error like below:

An error has occurred while serving metrics:

389 error(s) occurred:

• collected metric "jnxIkeTunMonEncryptAlgo" { label:<name:"jnxIkeTunMonIndex" value:"" > label:<name:"jnxIkeTunMonRemoteGwAddr" value:"202.125.133.182" > gauge:<value:6 > } was collected before with the same name and label values
• collected metric "jnxIkeTunMonOutPkts" { label:<name:"jnxIkeTunMonIndex" value:"" > label:<name:"jnxIkeTunMonRemoteGwAddr" value:"202.125.133.182" > counter:<value:78 > } was collected before with the same name and label values
• collected metric "jnxIkeTunMonState" { label:<name:"jnxIkeTunMonIndex" value:"" > label:<name:"jnxIkeTunMonRemoteGwAddr" value:"91.240.56.25" > gauge:<value:1 > } was collected before with the same name and label values
• collected metric "jnxIkeTunMonLifeTime" { label:<name:"jnxIkeTunMonIndex" value:"" > label:<name:"jnxIkeTunMonRemoteGwAddr" value:"203.135.5.51" > gauge:<value:10715 > } was collected before with the same name and label values
• collected metric "jnxIkeTunMonLocalRole" { label:<name:"jnxIkeTunMonIndex" value:"" > label:<name:"jnxIkeTunMonRemoteGwAddr" value:"46.193.136.90" > gauge:<value:2 > } was collected before with the same name and label values

Could someone please help me on either ONE of the below:

1. How to ignore/remove "jnxIkeTunMonIndex" so that I will receive values only for "jnxIkeTunMonRemoteGwAddr".
   OR
2. How to ignore the duplicate values from above output.

Expected outputs are:

HELP jnxIkeTunMonDPDDownCount The number of times that the remote peer is detected in a dead (or down) state. - 1.3.6.1.4.1.2636.3.52.1.1.2.1.27
TYPE jnxIkeTunMonDPDDownCount counter
jnxIkeTunMonDPDDownCount{jnxIkeTunMonRemoteGwAddr="169.254.198.25"} 0
jnxIkeTunMonDPDDownCount{jnxIkeTunMonRemoteGwAddr="125.19.241.146"} 0

OR
** Should ignore the duplicate entries (actually they are not duplicate but when jnxIkeTunMonIndex is null they come as duplicate
HELP jnxIkeTunMonDPDDownCount The number of times that the remote peer is detected in a dead (or down) state. - 1.3.6.1.4.1.2636.3.52.1.1.2.1.27
TYPE jnxIkeTunMonDPDDownCount counter
jnxIkeTunMonDPDDownCount{jnxIkeTunMonIndex="",jnxIkeTunMonRemoteGwAddr="169.254.198.25"} 0
jnxIkeTunMonDPDDownCount{jnxIkeTunMonIndex="",jnxIkeTunMonRemoteGwAddr="169.254.198.25"} 0

Thanks in advance !!

[bastischubert]

looking at the mib: do not remove the jnxIkeTunMonIndex as it's necessary to produce correct output.
jnxIkeTunMonDPDDownCount is deprecated and shouldn't be used in new setups anyway.

if you have further questions please try to format your text as good as you can

[kommuri-bharath]

Thank you very much @bastischubert for the reply.

Argos team says that the value for jnxIkeTunMonIndex keeps changes and this is producing a leak in ARGOS. This is the reason they want me to get rid of that value.

I will check on what I can do @bastischubert. And for the "format your text" suggestion, I am thinking that the text in my question confused you. Next time I will write the questions with better formatting.

[bastischubert]

No worries, just try to use formatting on you output and it will instantly be readable 🤣
What is ARGOS?

[kommuri-bharath]

Argos is the monitoring platform which is deployed with ArgoCD. Basically we are using ARGOS to ask prometheus to connect to targets and store the data.

[SuperQ]

This sounds like a bug in whatever "ARGOS" is. This component does not seem to exist in the ArgoCD documentation.

Without having public documentation for this component there is no way for anyone here to help.

[kommuri-bharath]

Understood @SuperQ , I will check internally on what can be done.

Thank you all for your extended support.