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

Parsing Errors - Number Format Exception - For Specific Level and Message Content #6

Open
technophile88 opened this issue Feb 19, 2018 · 1 comment

Comments

@technophile88
Copy link

While using this Content Pack for Cisco Catalyst Switches, I am getting Indexer failures due to parsing error for a specific severity level (6) and the IPACCESSLOGNP / IPACCESSLOGP messages while all the other messages are being parsed successfully. The typical error messages for indexer failures are:

{"type":"mapper_parsing_exception","reason":"failed to parse [level]","caused_by":{"type":"number_format_exception","reason":"For input string: "190>: HOSTNAME1: %SEC-6-IPACCESSLOGNP: list 1 permitted 0 172.16.16.16 -""}}

{"type":"mapper_parsing_exception","reason":"failed to parse [level]","caused_by":{"type":"number_format_exception","reason":"For input string: "190>: HOSTNAME2: %SEC-6-IPACCESSLOGP: list vlan10_XYZ denied udp 169.254.63.64(137) -""}}

{"type":"mapper_parsing_exception","reason":"failed to parse [level]","caused_by":{"type":"number_format_exception","reason":"For input string: "46>: HOSTNAME: %SEC-6-IPACCESSLOGNP: list 1 permitted 0 172.16.64.128 -""}}

There aren't any other type of indexer failures and errors. What modifications are required to remove these errors?

Thanks,

@diegocanton
Copy link
Contributor

Two contributions regarding processing problems were performed, but were pending signature of CLA. Try a project fork and make the suggested changes, see if that solves your problem.

https://github.com/graylog-labs/graylog-contentpack-cisco-catalyst/pull/2/files
https://github.com/graylog-labs/graylog-contentpack-cisco-catalyst/pull/4/files

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

2 participants