OBSDOCS-1472: Prepare Enabling monitoring for user-defined projects f…

[eromanova97]

Version(s) for cherry-picking: none

Issue: OBSDOCS-1472

Link to docs preview: no preview necessary

QE review:

• QE has approved this change.

Additional information:

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1472 which is a valid jira issue.

In response to this:

Version(s) for cherry-picking: none

Issue: OBSDOCS-1472

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]

🤖 Thu Nov 07 08:54:43 - Prow CI generated the docs preview:

https://84580--ocpdocs-pr.netlify.app/
https://84580--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/enabling-monitoring-for-user-defined-projects.html

[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.

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1472 which is a valid jira issue.

In response to this:

Version(s) for cherry-picking: none

Issue: OBSDOCS-1472

Link to docs preview: no preview necessary

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]

https://84580--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/enabling-monitoring-for-user-defined-projects.html
there are two same headers Enabling monitoring for user-defined projects, I think we could remove the second one, WDYT?

found it's the same for 4.17 released doc: https://docs.openshift.com/container-platform/4.17/observability/monitoring/enabling-monitoring-for-user-defined-projects.html

[eromanova97]

https://84580--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/enabling-monitoring-for-user-defined-projects.html there are two same headers Enabling monitoring for user-defined projects, I think we could remove the second one, WDYT?

found it's the same for 4.17 released doc: https://docs.openshift.com/container-platform/4.17/observability/monitoring/enabling-monitoring-for-user-defined-projects.html

@juzhao Oh yes, I actually don't like it either. The problem here is that the first one is the name of the whole file while the second one is the name of the actual procedure involved. Both titles must be there due to our doc rules and the way they are structured.

So the only thing that can be done here is to rename them. The procedure being called "Enabling monitoring for user-defined projects" makes sense. However, the whole chapter being called the same makes sense as well.
Honestly, I could not come up with the possible replacement title 😓

It is not wrong to have it as it is currently, but if you have any ideas, let me know

[juzhao]

https://84580--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/enabling-monitoring-for-user-defined-projects.html there are two same headers Enabling monitoring for user-defined projects, I think we could remove the second one, WDYT?
found it's the same for 4.17 released doc: https://docs.openshift.com/container-platform/4.17/observability/monitoring/enabling-monitoring-for-user-defined-projects.html

@juzhao Oh yes, I actually don't like it either. The problem here is that the first one is the name of the whole file while the second one is the name of the actual procedure involved. Both titles must be there due to our doc rules and the way they are structured.

So the only thing that can be done here is to rename them. The procedure being called "Enabling monitoring for user-defined projects" makes sense. However, the whole chapter being called the same makes sense as well. Honestly, I could not come up with the possible replacement title 😓

It is not wrong to have it as it is currently, but if you have any ideas, let me know

keep it is fine, maybe others have an idea for it.
/lgtm

[eromanova97]

/label peer-review-needed

[openshift-ci-robot]

@eromanova97: This pull request references OBSDOCS-1472 which is a valid jira issue.

In response to this:

Version(s) for cherry-picking: none

Issue: OBSDOCS-1472

Link to docs preview: no preview necessary

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.

[skopacz1]

LGTM

[eromanova97]

/label merge-review-needed

[maxwelldb]

Seems fine to me. @eromanova97 Can you confirm the merge target for this?

[eromanova97]

Hello @maxwelldb it only goes to the branch against which it is raised (monitoring-docs-restructure) so it needs no chery-picking, just merging. Thank you!