Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tables

The table must be one of the following:

  • my.app → tables created by sending data from a new, proprietary data source.

  • my.upload → tables created by manually uploading a file containing data.

Info

Unless…

  • They have less than 4 tag levels, which makes them ineligible for the use of the autoparser.

  • They have been created by injecting data from another table, which are already properly parsed.

Events

Events must comply with the following conditions:

  • Events must contain the same number of fields in the same order.

  • Events must use delimiters in the same pattern in every event.

  • Events must use valid formats.

  • Timestamp data will be parsed as a string when presenting an invalid format. Check valid formats below:

    • ddd MMM DD HH:mm:ss YYYY → Thu Mar 29 00:21:05 2012

    • DD-MMM-YYYY HH:mm:ss.SSS → 27-Aug-2012 09:44:09.378

    • DD/MM/YYYY HH:mm:ss → 23/07/2019 07:55:00

    • DD/MM/YYYY H:mm:ss → 14/09/2012 9:42:05

    • YYYY-MM-DD HH:mm:ss.SSS → 2000-12-17 01:01:01.123

    • YYYY/MM/DD HH:mm:ss → 2012/08/25 06:48:18

    • YYYY/MM/DD → 2012/08/25

    • yyyy-MM-dd:hh:mm:ss+gmt → 2012-08-16:10:29:17+0200

    • yyyy-MM-dd hh:mm:ss.micros → 2000-12-17 01:01:01.123456

    • Epoch.millis (recognized as a float, you need to change it) → 1234567890.123

    • Millis (recognized as an integer, you need to change it) → 1584100816544

Info

Disparate data

If the events do not conform to these requirements, it may be imposible impossible to extract a pattern and an error will pop up to further specify the reason. You can then parse it informing you that your data has been parsed with errors. This means that some fields could not be parsed properly and you will see null values wherever the error occurred.

To avoid this, you can parse this data manually using operations such as Split (split) and later create a custom table. For my.app data, you can also contact customer support to request a custom parser.

...

  • View level of the Finders permission. This permission is required to access a search, which is necessary to use the autoparser.

  • The Log autoparser permission. This permission is required to enable the option in the toolbar menu of the search window.

...

Using the

...

Rw step

Inside the table that you want to parse, click the option menu in the toolbar and select Source table → Autoparse.

Info

Autoparse option not showing

The option will not appear if the requirements explained above are not met.

...

Rw step

The Autoparser window opens so you can select the desired settings to transform the raw data contained in the message field into a fully classified table.

...

Rw step

If you want a different set of samples, click the Reload samples button next to the No. of Samples dropdown (see icon below).

This will lead to two possible scenarios depending on the temporal aspects of your query:

  • Fixed period query: new events are not being received so you will get a message informing you that "no new events were found" and thus changing the samples is not possible.

  • Real-time query: new events are being received so this will load the last 200. If the structure changes, new delimiters will be considered. If the structure is too different, you will get the "Disparate Data" error message explained before.

Rw step

Select or deselect the symbols identified as possible field delimiters by clicking in the Delimiters area or one by one in the Sample area. The symbols are displayed in colors to show if they are going to be used when parsing.

...

Color

...

Meaning

...

All the symbols in the sample are going to be used.

...

None of the symbols in the sample are going to be used.

...

Some of the symbols in the sample are going to be used. A number is displayed below to specify how many of them.

Rw step

Assign names and select the required data type for each field using the dropdown menu.

Info

Autocomplete field names

You can enter the command /fillNames in any of the name fields to autocomplete all the available fields with standard names (column1, column2…)

Rw step

Mark the Exclude checkbox for any fields you do not want to include in the parsed table. When you do so, the corresponding name field will be automatically disabled.

Rw step

Click Confirm.

Info

The process of parsing will not create a new table but transform the original table instead so it can be fully used in Devo.

Autoparsing an already parsed table

If you are not happy with the result for whatever reason, you can use the Autoparser again. However, it is not possible to apply changes selectively; the table will be reset to its original unparsed state for you to start over.

You just need to open the Autoparser as instructed before. Don't worry if you have second thoughts after clicking because you will receive a warning message. You can either cancel and keep the table as it is or restore it to parse it again with different settings.

If you choose to restore it, you will be forced out while the table goes back to its original unparsed state. To parse it anew, you need to access it again through the Data Search and open the Autoparser once more.

Autoparsing special objects

...

autoparser

Child pages (Children Display)
depth1
allChildrentrue
style
sortAndReverse
first0