Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions _topic_map.yml
Original file line number Diff line number Diff line change
Expand Up @@ -786,6 +786,8 @@ Topics:
File: configuring-the-monitoring-stack
- Name: Managing cluster alerts
File: managing-cluster-alerts
- Name: Examining cluster metrics
File: examining-cluster-metrics
- Name: Accessing Prometheus, Alertmanager, and Grafana
File: prometheus-alertmanager-and-grafana
- Name: Exposing custom application metrics for autoscaling
Expand Down
File renamed without changes
File renamed without changes
Binary file added images/monitoring-metrics-screen.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
File renamed without changes
File renamed without changes
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,9 @@
// * monitoring/cluster-monitoring/prometheus-alertmanager-and-grafana.adoc

[id="monitoring-accessing-prometheus-alerting-ui-grafana-using-the-web-console_{context}"]
= Accessing Prometheus, Alerting UI, and Grafana using the Web console
= Accessing Prometheus, Alerting UI, and Grafana using the web console

You can access Prometheus, Alerting UI, and Grafana web UIs using a Web browser through the {product-title} Web console.
You can access Prometheus, Alerting UI, and Grafana web UIs using a web browser through the {product-title} web console.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prometheus, Alerting UI, and Grafana web UIs
=>
Prometheus, Alerting, and Grafana web UIs

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implemented in #16978.


[NOTE]
====
Expand All @@ -18,11 +18,11 @@ The Alerting UI accessed in this procedure is the new interface for Alertmanager

.Procedure

. Navigate to the {product-title} Web console and authenticate.
. Navigate to the {product-title} web console and authenticate.

. To access Prometheus, navigate to "Monitoring" -> "Metrics".
. To access Prometheus, navigate to the "Monitoring" -> "Metrics" page.
+
To access the Alerting UI, navigate to "Monitoring" -> "Alerts" or "Monitoring" -> "Silences".
To access the Alerting UI, navigate to the "Monitoring" -> "Alerting" page.
+
To access Grafana, navigate to "Monitoring" -> "Dashboards".
To access Grafana, navigate to the "Monitoring" -> "Dashboards" page.

Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
[id="monitoring-accessing-prometheus-alertmanager-grafana-directly_{context}"]
= Accessing Prometheus, Alertmanager, and Grafana directly

You can access Prometheus, Alertmanager, and Grafana web UIs using the `oc` tool and a Web browser.
You can access Prometheus, Alertmanager, and Grafana web UIs using the `oc` tool and a web browser.

[NOTE]
====
Expand Down Expand Up @@ -38,5 +38,5 @@ For example, this is the resulting URL for Alertmanager:
https://alertmanager-main-openshift-monitoring.apps._url_.openshift.com
----

. Navigate to the address using a Web browser and authenticate.
. Navigate to the address using a web browser and authenticate.

Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,6 @@ Before application developers can monitor their applications, the human operator

.Procedure

. In the {product-title} web console, navigate to *Operators* -> *OperatorHub* and install the Prometheus Operator in the namespace where your application is.
. In the {product-title} web console, navigate to the *Operators* -> *OperatorHub* page and install the Prometheus Operator in the namespace where your application is.

. Navigate to *Catalog* -> *Developer Catalog* and install Prometheus, Alertmanager, Prometheus Rule, and Service Monitor in the same namespace.
. Navigate to the *Catalog* -> *Developer Catalog* page and install Prometheus, Alertmanager, Prometheus Rule, and Service Monitor in the same namespace.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Navigate to the Catalog -> Developer Catalog page
It is better change to
Navigate to the Operators -> Installed Operators page

reason: there is not link in the left navigation area links to /catalog page

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implemented in #16978.

14 changes: 7 additions & 7 deletions modules/monitoring-contents-of-the-alerting-ui.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,13 @@
[id="contents-of-the-alerting-ui_{context}"]
= Contents of the Alerting UI

This section shows and explains the contents of the Alerting UI, a Web interface to the Alertmanager.
This section shows and explains the contents of the Alerting UI, a web interface to the Alertmanager.

The main three pages of the Alerting UI are the *Alerts*, the *Silences*, and the *YAML* pages.

The *Alerts* page is located in *Monitoring* -> *Alerts* of the {product-title} web console.
The *Alerts* page is accessible by clicking *Monitoring* -> *Alerts* in the {product-title} web console.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Alerts page is accessible by clicking Monitoring -> Alerting -> Alerts

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implemented in #16978.


