MessageFlags Enumeration

Various flags that can be attributed to a LogMessage.

Namespace: GSF.Diagnostics
Assembly: GSF.Core (in GSF.Core.dll) Version: 2.4.258-beta+f8b6aa3dbfe0b4cc2b0b0760dd5d2a3dd4f59d09

Syntax

[FlagsAttribute]
public enum MessageFlags

<FlagsAttribute>
Public Enumeration MessageFlags

[FlagsAttribute]
public enum class MessageFlags

[<FlagsAttribute>]
type MessageFlags

GSF.Diagnostics.MessageFlags = function();
GSF.Diagnostics.MessageFlags.createEnum('GSF.Diagnostics.MessageFlags', true);

Members

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).