
milliseconds of each other then they probably have a causal relationship. Also, if there is a time-out in the software somewhere,
that time-out may often be found by looking at this timestamp.
Next is the log level. In this case, it is “INFO”, which is standard. It can also be “WARN” for more serious happenings in the
SLEE, or “DEBUG” if debug messages are enabled. Section 10.1.2 in Chapter 10 has much more information about the log
levels available and how to set them.
Next is the logger key – in this case, [rhino.alarm.manager]. Every log message has a key, and this shows what part of Rhino
this log message came from. Verbosity of each logger key can be controlled, as discussed in Section 10.1.1 of Chapter 10.
Then, the thread which outputted this message is displayed – in this case, <Thread-4>.
Finally, the rest of the message is the actual log message. In this case, it is an Alarm message which is being outputted.
Open Cloud Rhino 1.4.3 Administration Manual v1.1 25
Commentaires sur ces manuels