image::alerts-screen.png[]
image::monitoring-alerts-screen.png[]

. Filtering alerts by their names.
. Filtering the alerts by their states. To fire, some alerts need a certain condition to be true for the duration of a timeout. If a condition of an alert is currently true, but the timeout has not been reached, such an alert is in the *Pending* state.
Expand All @@ -21,9 +21,9 @@ image::alerts-screen.png[]
. Value of the Severity label of the alert.
. Actions you can do with the alert.

The *Silences* page is located in *Monitoring* -> *Silences* of the {product-title} web console.
The *Silences* page is accessible by clicking *Monitoring* -> *Silences* in the {product-title} web console.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Silences page is accessible by clicking Monitoring -> Alerting -> Silences

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implemented in #16978.


image::silences-screen.png[]
image::monitoring-silences-screen.png[]

. Creating a silence for an alert.
. Filtering silences by their name.
Expand All @@ -33,9 +33,9 @@ image::silences-screen.png[]
. Number of alerts that are being silenced by the silence.
. Actions you can do with a silence.

The *YAML* page is located in *Monitoring* -> *Alerting* -> *YAML* of the OpenShift Container Platform web console.
The *YAML* page is accessible by clicking *Monitoring* -> *Alerting* -> *YAML* in the {product-title} web console.

image::yaml-screen.png[]
image::monitoring-yaml-screen.png[]

. Upload a file with Alertmanager configuration.
. Examine and edit the current Alertmanager configuration.
Expand Down
35 changes: 35 additions & 0 deletions modules/monitoring-contents-of-the-metrics-ui.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
// Module included in the following assemblies:
//
// * monitoring/cluster-monitoring/examining-cluster-metrics.adoc

[id="contents-of-the-metrics-ui_{context}"]
= Contents of the Metrics UI

This section shows and explains the contents of the Metrics UI, a web interface to Prometheus.

The *Metrics* page is accessible by clicking *Monitoring* -> *Metrics* in the {product-title} web console.

image::monitoring-metrics-screen.png[]

. Actions.
* Add query.
* Expand all query tables.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If one result table is collapse, the menu is "Collapse all query tables", if all tables are collapsed, the menu is "Expand all query tables"
I think
Expand/Collapse all query tables(Based on the result table is collapsed or expanded) is better.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed to "Expand or collapse", but didn't use "(Based on the result table is collapsed or expanded)", it is too long and unnecessary.
Implemented in #16978.

* Delete all queries.
. Hide the plot.
. The interactive plot.
. The catalog of available metrics.
. Add query.
. Run queries.
. Query forms.
. Expand or collapse the form.
. The query.
. Clear query.
. Disable query.
. Actions for a specific query.
* Disable query.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if the query is disabled, the menu is "Enable query",
if the query is enabled, the menu is "Disable query"
I think
Enable /Disable query(Based on the query is disabled or enabled ) is better.

It is the same for "Hide all series"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed to "Enable or disable", but didn't use "(Based on the query is disabled or enabled )", it is too long and unnecessary.
Implemented in #16978.

* Hide all series of the query from the plot.
* Delete query.
. The metrics table for a query.
. Color assigned to the graph of the metric. Clicking the square shows or hides the metric's graph.

Additionally, there is a link to the old Prometheus interface next to the title of the page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say: You can access the old Prometheus interface by clicking the Prometheus UI link at the top of the page.

Would someone know it's the old interface? Or is it just an alternate interface?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The perspective of this whole section is "what do we have in this interface", that's why for all items I just call them out and say what they are for. You suggestion is valid for a procedure module.
It's not the best word, true. We are using old to imply that people should move away from that and into the new interface developed by the OCP team. "Alternate" interface doesn't have that implication. As to whether someone would know: maybe not, and that's why we'd better tell them.

2 changes: 1 addition & 1 deletion modules/monitoring-editing-silences.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ You can edit a silence, which will expire the existing silence and create a new

.Procedure

. Navigate to the *Monitoring* -> *Silences* screen.
. Navigate to the *Monitoring* -> *Alerting* -> *Silences* page.

