Gemstone Diagnostics Library
Message
Various flags that can be attributed to a LogMessage.
Definition
Namespace: Gemstone.Diagnostics
Assembly: Gemstone.Diagnostics (in Gemstone.Diagnostics.dll) Version: 1.0.187 -- Release Build+1f3ed8b6221c2b087349bd4a0f5f67d184969372
Assembly: Gemstone.Diagnostics (in Gemstone.Diagnostics.dll) Version: 1.0.187 -- Release Build+1f3ed8b6221c2b087349bd4a0f5f67d184969372
C#
[FlagsAttribute]
public enum MessageFlagsVB
<FlagsAttribute>
Public Enumeration MessageFlagsC++
[FlagsAttribute]
public enum class MessageFlagsJavaScript
Gemstone.Diagnostics.MessageFlags = function();
Gemstone.Diagnostics.MessageFlags.createEnum('Gemstone.Diagnostics.MessageFlags', true);Members
| 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 issue 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). |