Station log levels (spy:/logSetup)

As an alternative to using the station’s DebugService to tune station log output, you can use the station spy HTML interface for log setup. To access the station’s logSetup page in Workbench, double-click the running station in the Nav tree for its Station Summary view. From there, double-click Spy, then click logSetup.

Figure 6. Station spy logSetup (from Station Summary)

Spy logSetup lists station processes, each showing its current log level, and starts with a (new) DEFAULT level. The following are the updated properties:

Level selection columns are ordered left-to-right in increasing order of message volume.
The number of severity levels has increased: 9 in N4.
Thelog levels are persisted each time you click to set/clear a check box, saved in the host’s ~/logging/logging.properties file. There is no separate Save To File in N4.0.
The level given to the top DEFAULT row is global to any row with the far-right DEFAULT box set. See the next example figure.

The following figure shows the top of the spy logSetup page after the DEFAULT level has been changed from INFO to WARNING, and then the weather process set to the non-default level FINE.

Figure 7. Example spy logSetup for a station after a couple of changes

Callouts in the figure above show:

Last change made, reflected in this status line area (Changed weather log to level ‘FINE’.)
The DEFAULT log level, which in this case has been set to WARNING. Note this log level now applies to all rows where one of the 9 non-default levels (OFF to ALL) has not been set.
Increasing station output by assigning various log levels above INFO consumes extra station resources and may exact a performance penalty! After troubleshooting, always return log levels to default values.

You can also easily review, and if necessary, adjust log levels from the station’s