-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
MGMT-16977: Mapping Alerts to AlarmEventRecords
Added mapping logic to the AlarmFetcher: * For each Alert retrieved from the AlertManager, map to an AlarmEventRecord object. * Use the resource server url for fetching info about resources and pools (needed for resourceID/resourceTypeID properties). Also added an API for fetching alarm probable causes: * This API is not defined by O2ims spec, but we can use it for exposing a custom list of probable causes. * This list is available in data folder (data/alarms/probable_causes.json), and can be customized and maintained by server admins as required. Note: this PR does not include AlarmDictionary support (will be handled separately).
- Loading branch information
1 parent
8e230b2
commit 25fbdef
Showing
10 changed files
with
1,098 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
[ | ||
{ | ||
"probableCauseId": "Watchdog", | ||
"name": "An alert that should always be firing to certify that Alertmanager is working properly.", | ||
"description": "This is an alert meant to ensure that the entire alerting pipeline is functional.\nThis alert is always firing, therefore it should always be firing in Alertmanager\nand always fire against a receiver. There are integrations with various notification\nmechanisms that send a notification when this alert is not firing. For example the\n\"DeadMansSnitch\" integration in PagerDuty.\n" | ||
}, | ||
{ | ||
"probableCauseId": "UpdateAvailable", | ||
"name": "Your upstream update recommendation service recommends you update your cluster.", | ||
"description": "For more information refer to 'oc adm upgrade' or https://console-openshift-console.apps.spoke1.redhat.com/settings/cluster/." | ||
}, | ||
{ | ||
"probableCauseId": "NodeClockNotSynchronising", | ||
"name": "Clock not synchronising.", | ||
"description": "Clock on ostest-extraworker-1 is not synchronising. Ensure NTP is configured on this host." | ||
}, | ||
{ | ||
"probableCauseId": "ClusterNotUpgradeable", | ||
"name": "One or more cluster operators have been blocking minor version cluster upgrades for at least an hour.", | ||
"description": "In most cases, you will still be able to apply patch releases. Reason AdminAckRequired. For more information refer to 'oc adm upgrade' or https://console-openshift-console.apps.spoke1.redhat.com/settings/cluster/." | ||
}, | ||
{ | ||
"probableCauseId": "AlertmanagerReceiversNotConfigured", | ||
"name": "Receivers (notification integrations) are not configured on Alertmanager", | ||
"description": "Alerts are not configured to be sent to a notification system, meaning that you may not be notified in a timely fashion when important failures occur. Check the OpenShift documentation to learn how to configure notifications with Alertmanager." | ||
}, | ||
{ | ||
"probableCauseId": "HighOverallControlPlaneMemory", | ||
"name": "Memory utilization across all control plane nodes is high, and could impact responsiveness and stability.", | ||
"description": "Given three control plane nodes, the overall memory utilization may only be about 2/3 of all available capacity. This is because if a single control plane node fails, the kube-apiserver and etcd my be slow to respond. To fix this, increase memory of the control plane nodes." | ||
} | ||
] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.