[This is preliminary documentation and is subject to change.]
Stipulates general logging message types like: Info/Warning/Error etc...
Namespace: NFX.LogAssembly: NFX (in NFX.dll) Version: 3.0.0.1 (3.0.0.1)
Syntax
Members
| Member name | Value | Description | |
|---|---|---|---|
| Debug | 0 | Used in debugging temp code | |
| DebugA | 1 | ||
| DebugB | 2 | ||
| DebugC | 3 | ||
| DebugD | 4 | ||
| DebugSQL | 5 | Emitted by DataStore implementations | |
| DebugGlue | 6 | Emitted by Glue/Net code | |
| DebugZ | 7 | Last debug-related message type for use in debug-related max-level config setting | |
| Trace | 50 | Tracing, no danger to system operation | |
| TraceA | 51 | ||
| TraceB | 52 | ||
| TraceC | 53 | ||
| TraceD | 54 | ||
| TraceSQL | 55 | Emitted by DataStore implementations | |
| TraceGlue | 56 | Emitted by Glue/Net code | |
| TraceErl | 57 | Emitted by Erlang code | |
| TraceZ | 58 | Last trace-related message type for use in trace-related max-level config setting | |
| PerformanceInstrumentation | 90 | Performance/Instrumentation-related message | |
| Info | 100 | Informational message, no danger to system operation | |
| InfoA | 101 | ||
| InfoB | 102 | ||
| InfoC | 103 | ||
| InfoD | 104 | ||
| InfoZ | 105 | Last info-related message type for use in info-related max-level config setting | |
| SecurityAudit | 200 | Permission audit, usualy a result of client user action, no danger to system operation | |
| Notice | 300 | SYSLOG.Notice Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required. | |
| Warning | 400 | Caution - inspect and take action. SYSLOG.Warning, not an error, but indication that an error will occur if action is not taken, e.g. file system 85% full - each item must be resolved within a given time. | |
| Error | 500 | Recoverable error, system will most-likely continue working normally. SYSLOG.Error Non-urgent failures, these should be relayed to developers or admins; each item must be resolved within a given time. | |
| Critical | 600 | SYSLOG.Critical Should be corrected immediately, but indicates failure in a primary system, an example is a loss of a backup ISP connection. | |
| CriticalAlert | 700 | SYSLOG.Alert Should be corrected immediately, therefore notify staff who can fix the problem. An example would be the loss of a primary ISP connection. | |
| Emergency | 1000 | Unrecoverable error, system will most-likely experience major operation disruption. SYSLOG.Emergency - A "panic" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call. | |
| CatastrophicError | 2000 | Unrecoverable error, system will experience major operation disruption. SYSLOG.Emergency - A "panic" condition usually affecting multiple apps/servers/sites. At this level it would usually notify all tech staff on call. |
See Also