Skip to content

Commit 2e16c73

Browse files
authored
Merge pull request #82491 from michelle-purcell/HCCDOC-2908-InsightsOperatorEnhancement
HCCDOC-2908 Add notes to gather operations procedure for Insights Operator
2 parents 83d986a + f20e590 commit 2e16c73

File tree

3 files changed

+40
-20
lines changed

3 files changed

+40
-20
lines changed

modules/running-insights-operator-gather-cli.adoc

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@
55

66
:_mod-docs-content-type: PROCEDURE
77
[id="running-insights-operator-gather-openshift-cli_{context}"]
8-
= Running an Insights Operator gather operation using the OpenShift CLI
9-
You can run an Insights Operator gather operation using the {product-title} command line interface.
8+
= Running an Insights Operator gather operation from the OpenShift CLI
9+
You can run an Insights Operator gather operation by using the {product-title} command line interface.
1010

1111
.Prerequisites
1212

@@ -20,7 +20,7 @@ You can run an Insights Operator gather operation using the {product-title} comm
2020
$ oc apply -f <your_datagather_definition>.yaml
2121
----
2222
+
23-
Replace `<your_datagather_definition>.yaml` with a configuration file using the following parameters:
23+
Replace `<your_datagather_definition>.yaml` with a configuration file that contains the following parameters:
2424
+
2525
[source,yaml]
2626
----
@@ -35,11 +35,16 @@ spec:
3535
----
3636
+
3737
--
38-
<1> Replace the `<your_data_gather>` with a unique name for your gather operation.
39-
<2> Enter individual gather operations to disable under the `gatherers` parameter. This example disables the `workloads` data gather operation and will run the remainder of the default operations. To run the complete list of default gather operations, leave the `spec` parameter empty. You can find the complete list of gather operations in the Insights Operator documentation.
38+
<1> Under *metadata*, replace `<your_data_gather>` with a unique name for the gather operation.
39+
<2> Under *gatherers*, specify any individual gather operations that you intend to disable. In the example provided, `workloads` is the only data gather operation that is disabled and all of the other default operations are set to run.
40+
When the `spec` parameter is empty, all of the default gather operations run.
4041
--
4142
42-
.Verification
43+
[IMPORTANT]
44+
====
45+
Do not add a prefix of `periodic-gathering-` to the name of your gather operation because this string is reserved for other administrative operations and might impact the intended gather operation.
46+
====
4347

44-
* Check that your new gather operation is prefixed with your chosen name under the list of pods in the `openshift-insights` project. Upon completion, the Insights Operator automatically uploads the data to Red Hat for processing.
48+
.Verification
4549

50+
* Check that your new gather operation is prefixed with your chosen name under the list of pods in the `openshift-insights` project. Upon completion, the Insights Operator automatically uploads the data to Red Hat for processing.

modules/running-insights-operator-gather-web-console.adoc

Lines changed: 22 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -6,20 +6,22 @@
66
:_mod-docs-content-type: PROCEDURE
77

88
[id="running-insights-operator-gather-web-console_{context}"]
9-
= Running an Insights Operator gather operation using the web console
10-
You can run an Insights Operator gather operation using the {product-title} web console.
9+
= Running an Insights Operator gather operation from the web console
10+
To collect data, you can run an Insights Operator gather operation by using the {product-title} web console.
1111

1212
.Prerequisites
1313

1414
* You are logged in to the {product-title} web console as a user with the `cluster-admin` role.
1515

1616
.Procedure
1717

18-
. Navigate to *Administration* -> *CustomResourceDefinitions*.
19-
. On the *CustomResourceDefinitions* page, use the *Search by name* field to find the *DataGather* resource definition and click it.
18+
. On the console, select *Administration* -> *CustomResourceDefinitions*.
19+
. On the *CustomResourceDefinitions* page, in the *Search by name* field, find the *DataGather* resource definition, and then click it.
20+
. On the console, select *Administration* -> *CustomResourceDefinitions*.
21+
. On the *CustomResourceDefinitions* page, in the *Search by name* field, find the *DataGather* resource definition, and then click it.
2022
. On the *CustomResourceDefinition details* page, click the *Instances* tab.
2123
. Click *Create DataGather*.
22-
. To create a new `DataGather` operation, edit the configuration file:
24+
. To create a new `DataGather` operation, edit the following configuration file and then save your changes.
2325
+
2426
[source,yaml]
2527
----
@@ -34,15 +36,22 @@ spec:
3436
----
3537
+
3638
--
37-
<1> Replace the `<your_data_gather>` with a unique name for your gather operation.
38-
<2> Enter individual gather operations to disable under the `gatherers` parameter. This example disables the `workloads` data gather operation and will run the remainder of the default operations. To run the complete list of default gather operations, leave the `spec` parameter empty. You can find the complete list of gather operations in the Insights Operator documentation.
39+
<1> Under *metadata*, replace `<your_data_gather>` with a unique name for the gather operation.
40+
<2> Under *gatherers*, specify any individual gather operations that you intend to disable. In the example provided, `workloads` is the only data gather operation that is disabled and all of the other default operations are set to run.
41+
When the `spec` parameter is empty, all of the default gather operations run.
3942
--
40-
+
41-
. Click *Save*.
43+
44+
[IMPORTANT]
45+
====
46+
Do not add a prefix of `periodic-gathering-` to the name of your gather operation because this string is reserved for other administrative operations and might impact the intended gather operation.
47+
====
4248

4349
.Verification
4450

45-
. Navigate to *Workloads* -> *Pods*.
46-
. On the Pods page, select the *Project* pulldown menu, and then turn on Show default projects.
47-
. Select the `openshift-insights` project from the *Project* pulldown menu.
48-
. Check that your new gather operation is prefixed with your chosen name under the list of pods in the `openshift-insights` project. Upon completion, the Insights Operator automatically uploads the data to Red Hat for processing.
51+
. On the console, select to *Workloads* -> *Pods*.
52+
. On the Pods page, go to the *Project* pull-down menu, and then select *Show default projects*.
53+
. Select the `openshift-insights` project from the *Project* pull-down menu.
54+
. On the console, select to *Workloads* -> *Pods*.
55+
. On the Pods page, go to the *Project* pull-down menu, and then select *Show default projects*.
56+
. Select the `openshift-insights` project from the *Project* pull-down menu.
57+
. Check that your new gather operation is prefixed with your chosen name under the list of pods in the `openshift-insights` project. Upon completion, the Insights Operator automatically uploads the data to Red Hat for processing.

support/remote_health_monitoring/using-insights-operator.adoc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,12 @@ If you enable Technology Preview in your cluster, the Insights Operator runs gat
5555
include::modules/insights-operator-gather-duration.adoc[leveloffset=+2]
5656
include::modules/running-insights-operator-gather-web-console.adoc[leveloffset=+2]
5757
include::modules/running-insights-operator-gather-cli.adoc[leveloffset=+2]
58+
59+
[role="_additional-resources"]
60+
[id="additional-resources"]
61+
.Additional resources
62+
* link:https://github.com/openshift/insights-operator/blob/master/docs/gathered-data.md[Insights Operator Gathered Data GitHub repository]
63+
5864
endif::openshift-rosa,openshift-dedicated[]
5965
// cannot list resource "secrets" in API group "" in the namespace "openshift-config"
6066
ifndef::openshift-rosa,openshift-dedicated[]

0 commit comments

Comments
 (0)