OBSDOCS-65: update-monitoring-troubleshooting-sample-code

[bburt-rh]

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OBSDOCS-65

Link to docs preview: https://74236--ocpdocs-pr.netlify.app/openshift-enterprise/latest/monitoring/troubleshooting-monitoring-issues.html#determining-why-prometheus-is-consuming-disk-space_troubleshooting-monitoring-issues

QE review:

• QE has approved this change.

Additional information:
Updates the monitoring troubleshooting content to replace and update sample code and to bring the formatting of the CLI commands into compliance with the OCP docs guidelines.

[openshift-ci-robot]

@bburt-rh: This pull request references OBSDOCS-65 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 "4.16.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OBSDOCS-65

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:
Updates the monitoring troubleshooting content to replace and update sample code and to bring the formatting of the CLI commands into compliance with the OCP docs guidelines.

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.

[bburt-rh]

/retest

[ocpdocs-previewbot]

🤖 Thu Apr 04 20:02:10 - Prow CI generated the docs preview:

https://74236--ocpdocs-pr.netlify.app/
https://74236--ocpdocs-pr.netlify.app/openshift-dedicated/latest/monitoring/troubleshooting-monitoring-issues.html
https://74236--ocpdocs-pr.netlify.app/openshift-enterprise/latest/monitoring/troubleshooting-monitoring-issues.html
https://74236--ocpdocs-pr.netlify.app/openshift-rosa/latest/monitoring/troubleshooting-monitoring-issues.html

[openshift-ci-robot]

@bburt-rh: This pull request references OBSDOCS-65 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 "4.16.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OBSDOCS-65

Link to docs preview: https://74236--ocpdocs-pr.netlify.app/openshift-enterprise/latest/monitoring/troubleshooting-monitoring-issues.html#determining-why-prometheus-is-consuming-disk-space_troubleshooting-monitoring-issues

QE review:

• QE has approved this change.

Additional information:
Updates the monitoring troubleshooting content to replace and update sample code and to bring the formatting of the CLI commands into compliance with the OCP docs guidelines.

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]

@bburt-rh: all tests passed!

Full PR test history. Your PR dashboard.

Details

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/test-infra repository. I understand the commands that are listed here.

[juzhao]

/lgtm

[openshift-ci-robot]

@bburt-rh: This pull request references OBSDOCS-65 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 "4.16.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OBSDOCS-65

Link to docs preview: https://74236--ocpdocs-pr.netlify.app/openshift-enterprise/latest/monitoring/troubleshooting-monitoring-issues.html#determining-why-prometheus-is-consuming-disk-space_troubleshooting-monitoring-issues

QE review:

• QE has approved this change.

Additional information:
Updates the monitoring troubleshooting content to replace and update sample code and to bring the formatting of the CLI commands into compliance with the OCP docs guidelines.

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.

[tmalove]

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

[tmalove]

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

[bburt-rh]

/cherrypick enterprise-4.12

[bburt-rh]

/cherrypick enterprise-4.13

[bburt-rh]

/cherrypick enterprise-4.14

[bburt-rh]

/cherrypick enterprise-4.15

[bburt-rh]

/cherrypick enterprise-4.16

[openshift-cherrypick-robot]

@bburt-rh: #74236 failed to apply on top of branch "enterprise-4.12":

Applying: OBSDOCS-65-update-monitoring-troubleshooting-sample-code
Using index info to reconstruct a base tree...
M	modules/monitoring-determining-why-prometheus-is-consuming-disk-space.adoc
M	monitoring/troubleshooting-monitoring-issues.adoc
Falling back to patching base and 3-way merge...
Auto-merging monitoring/troubleshooting-monitoring-issues.adoc
CONFLICT (content): Merge conflict in monitoring/troubleshooting-monitoring-issues.adoc
Auto-merging modules/monitoring-determining-why-prometheus-is-consuming-disk-space.adoc
CONFLICT (content): Merge conflict in modules/monitoring-determining-why-prometheus-is-consuming-disk-space.adoc
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-65-update-monitoring-troubleshooting-sample-code
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".

Details

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/test-infra repository.

[openshift-cherrypick-robot]

@bburt-rh: new pull request created: #74359

Details

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/test-infra repository.

[openshift-cherrypick-robot]

@bburt-rh: new pull request created: #74360

Details

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/test-infra repository.

[openshift-cherrypick-robot]

@bburt-rh: new pull request created: #74361

Details

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/test-infra repository.

[openshift-cherrypick-robot]

@bburt-rh: new pull request created: #74362

Details

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/test-infra repository.

[openshift-cherrypick-robot]

@bburt-rh: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.16 from head openshift-cherrypick-robot:cherry-pick-74236-to-enterprise-4.16: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-74236-to-enterprise-4.16."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

Details

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/test-infra repository.

[openshift-cherrypick-robot]

@bburt-rh: #74236 failed to apply on top of branch "enterprise-4.12":

Applying: OBSDOCS-65-update-monitoring-troubleshooting-sample-code
Using index info to reconstruct a base tree...
M	modules/monitoring-determining-why-prometheus-is-consuming-disk-space.adoc
M	monitoring/troubleshooting-monitoring-issues.adoc
Falling back to patching base and 3-way merge...
Auto-merging monitoring/troubleshooting-monitoring-issues.adoc
CONFLICT (content): Merge conflict in monitoring/troubleshooting-monitoring-issues.adoc
Auto-merging modules/monitoring-determining-why-prometheus-is-consuming-disk-space.adoc
CONFLICT (content): Merge conflict in modules/monitoring-determining-why-prometheus-is-consuming-disk-space.adoc
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-65-update-monitoring-troubleshooting-sample-code
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".

Details

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/test-infra repository.

[openshift-cherrypick-robot]

@bburt-rh: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.13 from head openshift-cherrypick-robot:cherry-pick-74236-to-enterprise-4.13: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-74236-to-enterprise-4.13."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

Details

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/test-infra repository.

[openshift-cherrypick-robot]

@bburt-rh: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.14 from head openshift-cherrypick-robot:cherry-pick-74236-to-enterprise-4.14: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-74236-to-enterprise-4.14."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

Details

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/test-infra repository.

[openshift-cherrypick-robot]

@bburt-rh: new pull request could not be created: failed to create pull request against openshift/openshift-docs#enterprise-4.15 from head openshift-cherrypick-robot:cherry-pick-74236-to-enterprise-4.15: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-74236-to-enterprise-4.15."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

Details

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/test-infra repository.