Skip to content
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

This filter may not work in Elasticsearch 2.0 #13

Open
webmstr opened this issue Nov 2, 2015 · 1 comment
Open

This filter may not work in Elasticsearch 2.0 #13

webmstr opened this issue Nov 2, 2015 · 1 comment

Comments

@webmstr
Copy link

@webmstr webmstr commented Nov 2, 2015

If you have a trap that is not fully parsed (all elements are not found in the mib), this filter will make new fields based on the object id. Unfortunately, these contain periods, which are not allowed in ES2.

Example: 1.3.6.1.4.1

There are a couple of solutions for this, which could be combined to make the input more useful:

For unknown IDs, make a better string, e.g. 1_3_6_1_4_1.

Allow the user to define what to do with unknown IDs, e.g. "skip_unknown" => true

Having the skip feature would allow users to keep just what they wanted by limited the mib definition to just the fields that interested them. Two birds with one stone...

Note that traps change all the time - vendors add new ids, etc - and keeping the mibs perfectly up to date is typically not possible.

@ABitMoreDepth
Copy link

@ABitMoreDepth ABitMoreDepth commented May 27, 2016

I've just bounced off this problem where we are supplied with mibs that aren't complete/malformed etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.