Skip to content

Commit 197f985

Browse files
Merge pull request #3100 from MicrosoftDocs/main
Auto Publish – main to live - 2025-09-05 22:20 UTC
2 parents 905baed + 80db366 commit 197f985

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

desktop-src/EventLog/event-types.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -17,12 +17,12 @@ The application indicates the event type when it reports an event. Each event mu
1717

1818
The following table describes the five event types used in event logging.
1919

20-
21-
| Event type | Description |
22-
|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
23-
| **Error** | An event that indicates a significant problem such as loss of data or loss of functionality. For example, if a service fails to load during startup, an Error event is logged. |
24-
| **Warning** | An event that is not necessarily significant, but may indicate a possible future problem. For example, when disk space is low, a Warning event is logged. If an application can recover from an event without loss of functionality or data, it can generally classify the event as a Warning event. |
20+
| Event type | Description |
21+
| ---------- | ----------- |
22+
| **Error** | An event that indicates a significant problem such as loss of data or loss of functionality. For example, if a service fails to load during startup, an Error event is logged. |
23+
| **Warning** | An event that is not necessarily significant, but may indicate a possible future problem. For example, when disk space is low, a Warning event is logged. If an application can recover from an event without loss of functionality or data, it can generally classify the event as a Warning event. |
2524
| **Information** | An event that describes the successful operation of an application, driver, or service. For example, when a network driver loads successfully, it may be appropriate to log an Information event. Note that it is generally inappropriate for a desktop application to log an event each time it starts. |
26-
| **Success Audit** | An event that records an audited security access attempt that is successful. For example, a user's successful attempt to log on to the system is logged as a Success Audit event. |
27-
| **Failure Audit** | An event that records an audited security access attempt that fails. For example, if a user tries to access a network drive and fails, the attempt is logged as a Failure Audit event. |
25+
| **Success Audit** | An event that records an audited security access attempt that is successful. For example, a user's successful attempt to log on to the system is logged as a Success Audit event. |
26+
| **Failure Audit** | An event that records an audited security access attempt that fails. For example, if a user tries to access a network drive and fails, the attempt is logged as a Failure Audit event. |
27+
2828
Selected activities of users can be tracked by auditing security events and then placing entries in a computer's security log.

0 commit comments

Comments
 (0)