. For the silence you want to modify, click the button in the last column and click *Edit silence*.
+
Expand Down
2 changes: 1 addition & 1 deletion modules/monitoring-expiring-silences.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ You can expire a silence. Expiring a silence deactivates it forever.

.Procedure

. Navigate to the *Monitoring* -> *Silences* page.
. Navigate to the *Monitoring* -> *Alerting* -> *Silences* page.

. For the silence you want to expire, click the button in the last column and click *Expire Silence*.
+
Expand Down
26 changes: 26 additions & 0 deletions modules/monitoring-exploring-the-visualized-metrics.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
// Module included in the following assemblies:
//
// * monitoring/cluster-monitoring/examining-cluster-metrics.adoc

[id="exploring-the-visualized-metrics_{context}"]
= Exploring the visualized metrics

After running the queries, the metrics are displayed on the interactive plot. The X axis of the plot represents time. The Y axis represents the metrics values. Each metric is shown as a colored graph. You can manipulate the plot and explore the metrics.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not a term though. It just refers to something on the plot and says what it represents.
And it's also one of the many things I'm describing here, and not particularly important in any way. So I don't see a need to emphasize this. Besides, by that logic, I'd want to italicize "the interactive plot" and "colored graph". I think all that is unnecessary.
It's also used only once, so it's first and only usage.


.Procedure

. Initially, all metrics from all enabled queries are shown on the plot. You can select which metrics are shown.
* To hide all metrics from a query, click {kebab} for the query and click *Hide all series*.
* To hide a specific metric, go to the query table and click the colored square near the metric name.
. To zoom into the plot and change the shown time range, do one of the following:
+
--
* Visually select the time range by clicking and dragging on the plot horizontally.
* Use the menu in the left upper corner to select the time range.
--
+
To reset the time range, click *Reset Zoom*.
. To display outputs of all queries at a specific point in time, hold the mouse cursor on the plot at that point. The query outputs will appear in a pop-up box.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hold the mouse cursor on the plot at that point
what about changing to "move the mouse cursor over the line"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's enough to just be on the right point in the X axis (time), you can be anywhere in the Y axis (metric value). It's good if the users know that, that's why I used the wording "on the plot at that point [in time]". You don't need to put cursor directly over the graph ("the line").
Not implemented.

. For more detailed information about metrics of a specific query, expand the table of that query using the drop-down button. Every metric is shown with its current value.
. To hide the plot, click *Hide Graph*.

Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ You can find an alert and see information about it or its governing alerting rul

.Procedure

. Open the {product-title} web console and navigate to *Monitoring* -> *Alerts*.
. Open the {product-title} web console and navigate to the *Monitoring* -> *Alerting* -> *Alerts* page.

. Optional: Filter the alerts by name using the *Filter alerts by name* field.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Filter alerts by name
=>
Filter Alerts by name

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implemented in #16978.


Expand All @@ -21,7 +21,7 @@ You can find an alert and see information about it or its governing alerting rul
+
To see alert details, click on the name of the alert. This is the page with alert details:
+
image::alert-overview.png[]
image::monitoring-alert-overview.png[]
+
The page has the graph with timeseries of the alert. It also has information about the alert, including:
+
Expand All @@ -32,7 +32,7 @@ The page has the graph with timeseries of the alert. It also has information abo
+
To see alerting rule details, click the button in the last column and select *View Alerting Rule*. This is the page with alerting rule details:
+
image::alerting-rule-overview.png[]
image::monitoring-alerting-rule-overview.png[]
+
The page has information about the alerting rule, including:
+
Expand Down
2 changes: 1 addition & 1 deletion modules/monitoring-getting-information-about-silences.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ You can find a silence and view its details.

.Procedure

. Open the {product-title} web console and navigate to *Monitoring* -> *Silences*.
. Open the {product-title} web console and navigate to the *Monitoring* -> *Alerting* -> *Silences* page.

. Optional: Filter the silences by name using the *Filter Silences by name* field.

Expand Down
30 changes: 30 additions & 0 deletions modules/monitoring-running-metrics-queries.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
// Module included in the following assemblies:
//
// * monitoring/cluster-monitoring/examining-cluster-metrics.adoc

[id="running-metrics-queries_{context}"]
= Running metrics queries

You begin working with metrics by entering one or several Prometheus Query Language (PromQL) queries.

.Procedure

. Open the {product-title} web console and navigate to the *Monitoring* -> *Metrics* page.

