The information in the following table shows the correlation between the Orchestration Server logging levels and those you are likely to see in Novell Sentinel.
Table 1-3 Orchestration Server Log Levels Mapped to Sentinel Log Levels
|
Orchestration Server Log Level (alpha) |
Sentinel Collector Log Level (numeric) |
Comments |
Usage Examples |
|---|---|---|---|
|
EMERGENCY |
5 |
Urgent conditions that require immediate attention. Indicates that the system is no longer functioning. |
|
|
ALERT |
5 |
Conditions that should be corrected immediately. |
|
|
CRITICAL |
5 |
Critical conditions. |
|
|
ERROR |
4 |
Errors that have been correctly handled. |
Unsuccessful job runs and provisioner/VM actions that have been correctly handled but might require manual attention. |
|
WARNING |
3 |
Warning messages. |
Unexpected but recoverable events indicating degraded operational status, fsuch as grid objects becoming unhealthy. |
|
NOTICE |
2 |
Conditions that are not error conditions, but should possibly be handled specially. |
Events expected occasionally as part of usual business operations, such as password changes, failed authentications and authorizations, grid objects returning to good health, server shutdown. |
|
STATUS |
1 |
Conditions that report on changes in operational conditions. |
Events expected frequently as part of usual business operations, such as successful authentications (logins and logouts), deletion of grid objects, changes in group membership, deployment of jobs/policies/schedules/triggers, policy association. |
|
INFO |
1 |
Informational messages. |
Non-security-sensitive events expected very frequently as part of usual business operations, such as successful job runs and provisioner/VM actions, resources going online/offline, session expiration/timeout. |