Event properties and severity levels
IBM® Hybrid Cloud Mesh (Mesh) events include properties such as a message, status, time created, resource affected, severity level, and more. Read details about these properties and severity levels.
Event properties
The following properties describe events:
| Properties | Description |
|---|---|
message |
A description of the event. |
severity |
The impact on the system and the potential errors it can cause. The possible values are critical, major, minor, information, cleared. |
category |
The system category of the event. The possible values are system, recommendation. |
created_at |
The date when the event was created. |
correlated |
If the event is cleared, this field points to the event that it cleared. |
resource_instance, resource_name |
The resource that the event relates to. |
resource_type |
The type of resource that the event relates to, that is, either gateway or cloud. |
You can also edit the following properties to help you to manage events:
| Editable properties | Description |
|---|---|
assigned_user |
The email address of the user who is assigned to handle the event. |
comment |
Comments that relate to handling this event that the user enters. |
labels |
User-defined labels. For example, you can use labels to categorize the event or to set its state. |
is_handled |
Set this property to true when the event is addressed. |
Event severity levels
The event severity levels are defined in the following table:
| Severity | Definition | Examples |
|---|---|---|
critical |
An indication of a severe service problem, affecting core functionality, that requires immediate attention and resolution, regardless of the time of day. |
|
major |
An indication of a problem that has, or might have, a significant impact on service. Steps must be taken as soon as possible because the affected service has degraded drastically and is in danger of being lost completely. |
|
minor |
An indication of a problem that does not have a serious impact on service. Instead, it affects only convenience for the users. A way to work around the problem exists or the system is operating suboptimally. This event does not require immediate attention. | A cloud location was discovered with no GPS coordinates |
information |
An event that is a result of normal operation of the system. |
|
cleared |
Indicates that the previous event in the correlated field automatically resolved. |
A gateway that was unreachable is now reachable |