Difference between revisions of "Logging output"
Boxofstops (Talk | contribs) (→Log to screen) |
Boxofstops (Talk | contribs) (→Log to screen) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
The logging output in Box Of Stops is available for troubleshooting purposes. Day to day this can be safely ignored. | The logging output in Box Of Stops is available for troubleshooting purposes. Day to day this can be safely ignored. | ||
| − | If you are experiencing [[Latency]] problems, it may be helpful to look at the logging output, to see how much of the latency is Box Of Stops itself | + | If you are experiencing [[Latency]] problems, it may be helpful to look at the logging output, to see how much of the latency is Box Of Stops itself. Note the timings in the example output below. |
[[File:Latency-output.png]] | [[File:Latency-output.png]] | ||
| Line 9: | Line 9: | ||
After [[Starting]] Box Of Stops, you can see the live logging output directly on the screen. | After [[Starting]] Box Of Stops, you can see the live logging output directly on the screen. | ||
| − | Typically though, Box Of Stops will have automatically launched itself as a background process on the Raspberry Pi (see [[Auto start]]). In this case please look at the log file (see below), or | + | Typically though, Box Of Stops will have automatically launched itself as a background process on the Raspberry Pi (see [[Auto start]]). In this case please look at the log file (see below), or [[Starting|restart]] Box Of Stops to see the live logging output again. |
== Log to file == | == Log to file == | ||
| Line 16: | Line 16: | ||
All these files will be stored at <tt>~/boxofstops/logs</tt> (see [[Directories]] for more information). | All these files will be stored at <tt>~/boxofstops/logs</tt> (see [[Directories]] for more information). | ||
| + | |||
| + | == Logging level == | ||
| + | |||
| + | By default the level of logging you see is <tt>info</tt>. In fact this means all <tt>info</tt>, <tt>warn</tt> and <tt>error</tt> messages will show. | ||
| + | |||
| + | This level can be changed from [[Application properties]] - look for the <tt>logging.level</tt> property. Valid values are: | ||
| + | * debug | ||
| + | * info | ||
| + | * warn | ||
| + | * error | ||
| + | * off | ||
Latest revision as of 18:25, 14 January 2018
The logging output in Box Of Stops is available for troubleshooting purposes. Day to day this can be safely ignored.
If you are experiencing Latency problems, it may be helpful to look at the logging output, to see how much of the latency is Box Of Stops itself. Note the timings in the example output below.
Log to screen
After Starting Box Of Stops, you can see the live logging output directly on the screen.
Typically though, Box Of Stops will have automatically launched itself as a background process on the Raspberry Pi (see Auto start). In this case please look at the log file (see below), or restart Box Of Stops to see the live logging output again.
Log to file
By default, Box Of Stops keeps 3 days of log files. Today's log file is stored as plain text, the older files are zip files.
All these files will be stored at ~/boxofstops/logs (see Directories for more information).
Logging level
By default the level of logging you see is info. In fact this means all info, warn and error messages will show.
This level can be changed from Application properties - look for the logging.level property. Valid values are:
- debug
- info
- warn
- error
- off
