-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New table option breaks OID numbers #60
Comments
Hi @igorrev, That's certainly a strange one, the code shouldn't make any changes to the middle of the OID string like that. Is there any chance that you can share the config you used and just a straight walk of the cvCallVolPeerTable (.1.3.6.1.4.1.9.9.63.1.3.8.4) please? |
Here is Logstash minimal config especial for this issue. Only snmp input and file output, no filters applied. It's only a part of more complex config but I'm sure it's independent from other parts.
Here is output file. I cut out only significant parts.
As you can see if index value exists in OID in "9.9.63.1.3.8.4.1" part it cuts off at first occurrence and concat to the the end. Also everything is OK with other Index>=10. I don't have peer with index=63 so I haven't results for this one. |
Additional info.
|
All good. I've found my mistake. I used sub instead of chomp. 🤦♂️ I'll get a fix up for it asap. |
Fix is included in PR #59 . |
@igorrev Latest release includes the fix for this, want to give it a go? |
New
table
option is great and very useful.But look what happens with OIDs.
I take two tables: 1.3.6.1.4.1.9.9.63.1.3.8.4.1.1.someindex and 1.3.6.1.4.1.9.9.63.1.3.8.4.1.2.someindex
For example, someindex = 41. Results are good:
But if someindex=1 results are wrong (take a look to OIDs):
Where is "1" between "9.9.63" and "3.8.4" ? What's the "1" on the tail ?!
If someindex=8 results are different but wrong too:
Where is "8" between "9.9.63.1.3" and ".4.1" ? What's the "8" on the tail ?!
I think it's some OID string cut and concat issue. Sorry but
table
feature is not really working now :(The text was updated successfully, but these errors were encountered: