openshift-docs
openshift-docs copied to clipboard
OBSDOCS-893 - Power Monitoring - Update OpenShift docs for accessing dashboards in Developer view
Change type: Doc update; Power Monitoring - Update OpenShift docs for accessing dashboards in Developer view Doc JIRA: https://issues.redhat.com/browse/OBSDOCS-893
Fix Version: 4.14+
Doc Preview: https://75659--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/power_monitoring/visualizing-power-monitoring-metrics.html#power-monitoring-accessing-dashboards-developer_visualizing-power-monitoring-metrics
SME Review: @vimalk78 QE Review: @vprashar2929 Peer Review:
🤖 Wed May 29 11:37:57 - Prow CI generated the docs preview:
https://75659--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/power_monitoring/visualizing-power-monitoring-metrics.html
Can we add in docs that in developer view only the namespaces visible to the developer will be visible in the powermon dashboard?
Can we add in docs that in developer view only the namespaces visible to the developer will be visible in the powermon dashboard?
@vimalk78 Added your comment as a NOTE.
Can we add in docs that in developer view only the namespaces visible to the developer will be visible in the powermon dashboard?
@vimalk78 Added your comment as a NOTE.
can we add with some examples, and screenshots
Can we add in docs that in developer view only the namespaces visible to the developer will be visible in the powermon dashboard?
@vimalk78 Added your comment as a NOTE.
can we add with some examples, and screenshots
@vimalk78 I would suggest not. A procedure module usually refers to the prerequisites, steps and, results. See https://docs.openshift.com/container-platform/4.14/observability/monitoring/reviewing-monitoring-dashboards.html#reviewing-monitoring-dashboards-developer_reviewing-monitoring-dashboards for reference.
/label peer-review-needed
/remove-label peer-review-needed
/label peer-review-in-progress
Hi @shreyasiddhartha . I've added two comments inline. Not necessarily show stoppers but clarify for the one option mentioned would be clear things up.
/remove-label peer-review-needed
/label peer-review-done
@dfitzmau: Those labels are not set on the issue: peer-review-needed
In response to this:
Hi @shreyasiddhartha . I've added two comments inline. Not necessarily show stoppers but clarify for the one option mentioned would be clear things up.
/remove-label peer-review-needed
/label peer-review-done
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.
/remove-label peer-review-in-progress
@shreyasiddhartha: 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.
/label merge-review-needed
LGTM. Thanks!
/lgtm
/cherrypick enterprise-4.14
/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
@mburke5678: new pull request created: #76646
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.
@mburke5678: new pull request created: #76647
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.
@mburke5678: new pull request created: #76648
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.