Situation information
The situation information is used to classify the condition that is reported by an event into a common set of situations.
The Common Base Event specification [CBE101] provides information on the set of situations defined for the Common Base Event, with the values and formats used to describe these situations. The Common Base Event Developer’s Guide [CBEBASE] provides general usage guidelines.
Consider the following points regarding situation information for problem determination events:
- Whenever possible, use the situation categorizations and qualifiers described in the base Common Base Event specification. Avoid using our own situation definitions as much as possible.
- Not all messages and logs can be classified using the situation definitions that are supplied in the base Common Base Event specification. We can use the OtherSituation categorization to provide our own situation information, but the recommended course of action for problem determination events is to use the ReportSituation categorization, with reportCategory=Log.
- Warning events can be confusing. A warning event (that is an event with severity=warning) typically indicates a recoverable failure, but the situation settings can be interpreted as unrecoverable failures (for example ConnectSituation, successDisposition=UNSUCCESSFUL). Use the appropriate situation categorization so the severity setting indicates the severity of the situation, that is whether the component recovered from the failure.
- The recommended setting for the reasoningScope value is EXTERNAL for all message events.
Related concepts
The Common Base Event in WebSphere Application Server
Related tasks
Add logging and tracing to the application
Common Base Event structure