. In the query field, enter your PromQL query.
* To show all available metrics and PromQL functions, click *Insert Metric at Cursor*.
. For multiple queries, click *Add Query*.
. For deleting queries, click {kebab} for the query, then select *Delete query*.
. For keeping but not running a query, click the *Disable query* button.
. Once you finish creating queries, click the *Run Queries* button. The metrics from the queries are visualized on the plot. If a query is invalid, the UI shows an error message.
+
[NOTE]
====
Queries that operate on large amounts of data might timeout or overload the browser when drawing timeseries graphs. To avoid this, hide the graph and calibrate your query using only the metrics table. Then, after finding a feasible query, enable the plot to draw the graphs.
====
+
. Optional: The page URL now contains the queries you ran. To use this set of queries again in the future, save this URL.

.Additional resources

See the link:https://prometheus.io/docs/prometheus/latest/querying/basics/[Prometheus Query Language documentation].
4 changes: 2 additions & 2 deletions modules/monitoring-silencing-alerts.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ You can either silence a specific alert or silence alerts that match a specifica

To silence a set of alerts by creating an alert specification:

. Navigate to the *Monitoring* -> *Silences* page of the {product-title} web console.
. Navigate to the *Monitoring* -> *Alerting* -> *Silences* page of the {product-title} web console.

. Click *Create Silence*.

Expand All @@ -21,7 +21,7 @@ To silence a set of alerts by creating an alert specification:

To silence a specific alert:

. Navigate to the *Monitoring* -> *Alerts* page of the {product-title} web console.
. Navigate to the *Monitoring* -> *Alerting* -> *Alerts* page of the {product-title} web console.

. For the alert that you want to silence, click the button in the last column and click *Silence Alert*. The *Create Silence* form will appear with prepopulated specification of the chosen alert.

Expand Down
17 changes: 17 additions & 0 deletions monitoring/cluster-monitoring/examining-cluster-metrics.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
[id="examining-cluster-metrics"]
= Examining cluster metrics
include::modules/common-attributes.adoc[]
:context: querying-metrics

toc::[]

{product-title} {product-version} provides a web interface to Prometheus, which enables you to run Prometheus Query Language (PromQL) queries and examine the metrics visualized on a plot. This functionality provides an extensive overview of the cluster state and enables you to troubleshoot problems.

include::modules/monitoring-contents-of-the-metrics-ui.adoc[leveloffset=+1]
include::modules/monitoring-running-metrics-queries.adoc[leveloffset=+1]
include::modules/monitoring-exploring-the-visualized-metrics.adoc[leveloffset=+1]

.Next steps

xref:../../monitoring/cluster-monitoring/prometheus-alertmanager-and-grafana.adoc#prometheus-alertmanager-and-grafana[Access the Prometheus, Alertmanager, and Grafana.]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Access the Prometheus, Alertmanager, and Grafana. interfaces? pages? Besides being grouped together, I'm not sure what the relationship is between these?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was asked (twice) to leave "interfaces" out of this wording due to some technicality (frankly I don't remember what technicality).
These three things is why have the monitoring stack at all. They are how you actually use the stack once you've configured it.


4 changes: 2 additions & 2 deletions monitoring/cluster-monitoring/managing-cluster-alerts.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ include::modules/common-attributes.adoc[]

toc::[]

{product-title} 4 provides a Web interface to the Alertmanager, which enables you to manage alerts. This section demonstrates how to use the Alerting UI.
{product-title} {product-version} provides a web interface to the Alertmanager, which enables you to manage alerts. This section demonstrates how to use the Alerting UI.

include::modules/monitoring-contents-of-the-alerting-ui.adoc[leveloffset=+1]
include::modules/monitoring-getting-information-about-alerts-and-alerting-rules.adoc[leveloffset=+1]
Expand All @@ -16,5 +16,5 @@ include::modules/monitoring-expiring-silences.adoc[leveloffset=+1]

.Next steps

xref:../../monitoring/cluster-monitoring/prometheus-alertmanager-and-grafana.adoc#prometheus-alertmanager-and-grafana[Access the Prometheus, Alertmanager, and Grafana.]
xref:../../monitoring/cluster-monitoring/examining-cluster-metrics.adoc#examining-cluster-metrics[Examine cluster metrics.]