OSDOCS-17079-1: CQA 2.0 for SUPP-1: Remote Health Monitoring (Insight…#114766
OSDOCS-17079-1: CQA 2.0 for SUPP-1: Remote Health Monitoring (Insight…#114766dfitzmau wants to merge 1 commit into
Conversation
|
@dfitzmau: This pull request references OSDOCS-17079 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
36dad76 to
224564f
Compare
9dacc12 to
54ce47d
Compare
e9315f7 to
e2f988e
Compare
|
@dfitzmau: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| @@ -31,13 +30,16 @@ ifdef::openshift-rosa,openshift-dedicated[] | |||
| endif::openshift-rosa,openshift-dedicated[] | |||
| * The *insights-config* `ConfigMap` object exists in the `openshift-insights` namespace. | |||
There was a problem hiding this comment.
| * The *insights-config* `ConfigMap` object exists in the `openshift-insights` namespace. | |
| * The `insights-config` `ConfigMap` object exists in the `openshift-insights` namespace. |
|
|
||
| . Go to *Workloads* -> *ConfigMaps* and select *Project: openshift-insights*. | ||
|
|
||
| . Click on the *insights-config* `ConfigMap` object to open it. |
There was a problem hiding this comment.
| . Click on the *insights-config* `ConfigMap` object to open it. | |
| . Click the *insights-config* `ConfigMap` object to open it. |
ISG advises to use "click" instead of "click on": https://www.ibm.com/docs/en/ibm-style?topic=word-usage#click
|
|
||
| [NOTE] | ||
| ==== | ||
| Previously, a cluster administrator would create or edit the {insights-operator} configuration using a *support secret* in the `openshift-config` namespace. {red-hat-lightspeed} now supports the creation of a `ConfigMap` object to configure the {insights-operator}. The {insights-operator} gives preference to the config map configuration over the support secret if both exist. |
There was a problem hiding this comment.
In modules/disabling-insights-operator-alerts.adoc, you removed the bold formatting from the phrase "support secret". Just wondering if you need to do the same thing here.
| = Enabling {insights-operator} alerts | ||
|
|
||
| [role="_abstract"] | ||
| When alerts are disabled, the {insights-operator} no longer sends alerts to the cluster Prometheus instance. You can reenable them. |
There was a problem hiding this comment.
| When alerts are disabled, the {insights-operator} no longer sends alerts to the cluster Prometheus instance. You can re-enable them. |
|
|
||
| [NOTE] | ||
| ==== | ||
| The *insights-config* `ConfigMap` object follows standard YAML formatting, wherein child values are below the parent attribute and indented two spaces. For the *Obfuscation* attribute, enter values as bulleted children of the parent attribute. |
There was a problem hiding this comment.
| The *insights-config* `ConfigMap` object follows standard YAML formatting, wherein child values are below the parent attribute and indented two spaces. For the *Obfuscation* attribute, enter values as bulleted children of the parent attribute. | |
| The `insights-config` `ConfigMap` object follows standard YAML formatting, wherein child values are below the parent attribute and indented two spaces. For the `Obfuscation` attribute, enter values as bulleted children of the parent attribute. |
Just a couple formatting nits to maintain consistency with other docs.
| ---- | ||
| * To enable persistent storage to retain the data archive file and history for up to the last 10 data gathering jobs, define the `storage` specification. Set *type* to `PersistentVolume`, and define the `mountPath` and `name` of the volume, as outlined in the following example: | ||
| + | ||
| * To enable persistent storage to retain the data archive file and history for up to the last 10 data gathering jobs, define the `storage` specification. Set *type* to `PersistentVolume`, and define the `mountPath` and `name` of the volume: |
There was a problem hiding this comment.
Should "type" be in bold, or in monospace font?
|
|
||
| :_mod-docs-content-type: CONCEPT | ||
| [id="running-insights-operator-gather_{context}"] | ||
| = Running an {insights-operator} gather operation on-demand |
There was a problem hiding this comment.
Since this is a concept module, I believe the title should be a noun phrase instead of a gerund. Here's a suggestion:
| = Running an {insights-operator} gather operation on-demand | |
| = On-demand {insights-operator} gather operations |
|
|
||
| [role="_abstract"] | ||
| In {product-title}, customers can disable reporting usage information. | ||
| You can disable reporting usage information but understand potential consequences before doing so. |
There was a problem hiding this comment.
| You can disable reporting usage information but understand potential consequences before doing so. | |
| You can disable reporting usage information, but understand potential consequences before doing so. |
|
|
||
| :_mod-docs-content-type: CONCEPT | ||
| [id="understanding-insights-operator-alerts_{context}"] | ||
| = Understanding {insights-operator} alerts |
There was a problem hiding this comment.
I believe the title should be a noun phrase since this is a concept module.
| = Understanding {insights-operator} alerts | |
| = {insights-operator} alerts |
|
|
||
| toc::[] | ||
|
|
||
| [role="_abstract"] |
There was a problem hiding this comment.
I noticed in the preview that the short description contains a URL. I didn't think that was allowed, so it would be good to double-check.
Version(s):
4.20+
Issue:
OSDOCS-17079
Link to docs preview: