Skip to content

Commit 93f37a4

Browse files
authored
Automation Controller Administration Guide/ User Guide typos/Link error? (RedHatInsights#1256)
https://issues.redhat.com/browse/AAP-20052 affects `titles/controller-admin-guide` and `controller-user-guide`
1 parent a4cc3ad commit 93f37a4

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

downstream/modules/platform/proc-controller-adding-gpg-key.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
= Adding a GPG key to {ControllerName}
44

5-
To use the GPG key for content singing and validation in {ControllerName}, add it by running the following command in the CLI:
5+
To use the GPG key for content signing and validation in {ControllerName}, add it by running the following command in the CLI:
66

77
[literal, options="nowrap" subs="+attributes"]
88
----

downstream/modules/platform/ref-controller-metrics-monitoring.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The metrics endpoint includes descriptions of each metric. Metrics of particular
1515
** colloquially called “job events lag”.
1616
** Running average of the lag time between when a task occurred in ansible and when the user is able to see it. This indicates how far behind the callback receiver is in processing events. When this number is very high, users can consider scaling up the control plane or using the capacity adjustment feature to reduce the number of jobs a control node controls.
1717
* `callback_receiver_events_insert_db`
18-
** Counter of events that have been inserted by a node. Can be used to calculate the job even insertion rate over a given time period.
18+
** Counter of events that have been inserted by a node. Can be used to calculate the job event insertion rate over a given time period.
1919
* `callback_receiver_events_queue_size_redis`
2020
** Indicator of how far behind callback receiver is in processing events. If too high, Redis can cause the control node to run out of memory (OOM).
2121

0 commit comments

Comments
 (0)