OBSDOCS-1011: Fix information about the user-workload-monitoring-conf…

[eromanova97]

Version(s): enterprise-4.12 and later

Issue: OBSDOCS-1011

Links to docs preview:

• Configuring the monitoring stack
  
• Enabling monitoring for user-defined projects
• Investigating why user-defined project metrics are unavailable

QE review:

• QE has approved this change.

Additional information:

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1011 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

Version(s): enterprise-4.12 and later

Issue: OBSDOCS-1011

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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.

[ocpdocs-previewbot]

🤖 Fri May 10 06:37:18 - Prow CI generated the docs preview:
https://75201--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1011 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

Version(s): enterprise-4.12 and later

Issue: OBSDOCS-1011

Links to docs preview:

• Configuring the monitoring stack
  
• Investigating why user-defined project metrics are unavailable

QE review:

• QE has approved this change.

Additional information:

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.

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1011 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

Version(s): enterprise-4.12 and later

Issue: OBSDOCS-1011

Links to docs preview:

• Configuring the monitoring stack
  
• Enabling monitoring for user-defined projects
• Investigating why user-defined project metrics are unavailable

QE review:

• QE has approved this change.

Additional information:

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.

[juzhao]

for all the description in the PR

** The `user-workload-monitoring-config` `ConfigMap` object exists.

along with the note

[NOTE]
====
Configurations applied to the `user-workload-monitoring-config` `ConfigMap` object are not activated unless a cluster administrator has enabled monitoring for user-defined projects.
====

they look good, but I think change

** The `user-workload-monitoring-config` `ConfigMap` object exists.

to

You have enabled monitoring for user-defined projects

is better, that is more clear, since the user-workload-monitoring-config ConfigMap is created by default if enabled user workload monitoring and users don't need to read the note if they have not enabled monitoring for user-defined projects.

[juzhao]

/lgtm

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1011 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 bug to target the "4.16.0" version, but no target version was set.

In response to this:

Version(s): enterprise-4.12 and later

Issue: OBSDOCS-1011

Links to docs preview:

• Configuring the monitoring stack
  
• Enabling monitoring for user-defined projects
• Investigating why user-defined project metrics are unavailable

QE review:

• QE has approved this change.

Additional information:

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.

[eromanova97]

/label peer-review-needed

[tmalove]

/remove-label peer-review-needed
/label peer-review-in-progress

[skopacz1]

Great work, I just left a few ISG-based nits. Let me know when they're addressed and this PR will be ready to merge!

[openshift-ci]

New changes are detected. LGTM label has been removed.

[eromanova97]

Thank you @skopacz1 the comments are addressed now 👍

[openshift-ci]

@eromanova97: all tests passed!

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

[skopacz1]

Changes LGTM, merging

[skopacz1]

/cherrypick enterprise-4.12

[skopacz1]

/cherrypick enterprise-4.13

[skopacz1]

/cherrypick enterprise-4.14

[skopacz1]

/cherrypick enterprise-4.15

[skopacz1]

/cherrypick enterprise-4.16

[openshift-cherrypick-robot]

@skopacz1: #75201 failed to apply on top of branch "enterprise-4.12":

Applying: OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap
Using index info to reconstruct a base tree...
A	modules/monitoring-adding-a-secret-to-the-alertmanager-configuration.adoc
M	modules/monitoring-assigning-tolerations-to-monitoring-components.adoc
M	modules/monitoring-attaching-additional-labels-to-your-time-series-and-alerts.adoc
M	modules/monitoring-configuring-a-local-persistent-volume-claim.adoc
M	modules/monitoring-configuring-external-alertmanagers.adoc
A	modules/monitoring-configuring-pod-topology-spread-constraints.adoc
M	modules/monitoring-configuring-remote-write-storage.adoc
M	modules/monitoring-configuring-the-monitoring-stack.adoc
M	modules/monitoring-creating-cluster-id-labels-for-metrics.adoc
M	modules/monitoring-enabling-a-separate-alertmanager-instance-for-user-defined-alert-routing.adoc
M	modules/monitoring-granting-users-permission-to-configure-alert-routing-for-user-defined-projects.adoc
M	modules/monitoring-investigating-why-user-defined-metrics-are-unavailable.adoc
M	modules/monitoring-modifying-retention-time-and-size-for-prometheus-metrics-data.adoc
M	modules/monitoring-modifying-the-retention-time-for-thanos-ruler-metrics-data.adoc
M	modules/monitoring-moving-monitoring-components-to-different-nodes.adoc
M	modules/monitoring-setting-log-levels-for-monitoring-components.adoc
M	modules/monitoring-setting-query-log-file-for-prometheus.adoc
M	modules/monitoring-setting-scrape-sample-and-label-limits-for-user-defined-projects.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/monitoring-setting-scrape-sample-and-label-limits-for-user-defined-projects.adoc
CONFLICT (content): Merge conflict in modules/monitoring-setting-scrape-sample-and-label-limits-for-user-defined-projects.adoc
Auto-merging modules/monitoring-setting-query-log-file-for-prometheus.adoc
CONFLICT (content): Merge conflict in modules/monitoring-setting-query-log-file-for-prometheus.adoc
Auto-merging modules/monitoring-setting-log-levels-for-monitoring-components.adoc
CONFLICT (content): Merge conflict in modules/monitoring-setting-log-levels-for-monitoring-components.adoc
Auto-merging modules/monitoring-moving-monitoring-components-to-different-nodes.adoc
CONFLICT (content): Merge conflict in modules/monitoring-moving-monitoring-components-to-different-nodes.adoc
Auto-merging modules/monitoring-modifying-the-retention-time-for-thanos-ruler-metrics-data.adoc
CONFLICT (content): Merge conflict in modules/monitoring-modifying-the-retention-time-for-thanos-ruler-metrics-data.adoc
Auto-merging modules/monitoring-modifying-retention-time-and-size-for-prometheus-metrics-data.adoc
CONFLICT (content): Merge conflict in modules/monitoring-modifying-retention-time-and-size-for-prometheus-metrics-data.adoc
Auto-merging modules/monitoring-investigating-why-user-defined-metrics-are-unavailable.adoc
Auto-merging modules/monitoring-granting-users-permission-to-configure-alert-routing-for-user-defined-projects.adoc
CONFLICT (content): Merge conflict in modules/monitoring-granting-users-permission-to-configure-alert-routing-for-user-defined-projects.adoc
Auto-merging modules/monitoring-enabling-a-separate-alertmanager-instance-for-user-defined-alert-routing.adoc
CONFLICT (content): Merge conflict in modules/monitoring-enabling-a-separate-alertmanager-instance-for-user-defined-alert-routing.adoc
Auto-merging modules/monitoring-creating-cluster-id-labels-for-metrics.adoc
CONFLICT (content): Merge conflict in modules/monitoring-creating-cluster-id-labels-for-metrics.adoc
Auto-merging modules/monitoring-configuring-the-monitoring-stack.adoc
CONFLICT (content): Merge conflict in modules/monitoring-configuring-the-monitoring-stack.adoc
Auto-merging modules/monitoring-configuring-remote-write-storage.adoc
CONFLICT (content): Merge conflict in modules/monitoring-configuring-remote-write-storage.adoc
CONFLICT (modify/delete): modules/monitoring-configuring-pod-topology-spread-constraints.adoc deleted in HEAD and modified in OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap. Version OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap of modules/monitoring-configuring-pod-topology-spread-constraints.adoc left in tree.
Auto-merging modules/monitoring-configuring-external-alertmanagers.adoc
CONFLICT (content): Merge conflict in modules/monitoring-configuring-external-alertmanagers.adoc
Auto-merging modules/monitoring-configuring-a-local-persistent-volume-claim.adoc
CONFLICT (content): Merge conflict in modules/monitoring-configuring-a-local-persistent-volume-claim.adoc
Auto-merging modules/monitoring-attaching-additional-labels-to-your-time-series-and-alerts.adoc
CONFLICT (content): Merge conflict in modules/monitoring-attaching-additional-labels-to-your-time-series-and-alerts.adoc
Auto-merging modules/monitoring-assigning-tolerations-to-monitoring-components.adoc
CONFLICT (content): Merge conflict in modules/monitoring-assigning-tolerations-to-monitoring-components.adoc
CONFLICT (modify/delete): modules/monitoring-adding-a-secret-to-the-alertmanager-configuration.adoc deleted in HEAD and modified in OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap. Version OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap of modules/monitoring-adding-a-secret-to-the-alertmanager-configuration.adoc left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick enterprise-4.12

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 kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@skopacz1: #75201 failed to apply on top of branch "enterprise-4.13":

Applying: OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap
Using index info to reconstruct a base tree...
A	modules/monitoring-configuring-pod-topology-spread-constraints.adoc
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): modules/monitoring-configuring-pod-topology-spread-constraints.adoc deleted in HEAD and modified in OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap. Version OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap of modules/monitoring-configuring-pod-topology-spread-constraints.adoc left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OBSDOCS-1011: Fix information about the user-workload-monitoring-config ConfigMap
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick enterprise-4.13

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 kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #75773

In response to this:

/cherrypick enterprise-4.14

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 kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #75774

In response to this:

/cherrypick enterprise-4.15

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 kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #75775

In response to this:

/cherrypick enterprise-4.16

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 kubernetes-sigs/prow repository.