2 # Standage destinations for the message service --
3 # for use by messageService.fcl, which defines standard configurations for
6 # Normally, users will use messageService.fcl which includes this file,
7 # rather than dealing with this file directly.
9 # Usage - in a fcl configuration file
11 # 1 - Place the following near the start, among the PROLOGs:
12 # #include "fcl/standardMessageDestinations.fcl"
14 # 2 - In a destinations entry in a block that will be part of the message
15 # service block, choose the selected standard destination configuration
17 # destinations : @local::mf_error
18 # destinations : @local::mf_warning
19 # destinations : @local::mf_coutInfo
20 # destinations : @local::mf_debug
22 # 3 - If message statistics will also be desired, also insert the corresponding
23 # standard statistics, from among:
24 # destinations : @local::mf_errorStats
25 # destinations : @local::mf_warningStats
26 # destinations : @local::mf_coutInfoStats
27 # destinations : @local::mf_debugStats
29 # 3 - Customizations to configurations using these standard destinations
30 # are straightforward to make; see customizingMessageFacilityFcl.txt
31 # for simple examples.
36 # Four standardized (but customizable) destinations, with different thresholds
37 # ----------------------------------------------------------------------------
47 type: file # Record the messages in a file.
48 filename: "error.log" # Name of the file in which to place the messages;
49 # quoted, because if contains a dot.
50 threshold: ERROR # Threshold of what level of messages to react to.
51 append: true # Will append messages to named file if it exists
52 categories: # A place to list named categories, if you want to
53 # specify the behavior for specific categories of
55 # For example, in LigInfo("suspiciousParticle") << p;
56 # the category of the message would be
57 # "suspiciousParticle."
59 default: # Limits for any category not explicitly mentioned.
61 limit : 100 # Output first 100 instances of messages in each
62 # category, then go to exponential backoff.
63 timespan : 300 # If this many seconds elapse between messages of
64 # one category being issued, reset the counting
65 # toward the limit (in this case, output the next
66 # 100 instances, even if limit had been exceeded).
73 filename : @local::mf_error.filename # Because the filename matches that
74 # of a destination (if used with
75 # errorMsg), the statistics will be
76 # placed at the end of the output
77 # to that destination.
83 filename: "warning.log"
84 threshold: WARNING # React to WARNING and ERROR message severities;
85 # ignore messages issued via iLogInfo and LogDebug.
98 filename : @local::mf_warning.filename
103 type: cout # type could be cout, cerr, archive, dds, or file.
104 threshold: INFO # React to INFO, WARNING, and ERROR
105 # message severities; ignore LogDebug messages.
108 ArtReport: # ArtReport is a category of INFO messages that
109 # the framework will generate to tell, for example,
110 # when a next event is started.
112 reportEvery : 50 # Output only every 50-th message issued in this
114 limit : -1 # -1 is a way to say do not impose any limit.
115 # Alternatively, one could just omit the limit
116 # entry, which would mean no limit.
132 filename: "debug.log"
134 threshold: "DEBUG" # No messages will be ignored due to this threshold.
135 # However, unless debugModules in service.message
136 # includes "*", messages from a module which is
137 # not among the debug modules listed will still
150 filename : @local::mf_debug.filename