Skip to content

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

@technophile88

Description

@technophile88

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,

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions