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

mapping Varbinds to fields is causing runaway field counts... #53

Open
peelman opened this issue Jan 2, 2018 · 2 comments
Open

mapping Varbinds to fields is causing runaway field counts... #53

peelman opened this issue Jan 2, 2018 · 2 comments

Comments

@peelman
Copy link

peelman commented Jan 2, 2018

https://github.com/logstash-plugins/logstash-input-snmptrap/blob/f0478381ff1f1a15dd7b2356d8b1ab27857d0666/lib/logstash/inputs/snmptrap.rb#L85

By trying to map every varbind to a field, we are rapidly exceeding the field count maxes in ElasticSearch. Raising that field count continuously isn't something that should be advocated.

It would be better to dump the varbinds into a single field and let a filter take care of extracting any relevant data.

@vsboost
Copy link

vsboost commented Nov 26, 2019

Im getting heaps of these with this change.

[logstash.inputs.snmptrap ][main] Failed to create event {:trap_object=>"#<SNMP::SNMPv2_Trap:0x159697d8 @request_id=928213, @error_index=0, @error_status=0, .......

@yongbuzhibu
Copy link

Im getting heaps of these with this change.

[logstash.inputs.snmptrap ][main] Failed to create event {:trap_object=>"#<SNMP::SNMPv2_Trap:0x159697d8 @request_id=928213, @error_index=0, @error_status=0, .......

hello, I also getting the same err mesage, how do you fix it?

@edmocosta edmocosta transferred this issue from logstash-plugins/logstash-input-snmptrap May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants