Skip to content

Commit 44c7047

Browse files
committed
better example of user-defined status lines
1 parent 60f2b70 commit 44c7047

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

README.rst

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -108,10 +108,12 @@ To do this create a .json configuration file containing a "userStatusLines" dici
108108
}
109109

110110

111-
Any user-defined status lines should be of the same form as the Correlator status lines, logged at INFO level similar
112-
to::
111+
Any user-defined status lines should be of the same form as the Correlator status lines, logged at INFO level,
112+
for example::
113113

114-
Some prefix: key1=value1 key2=value2 key3="value 3"
114+
on all wait(5.0) {
115+
log "MyApplication status: kpi1="+kpi1.toString()+" kpi2="+kpi2.toString()+" string_kpi=\""+kpi3+"\"" at INFO;
116+
}
115117

116118
Technical detail: the frequency and timing of other status lines may not match when the main "Correlator status:" lines
117119
are logged. The analyzer just uses the main status lines for the timing, adding the most recently seen user status

0 commit comments

Comments
 (0)