| Logdoc index | Logdoc entry list | Log entry group | Log entry |
| Name | Category | Entries |
|---|---|---|
| Servlet | org.xins.server.servlet | 3 |
| Internal lifespan-related | org.xins.server.lifespan | 2 |
| Bootstrapping | org.xins.server.lifespan.bootstrap | 42 |
| Logging subsystem | org.xins.server.log | 12 |
| Initialization | org.xins.server.lifespan.init | 42 |
| Runtime | org.xins.server.runtime | 18 |
| HTTP-level | org.xins.server.runtime.http | 3 |
| Transaction logging | org.xins.server.runtime.tx | 2 |
| Access rule matching | org.xins.server.runtime.acl | 3 |
| Calling Convention | org.xins.server.runtime.cc | 2 |
| Diagnostic Context Identifiers | org.xins.server.runtime.context | 3 |
| Shutdown | org.xins.server.lifespan.shutdown | 8 |
| Front-end calling convention | org.xins.server.cc.frontend | 6 |
The following translation bundles are available:
The following log levels can be used:
| ID | Description |
|---|---|
| DEBUG | Debugging messages. Only useful for programmers. This is the only level that may contain implementation details that are not exposed outside individual functions. |
| INFO | Informational messages. Typically not important to operational people, except in cases where a problem is being traced or if behaviour is investigated. |
| NOTICE | Informational messages that should typically be noticed by operational people. |
| WARNING | Warning messages. Should be noticed, but typically require no immediate action, although they may indicate a problem that should be fixed. |
| ERROR | Error messages. Indicates an error that should be fixed. However, it does not keep the whole application from functioning. |
| FATAL | Fatal error messages. Indicates an error that keeps the whole application from functioning. |
Note that it is a fatal condition to start with an unexpected condition of any crucial aspect of the application. If the configuration of all crucial aspects of the application could not be correctly and fully processed it is effectively in an unexpected state. Falling back to defaults does not imply returning to an expected condition because clearly some specific configuration was intended and expected.
This rule should be applied to determine whether a message should be logged at the FATAL level or not.