|
MessageFlags Enumeration
|
Various flags that can be attributed to a
LogMessage.
Namespace: GSF.DiagnosticsAssembly: GSF.Core (in GSF.Core.dll) Version: 2.4.205-beta+5ef4169f3b1079d8b163dd363614f656bd140924
Syntax GSF.Diagnostics.MessageFlags = function();
GSF.Diagnostics.MessageFlags.createEnum('GSF.Diagnostics.MessageFlags', true);
View SourceMembers Member name | Value | Description |
---|
None | 0 |
No flags are specified.
|
UsageIssue | 2 |
Indicates that a segment of code is not being used properly or ideally.
|
BugReport | 4 |
Indicates that a bug in the code exists somewhere. This is helpful when the programmer suspects that
certain exceptions were not properly handled.
|
PerformanceIssue | 8 |
A flag indicating that a performance related issue has occurred.
|
SecurityMessage | 16 |
Indicates this message has security implications with it. Such as
a successful/unsuccessful authentication.
|
SystemHealth | 32 |
These messages in generally should always be logged because they report the state of the current system's health. Normally this
will be when the system health is abnormal, for example, something abnormal is happening in the background that is important to
note and can assist debugging other components. Messages raised here would include First Chance Exceptions
and exceptions in log message routing (such as Message Suppression).
|
See Also