Health events allow you to keep track of the health of your Collectors and Sources. You can use them to find and investigate common errors and warnings that are known to cause collection issues.
This framework includes the following:
- Health event logs indexed in an internal Partition.
- A health events table on the Alerts page.
- A health status column on the Collection page.
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. For details on what information is available in a health event, see the common parameters table.
Health events table
The health events table allows you to easily view and investigate problems getting your data to Sumo.
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.
The health events table is at Manage Data > Alerts > Health Events.
Click on a row to view the details of a health event.
Under the More Actions menu you can select:
- Event History to run a search against the sumologic_system_events Partition to view all of the related event logs.
- View Object to view the Collector or Source in the Collection page related to the event.
Health events severity
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.
A warning indicates the Collector or Source has a configuration issue or is operating in a degraded state.
An error indicates the Collector or Source is unable to collect data as expected.
Each health event log has common keys that categorize it to a product area and provide details of the event. The following table shows the common parameters in the order that they are found in health event logs.
|details||The details of the event include the type as
||JSON object of Strings|
|eventType||Health events have a value of
|accountId||The unique identifier of the organization.||String|
|eventId||The unique identifier of the event.||String|
|eventName||The name of the event.||String|
|eventTime||The event timestamp in ISO 8601 format.||String|
|eventFormatVersion||The event log format version.||String|
|operator||Information on who did the operation. If it's missing, the Sumo service was the operator.||JSON object of Strings|
|subsystem||The product area of the event.||String|
|resourceIdentity||This includes any unique identifiers, names, and the type of the object associated with the event.||JSON object of Strings|
Health event log example
"name": "Failed to find the file path",
"description": "File collection is not working as expected because of invalid path."
"eventFormatVersion": "1.0 beta",
Search health events
To search all health events run a query against the internal partition named sumologic_system_events. For example,
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 fields are assigned to health event logs as follows:
|Metadata Field||Assignment Description|
|_sourceCategory||Value of the common parameter,
|_sourceName||Value of the common parameter,
|_sourceHost||The remote IP address of the host that made the request. If not available the value will be
A Health column on the Collection page shows color-coded healthy, error, and warning states for Collectors and Sources so you can quickly determine the health of your Collectors and Sources.
- You can hover your mouse over a Collector or Source to view a tooltip that provides the number of health events detected on the Collector or Source.
You can click on the Health status in a row to view a pop-up displaying a list of related events.