-
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
SNMP Table support addition #49
Conversation
thanks a lot @axrayn - looking at this! |
Overall looks great! only thing missing are some specs :P |
Oops, my bad! I'll go through and see if I can add some specs and shout out if I get stuck. |
@colinsurprenant Added specs for both the walk and tables functions (and then proceeded to git push before I'd commited the changes 🤦♂️ ) |
@axrayn perfect! all code change LGTM! 🎉
Also, could you squash all code commits into one and the "version" related changes ( Let me know if you need help with git-fu for squashing etc. Once the above is in I will merge and publish this! |
Moved row insert out one layer to correct spot. pin bundler version to < 2 [skip ci] Travis: update LOGSTASH_BRANCH from 6.[0..4] to 6.5 update matrix to include current targets [ci skip] Update .travis.yml Catching up to the master on logstash-input-snmp Update snmp.rb Updating error message about needing a get, walk, or table. Update logstash-input-snmp.gemspec Bumping plugin version Update CHANGELOG.md Updating changelog Rebase Adding spec tests for tables
LGTM. Let's merge & publish! |
v1.1.0 published and available for install. |
Hi Everyone , great jobs table support work great ! Some one could provide a kv filter or split filter exemple to extract values of each SNMP index inside a document ? exemple of table input :
i have posted a questionfor helping everyone like me who have trouble to extract value: i will propose a PR to update document just after. 👍 |
Thanks for advocating for quality docs, @colinsurprenant. |
@colinsurprenant Here's the PR for table support and bumps the version to 1.0.2.
This doesn't include the support for a config option to split table results rather than users relying on the split filter.