You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/configure.rst
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -192,9 +192,10 @@ You can view logger's log level as a general cut off.
192
192
For example, if we have set it to ``warning``, no debug or informational messages would ever be printed.
193
193
194
194
Finally, there is a special set of handlers for handling performance log messages.
195
-
These are stored in the ``handlers_perflog`` property.
196
-
The performance handler in this example will create a file per test and per system/partition combination and will append the performance data to it every time the test is run.
197
-
Notice in the ``format`` property how the message to be logged is structured such that it can be easily parsed from post processing tools.
195
+
Performance log messages are generated *only* for `performance tests <tutorial_basics.html#writing-a-performance-test>`__, i.e., tests defining the :attr:`perf_patterns <reframe.core.pipeline.RegressionTest.perf_patterns>` attribute.
196
+
The performance log handlers are stored in the ``handlers_perflog`` property.
197
+
The ``filelog`` handler used in this example will create a file per test and per system/partition combination (``./<system>/<partition>/<testname>.log``) and will append to it the obtained performance data every time a performance test is run.
198
+
Notice how the message to be logged is structured in the ``format`` property, such that it can be easily parsed from post processing tools.
198
199
Apart from file logging, ReFrame offers more advanced performance logging capabilities through Syslog and Graylog.
0 commit comments