You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/get-started/sumo-logic-ui.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ Use the **Go To...** menu for quick access to settings and features. <img src={u
89
89
90
90
With the Sumo Logic Administrator role, you can manage your organization's data collection settings, ingest budget, partitions, and more. To access these settings, go to the top nav bar and click the **Configuration** icon.<br/><img src={useBaseUrl('img/get-started/config.png')} alt="config.png" width="300"/>
Health events allow you to keep track of the health of your Collectors, Sources, and Ingest Budgets. You can use them to find and investigate common errors and warnings that are known to cause collection issues.
14
+
System events allow you to keep track of the health of your Collectors, Sources, and Ingest Budgets. You can use them to find and investigate common errors and warnings that are known to cause collection issues.
15
15
16
16
This framework includes the following:
17
17
18
-
*Health event logs indexed in the [System Event Index](/docs/manage/security/audit-indexes/system-event-index).
19
-
* A [health events table](#health-events-table) on the Alerts page.
20
-
* A health status column on the [Collection page](#collection-page).
18
+
*Account event logs indexed in the [Account Event Index](/docs/manage/security/audit-indexes/account-event-index).
19
+
* A [account events table](#account-events-table) on the Alerts page.
20
+
* A account status column on the [Collection page](#collection-page).
21
21
22
-
Health events are sent from Installed Collectors on version 19.308-2 and
23
-
later.
22
+
Account events are sent from Installed Collectors on version 19.308-2 and later.
24
23
25
24
## Alerts
26
25
27
-
Alerts for specific health events are easy to create in the Health Events Table. The details pane of an event provides a **Create Scheduled Search** button to automatically generate the required query.
26
+
Alerts for specific account events are easy to create in the Account Events Table. The details pane of an event provides a **Create Scheduled Search** button to automatically generate the required query.
28
27
29
-
## Health events
28
+
## Account events
30
29
31
-
Health events are created when an issue is detected with a Collector or Source. Events are indexed and searchable in a separate partition named **sumologic_system_events** in the [System Event Index](/docs/manage/security/audit-indexes/system-event-index). For details on what information is available in a health event, see the [common parameters](#common-parameters) table.
30
+
Account events are created when an issue is detected with a Collector or Source. Events are indexed and searchable in a separate partition named **sumologic_system_events** in the [Account Event Index](/docs/manage/security/audit-indexes/account-event-index). For details on what information is available in a health event, see the [common parameters](#common-parameters) table.
32
31
33
-
### Health events table
32
+
### Account events table
34
33
35
-
The health events table allows you to easily view and investigate problems getting your data to Sumo.
34
+
The account events table allows you to easily view and investigate problems getting your data to Sumo.
36
35
37
-
On the health events table, you can search, filter, and sort incidents by key aspects like severity, resource name, event name, resource type, and opened since date.
36
+
On the account events table, you can search, filter, and sort incidents by key aspects like severity, resource name, event name, resource type, and opened since date.
38
37
39
-
[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access the health events table, in the main Sumo Logic menu select **Manage Data > Monitoring > Health Events**.
38
+
[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access the account events table, in the main Sumo Logic menu select **Manage Data > Monitoring > Health Events**.
40
39
41
-
[**New UI**](/docs/get-started/sumo-logic-ui/). To access the health events table, in the top menu select **Configuration**, and then under **Data Collection** select **Health Events**. You can also click the **Go To...** menu at the top of the screen and select **Health Events**.
40
+
[**New UI**](/docs/get-started/sumo-logic-ui/). To access the account events table, in the top menu select **Configuration**, and then under **Data Collection** select **Account Events**. You can also click the **Go To...** menu at the top of the screen and select **Account Events**.
Click the **Create Scheduled Search** button on the details pane to get alerts for specific health events. The unique identifier of the resource, such as the Source or Collector, is used in the query. See [Schedule a Search](../alerts/scheduled-searches/schedule-search.md) for details.
49
+
Click the **Create Scheduled Search** button on the details pane to get alerts for specific account events. The unique identifier of the resource, such as the Source or Collector, is used in the query. See [Schedule a Search](../alerts/scheduled-searches/schedule-search.md) for details.
51
50
52
51
Under the **More Actions** menu you can select:
53
52
54
53
***Event History** to run a search against the **sumologic_system_events** partition to view all of the related event logs.
55
54
***View Object** to view the Collector or Source in the Collection page related to the event.
56
55
57
-
### Health events severity
56
+
### Account events severity
58
57
59
58
Events are categorized by two severity levels, warning and error. The severity column has color-coded error and warning events so you can quickly determine the severity of a given issue.
60
59
@@ -71,7 +70,7 @@ common parameters in the order that they are found in health event logs.
71
70
|:--|:--|:--|
72
71
| status | Either `Healthy` or `Unhealthy` based on the event. | String |
73
72
| details | The details of the event include the type as `trackerId`, the `name` of the event, and a `description`. | JSON object of Strings |
74
-
| eventType |Health events have a value of `Health-Change`. | String |
73
+
| eventType |Account events have a value of `Health-Change`. | String |
75
74
| severityLevel | Either `Error` or `Warning` based on the event. | String |
76
75
| accountId | The unique identifier of the organization. | String |
77
76
| eventId | The unique identifier of the event. | String |
@@ -110,22 +109,22 @@ common parameters in the order that they are found in health event logs.
110
109
}
111
110
```
112
111
113
-
## Search health events
112
+
## Search Account events
114
113
115
-
To search all health events run a query against the internal partition
114
+
To search all account events run a query against the internal partition
116
115
named **sumologic_system_events**. For example,
117
116
118
117
```sql
119
118
_index=sumologic_system_events "Health-Change"
120
119
```
121
120
122
121
:::tip
123
-
Create a scheduled search to get alerts for specific health events.
122
+
Create a scheduled search to get alerts for specific account events.
124
123
:::
125
124
126
125
### Metadata assignment
127
126
128
-
Creating a query that defines built-in metadata field values in the scope can help improve search performance and limit results to what you're investigating. [Metadata](../search/get-started-with-search/search-basics/built-in-metadata.md) fields are assigned to health event logs as follows:
127
+
Creating a query that defines built-in metadata field values in the scope can help improve search performance and limit results to what you're investigating. [Metadata](../search/get-started-with-search/search-basics/built-in-metadata.md) fields are assigned to account event logs as follows:
129
128
130
129
|**Metadata Field**|**Assignment Description**|
131
130
|:--|:--|
@@ -139,9 +138,9 @@ A **Health** column on the Collection page shows color-coded healthy, error, a
139
138
140
139
The **status** column now shows the status of Sources manually paused by users.
141
140
142
-
Health events allow you to keep track of the health of your Collectors, Sources, and Ingest Budgets. You can use them to find and investigate common errors and warnings that are known to cause collection issues. See [Health events](/docs/manage/health-events.md) for details.
262
+
Account events allow you to keep track of the health of your Collectors, Sources, and Ingest Budgets. You can use them to find and investigate common errors and warnings that are known to cause collection issues. See [Account events](/docs/manage/account-events.md) for details.
263
263
264
-
Ingest budgets that have exceeded their capacity are placed in an **Error** health state. The following are two common queries used to investigate the health of ingest budgets.
264
+
Ingest budgets that have exceeded their capacity are placed in an **Error** account state. The following are two common queries used to investigate the health of ingest budgets.
265
265
266
266
A query to search for all ingest budgets that are over capacity.
0 commit comments