Changes between Version 23 and Version 24 of LogViewerPlugin


Ignore:
Timestamp:
Aug 24, 2018, 7:10:22 AM (6 years ago)
Author:
figaro
Comment:

Moved example to functional description

Legend:

Unmodified
Added
Removed
Modified
  • LogViewerPlugin

    v23 v24  
    88
    99Be careful with large log files: use the tail-function to limit the output to the last few lines, because it would otherwise take a long time to display.
     10
     11You find the ''Log Viewer'' on the ''Admin'' page in the ''General'' section (see [#Example below]). Having this page called, select the log level you wish to see the entries for, using the drop-down. Optionally, you may chose to display all "higher priority" as well, where "higher" means the entries on top of the one you selected.
     12
     13You now can further restrict the amount of lines displayed: the ''Tail'' input works similar to the `tail -f` shell command, only showing the last N lines. If you input nothing here, this restriction is skipped, but if you do, the following search will be limited to these lines. In the ''Search'' input box you can enter a term which must be found in a line to be displayed. You can also use regular expressions here, in which case you must check the corresponding button. If you additionally check the "not" button, that search will be inverted, ie only lines ''not'' containing/matching your search term will be shown.
     14
     15Hovering your mouse over the input areas shows a tooltip with the meanings.
     16
     17Once you made your selections, push the button and the matching lines from the `trac.log` will be displayed.
     18
     19Here is what it may look like, having selected "Info and above":
     20
     21[[Image(logviewer.jpg, border=2)]]
     22
     23As you can see, the log lines are quite colorful: each log level has its distinct color assigned. If you like to change the choice of colors here, you can easily apply your own style sheets. All elements can be identified without problems: the different log levels use classes, and even the other elements of the GUI use classes and ids. Furthermore, in this example you might note that obviously nothing was logged at "Info" level.
    1024
    1125== Bugs/Feature Requests
     
    8094The meaning of those three settings corresponds to the similarly named items from the autoload, with the difference that the values here only apply when autoload is disabled.
    8195
    82 == Usage
     96== Feedback
    8397
    84 You find the ''Log Viewer'' on the ''Admin'' page in the ''General'' section (see [#Example below]). Having this page called, select the log level you wish to see the entries for, using the drop-down. Optionally, you may chose to display all "higher priority" as well, where "higher" means the entries on top of the one you selected.
    85 
    86 You now can further restrict the amount of lines displayed: the ''Tail'' input works similar to the `tail -f` shell command, only showing the last N lines. If you input nothing here, this restriction is skipped, but if you do, the following search will be limited to these lines. In the ''Search'' input box you can enter a term which must be found in a line to be displayed. You can also use regular expressions here, in which case you must check the corresponding button. If you additionally check the "not" button, that search will be inverted, ie only lines ''not'' containing/matching your search term will be shown.
    87 
    88 Hovering your mouse over the input areas shows a tooltip with the meanings.
    89 
    90 Once you made your selections, push the button and the matching lines from the `trac.log` will be displayed.
    91 
    92 == Example
    93 
    94 Here is what it may look like, having selected "Info and above":
    95 
    96 [[Image(logviewer.jpg)]]
    97 
    98 As you can see, the log lines are quite colorful: each log level has its distinct color assigned. If you like to change the choice of colors here, you can easily apply your own style sheets. All elements can be identified without problems: the different log levels use classes, and even the other elements of the GUI use classes and ids. Furthermore, in this example you might note that obviously nothing was logged at "Info" level.
    99 
    100 == User Comments
    101 
    102  * Your feedback here, please. Or if you don't want to write something, use the poll below (you must be logged in to vote):
     98Your feedback here, please. Or if you don't want to write something, use the poll below (you must be logged in to vote):
    10399  * olemis: This plugin is cool and very useful (especially to manage remote Trac instances ''';o)'''.
    104100   Nonetheless, if you are debugging then you might like to try TracDeveloperPlugin too.