Skip to content

Commit e1d968a

Browse files
author
Suyog Sainkar
committed
Applied SME feedback
1 parent 731a03f commit e1d968a

File tree

1 file changed

+11
-8
lines changed

1 file changed

+11
-8
lines changed

doc-Monitoring_Alerts_and_Reporting/topics/Integrating_Prometheus_Alerts.adoc

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,24 +3,24 @@
33

44
[NOTE]
55
====
6-
This feature is available with this release of {product-title} as a technology preview only. For more information on the support scope for features marked as technology previews, see https://access.redhat.com/support/offerings/techpreview[Technology Preview Features Support Scope].
6+
This feature is currently available as a technology preview only. For more information on the support scope for features marked as technology previews, see https://access.redhat.com/support/offerings/techpreview[Technology Preview Features Support Scope].
77
====
88

9-
Prometheus is used as an external alerting component. {product-title_short} integrates Prometheus alerts for use with OpenShift Container Platform. {product-title_short} collects EmsEvents from Prometheus, generates alerts based on these events, and then attaches alerts to inventory objects.
9+
Prometheus is used as an external alerting component. {product-title_short} integrates Prometheus alerts for use with OpenShift Container Platform. {product-title_short} collects events from Prometheus, generates alerts based on these events, and then attaches alerts to inventory objects.
1010

11-
It is possible to view ongoing alerts in {product-title_short} and manage their life cycle, including the ability to:
11+
It is possible to view ongoing alerts in {product-title_short} by navigating to menu:Monitor[Alerts] and manage their life cycle, including the ability to:
1212

13-
* View active alerts per provider in the alert dashboard.
13+
* View active alerts per provider in the *Overview* screen.
1414
* View alert data and related objects.
15-
* Assign and acknowledge alerts in the alerts list screen.
15+
* Comment, assign, and acknowledge alerts in the *All Alerts* screen.
1616

1717
=== Configuring Prometheus Alerts in {product-title_short}
1818

1919
Configuring and enabling Prometheus alerts in {product-title_short} comprises the following steps:
2020

2121
. Deploying and configuring Prometheus on OpenShift.
2222
. Assigning Prometheus alert profiles to the enterprise in {product-title_short}.
23-
. Adding OpenShift Containers Providers and Prometheus alert endpoints in {product-title_short}.
23+
. Adding an OpenShift Containers Provider with a Prometheus alert endpoint in {product-title_short}.
2424

2525
==== Deploying and Configuring Prometheus on OpenShift
2626

@@ -38,6 +38,9 @@ $ oc edit configmap -n openshift-metrics prometheus
3838
- name: example-rules
3939
interval: 30s # defaults to global interval
4040
rules:
41+
42+
<<
43+
4144
- alert: "NodeDown"
4245
expr: up{job="kubernetes-nodes"} == 0
4346
annotations:
@@ -81,9 +84,9 @@ Alerts triggered before assigning the profiles to the enterprise will not appear
8184
+
8285

8386

84-
==== Adding OpenShift Containers Providers and Prometheus Alert Endpoints
87+
==== Adding an OpenShift Containers Provider with a Prometheus Alert Endpoint
8588

86-
Complete the following procedure using the {product-title_short} user interface to add OpenShift Containers Provider and Prometheus alerts endpoints.
89+
Complete the following procedure using the {product-title_short} user interface to add an OpenShift Containers Provider with a Prometheus alert endpoint.
8790

8891
. Navigate to menu:Compute[Containers > Providers].
8992
. Click image:1847.png[Configuration] (*Configuration*), then click image:1862.png[Add New Containers Provider] (*Add New Containers Provider*).

0 commit comments

Comments
 (0)