Application Management
Causes of unparsed messages in Loggly
This article helps to identify the causes as to why your expected message format in Loggly is unparsed.
First published date
8/12/2021 6:13 PM
Last published date
8/19/2021 6:26 PM
Overview
Unparsed messages are unformatted key values that cannot identify the value in an input field. If the log message is unparsed, the messages will not be indexed in key-value field format.
Product section
Loggly
Cause
You will receive these errors due to the following causes:
1. You received a Max Field notification if you already exceeded the field limit.
2. You encountered Mapping Conflict notifications if the fields on the events are not indexed or parsed.
3. You may be using an unsupported log format type.
1. You received a Max Field notification if you already exceeded the field limit.
2. You encountered Mapping Conflict notifications if the fields on the events are not indexed or parsed.
3. You may be using an unsupported log format type.
Resolution
These are the approaches on how to check and fix unparse messages
1. Max Field Limit
2. Mapping Conflict
3. Automated Parsing Log Types
1. Max Field Limit
2. Mapping Conflict
3. Automated Parsing Log Types