You can parse your logs using our Data Parsing Wizard. To use this feature, hover your mouse over the Log Shipping tab and click on Data Parsing from dropdown menu.
Note: Our Data Parsing is currently in BETA.
Before we go into details on how to use the Data Parsing feature, keep in mind that we offer Parsing as a Service to all of our users. Simply send us a request and we will handle all of your parsing needs. For more details visit this page: Parsing Request
In order for the Data Parsing Wizard to work, you should first send custom logs to your Logz.io account. Once that has been done, let's start parsing our logs:
- Setup - Start by choosing your Data Source from the dropdown menu, then click Next
- Parse - This step is where you define how you want your log to be broken up and parsed
- After entering your Pattern Name
- Click on Select to choose some Sample Log Line
- From there, select up to five sample logs out of the last five hundred that have been shipped to Logz.io to create your parsing
- Click on Select
- You will then be able to choose your Parse Method from the dropdown. As previously mentioned, Grok is supported with Delimiter, JSON and Key Value parsing will be introduced soon.
- Start entering your Grok Pattern
Note: We recommend using both the Grok Debugger and this list of grok patterns as reference.
- Extra Pointer:
- As soon as you begin grokking, your log lines will begin to be parsed into separate fields in the Parse Results table below. The colors help you to match the fields in the log lines with your parsing results. Make sure you see the name you chose for the fields in the log.
- To omit data, simply do not name the fields.
- Using “message” as the field name overrides the existing message field in the log, and you can use it as many times as you want — the values for this field will be concatenated into a comma-separated message field. If you do not use this field name in the grok pattern, the default message field will be used.
- After entering your grok pattern, you can define a field type for each field that you parse.
- While we recommend leaving this default setting (“Automatic”), you have the option to define other types such as boolean, date, IP, and byte. For geo-enrichment for example, you will need to select the “Geo-Enrichment” field type.
- Enrich - You can apply some advanced parsing customizations
- If you selected to parse one of the IP fields as a Geo IP field in the previous step, you will now be able to decide with which geo fields to enrich the field.
- Under “Set Timestamp,” you will be able to configure all the timestamp fields that appear within your logs. For example, you can set which timestamp is the leading timestamp (a leading timestamp determines the sequential order in which the logs are displayed).
- Validate - It’s now time to make sure that you are happy with the parsing results
Some points that are worth highlighting:
- Data Parsing feature can only be used on log types that do not have pre-defined parsing. If you would like to apply changes to those logs anyway, contact email@example.com.
- Again, Grok is the only supported parsing method. Delimiter, JSON, and Key Value parsing will be introduced soon.
- Our system will also monitor and automatically identify parsing that isn't efficient, notifies our Support team, who will reach out to assist you making your parsing better for you and our system.
- Why do the heavy lifting? We can do it for you - Parsing Request