OBSDOCS-1612: Move the alertmanager configuration modules under a new…

[eromanova97]

Version(s): none for cherry-picking, monitoring-docs-restruce only

Issue: OBSDOCS-1612

Links to docs preview:

• Before you begin
• Configuring alerts and notifications for core platform monitoring
• Configuring alerts and notifications for user workload monitoring

QE review:

• QE has approved this change.

Additional information:
The changes it this PR are not yet user-facing.
This PR adds an existing content to about alert configurations to the new assembly.

The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

This PR also makes small changes to naming of procedures to mitigate the confusion about using multiple terms for the same configuration.

NOTE: The links and xrefs will be filled in in a different PR, because the content from other assemblies still needs to be moved to the new place, which means that if I filled the links now, I would have to keep repairing them later. So I am keeping that for a separate PR.

[openshift-ci-robot]

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

In response to this:

Version(s): none for cherry-picking, monitoring-docs-restruce` only

Issue: OBSDOCS-1612

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:
The changes it this PR are not yet user-facing.
This PR adds an existing content to about alert configurations to the new assembly.

The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

This PR also makes small changes to naming of procedure to mitigate the confusion about using multiple terms for the same configuration.

NOTE: The links and xrefs will be filled in in a different PR, because the content from other assemblies still needs to be moved to the new place, which means that if I filled the links now, I would have to keep repairing them later. So I am keeping that for a separate PR.

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 Jan 17 08:11:59 - Prow CI generated the docs preview:

https://86941--ocpdocs-pr.netlify.app/openshift-dedicated/latest/observability/monitoring/enabling-alert-routing-for-user-defined-projects.html
https://86941--ocpdocs-pr.netlify.app/openshift-dedicated/latest/observability/monitoring/managing-alerts.html
https://86941--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/common-monitoring-configuration-scenarios.html
https://86941--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/configuring-core-platform-monitoring/configuring-alerts-and-notifications.html
https://86941--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/configuring-user-workload-monitoring/before-you-begin-uwm.html
https://86941--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/configuring-user-workload-monitoring/configuring-alerts-and-notifications-uwm.html
https://86941--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/enabling-alert-routing-for-user-defined-projects.html
https://86941--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/monitoring/managing-alerts.html
https://86941--ocpdocs-pr.netlify.app/openshift-rosa/latest/observability/monitoring/enabling-alert-routing-for-user-defined-projects.html
https://86941--ocpdocs-pr.netlify.app/openshift-rosa/latest/observability/monitoring/managing-alerts.html

[openshift-ci-robot]

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

In response to this:

Version(s): none for cherry-picking, monitoring-docs-restruce` only

Issue: OBSDOCS-1612

Links to docs preview:

• Configuring alerts and notifications for core platform monitoring
• Configuring alerts and notifications for user workload monitoring

QE review:

• QE has approved this change.

Additional information:
The changes it this PR are not yet user-facing.
This PR adds an existing content to about alert configurations to the new assembly.

The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

This PR also makes small changes to naming of procedure to mitigate the confusion about using multiple terms for the same configuration.

NOTE: The links and xrefs will be filled in in a different PR, because the content from other assemblies still needs to be moved to the new place, which means that if I filled the links now, I would have to keep repairing them later. So I am keeping that for a separate PR.

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-1612 which is a valid jira issue.

In response to this:

Version(s): none for cherry-picking, monitoring-docs-restruce` only

Issue: OBSDOCS-1612

Links to docs preview:

• Before you begin
• Configuring alerts and notifications for core platform monitoring
• Configuring alerts and notifications for user workload monitoring

QE review:

• QE has approved this change.

Additional information:
The changes it this PR are not yet user-facing.
This PR adds an existing content to about alert configurations to the new assembly.

The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

This PR also makes small changes to naming of procedure to mitigate the confusion about using multiple terms for the same configuration.

NOTE: The links and xrefs will be filled in in a different PR, because the content from other assemblies still needs to be moved to the new place, which means that if I filled the links now, I would have to keep repairing them later. So I am keeping that for a separate PR.

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-1612 which is a valid jira issue.

In response to this:

Version(s): none for cherry-picking, monitoring-docs-restruce` only

Issue: OBSDOCS-1612

Links to docs preview:

• Before you begin
• Configuring alerts and notifications for core platform monitoring
• Configuring alerts and notifications for user workload monitoring

QE review:

• QE has approved this change.

Additional information:
The changes it this PR are not yet user-facing.
This PR adds an existing content to about alert configurations to the new assembly.

The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

This PR also makes small changes to naming of procedures to mitigate the confusion about using multiple terms for the same configuration.

NOTE: The links and xrefs will be filled in in a different PR, because the content from other assemblies still needs to be moved to the new place, which means that if I filled the links now, I would have to keep repairing them later. So I am keeping that for a separate PR.

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-1612 which is a valid jira issue.

In response to this:

Version(s): none for cherry-picking, monitoring-docs-restruce only

Issue: OBSDOCS-1612

Links to docs preview:

• Before you begin
• Configuring alerts and notifications for core platform monitoring
• Configuring alerts and notifications for user workload monitoring

QE review:

• QE has approved this change.

Additional information:
The changes it this PR are not yet user-facing.
This PR adds an existing content to about alert configurations to the new assembly.

The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

This PR also makes small changes to naming of procedures to mitigate the confusion about using multiple terms for the same configuration.

NOTE: The links and xrefs will be filled in in a different PR, because the content from other assemblies still needs to be moved to the new place, which means that if I filled the links now, I would have to keep repairing them later. So I am keeping that for a separate PR.

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]

/lgtm

[eromanova97]

/label peer-review-needed

[openshift-ci-robot]

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

In response to this:

Version(s): none for cherry-picking, monitoring-docs-restruce only

Issue: OBSDOCS-1612

Links to docs preview:

• Before you begin
• Configuring alerts and notifications for core platform monitoring
• Configuring alerts and notifications for user workload monitoring

QE review:

• QE has approved this change.

Additional information:
The changes it this PR are not yet user-facing.
This PR adds an existing content to about alert configurations to the new assembly.

The content in the original assembly is still there . The reason is to not lose any content while moving it around. There will be a separate issue that will make sure that all the content is transfered as needed.

Therefore, the main thing to check in this PR is to see if the structure in the linked chapters looks good and renders without issues.

This PR also makes small changes to naming of procedures to mitigate the confusion about using multiple terms for the same configuration.

NOTE: The links and xrefs will be filled in in a different PR, because the content from other assemblies still needs to be moved to the new place, which means that if I filled the links now, I would have to keep repairing them later. So I am keeping that for a separate PR.

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]

/remove-label peer-review-needed

[eromanova97]

/label peer-review-needed

[xenolinux]

A few comments; otherwise LGTM

[openshift-ci]

New changes are detected. LGTM label has been removed.

[eromanova97]

/label merge-review-needed

[jeana-redhat]

This is looking good! I found a couple tiny changes to make, and was thinking about the "before you begin" titles, but that last one is out of scope here and just for your consideration as you work on this.

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

[jeana-redhat]

Musing on structure...

So, I like the idea of "before you begin" but I am not sure if it's right as the assembly title. It makes sense to me as an introduction in that section, but right now we have a page called "before you begin" that includes a bunch of actual procedures under it. It also shows in the left nav as "before you begin" - not sure a user would expect to see so many procedures when they click that in the nav.

Does it make sense to call this assembly something elese and bump the "before you begin" content into a first subsection? Maybe something about "preparing", which would imply the need to read it first but also match expectations of a lot of procedural work?

NB: it is also very possible I am just misunderstanding :)

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