Page Comparison

Wrangler provides the io.picolabs.logging ruleset which when installed on a pico allows the user to browse past episodes that have occurred on the pico. An episode is what occurs as a result of a pico receiving an event or query. Raised events that follow from an initial received event are contained within one episode. The logging ruleset and logging tab in the UI can be useful because it contains the same information as piped to the console without concatenation, which is incredibly useful for debugging.

If not installed, simply click "install" to get the logged information:

...

The logging tab of the pico UI with io.picolabs.logging installed displays the episode in its entirety, without concatenation:

...

This tab allows you to see detailed logging information concerning events and queries sent to the pico within the last twelve hours.

...

What you are looking at is the latest transactions performed by the pico, with a timestamp (using Zulu or GMT time, to the millisecond), whether the transaction was an event or a query. Finally, for queries you are shown the RID of the ruleset, a slash, the name of the function called, and any arguments shown in a map. For events you are shown the domain, a colon, the name or type of the event, and any attributes shown as a map.

These transactions are ordered most recent first.

Checking the box opens up more detail, with the various things that happened shown in chronological order.

...

You will always see first when the transaction was queued, and when it started. At the bottom, you will see the time when it was completed (which will sometimes be with an error).

For an event, you will see the events that were raised, starting with the one that initiated the event transaction. In this case, they are:

1. engine_ui:new

2. wrangler:new_child_request

3. wrangler:new_child_created

Under each event, you will see which rule or rules were selected, and whether or not the rules fired.

...