OBSDOCS-1603: Add assemblies to the 'Getting started' section

[eromanova97]

Version: none for cherry-picking, monitoring-docs-restructure only
QE review:

• QE has approved this change.

Docs preview:

• Core platform monitoring first steps
• User workload monitoring first steps
• Developer and non-administrator steps

Additional information:
The changes in the PR are not yet user-facing

This PR moves content from old assebly to the new ones. 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.

You can see the original assembly here: Common monitoring configuration scenarios

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.

[openshift-ci-robot]

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

In response to this:

Version: none for cherry-picking, monitoring-docs-restructure only
QE review:

• QE has approved this change.

Docs preview:

Additional information:
The changes in the PR are not yet user-facing

This PR moves content from old assebly to the new ones. 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.

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 24 09:48:33 - Prow CI generated the docs preview:
https://87498--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

[openshift-ci-robot]

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

In response to this:

Version: none for cherry-picking, monitoring-docs-restructure only
QE review:

• QE has approved this change.

Docs preview:

• Core platform monitoring first steps
• User workload monitoring first steps
• Developer and non-administrator steps

Additional information:
The changes in the PR are not yet user-facing

This PR moves content from old assebly to the new ones. 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.

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

[openshift-ci-robot]

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

In response to this:

Version: none for cherry-picking, monitoring-docs-restructure only
QE review:

• QE has approved this change.

Docs preview:

• Core platform monitoring first steps
• User workload monitoring first steps
• Developer and non-administrator steps

Additional information:
The changes in the PR are not yet user-facing

This PR moves content from old assebly to the new ones. 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.

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

[openshift-ci-robot]

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

In response to this:

Version: none for cherry-picking, monitoring-docs-restructure only
QE review:

• QE has approved this change.

Docs preview:

• Core platform monitoring first steps
• User workload monitoring first steps
• Developer and non-administrator steps

You can see the original assembly here: Common monitoring configuration scenarios

Additional information:
The changes in the PR are not yet user-facing

This PR moves content from old assebly to the new ones. 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.

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

In response to this:

Version: none for cherry-picking, monitoring-docs-restructure only
QE review:

• QE has approved this change.

Docs preview:

• Core platform monitoring first steps
• User workload monitoring first steps
• Developer and non-administrator steps

Additional information:
The changes in the PR are not yet user-facing

This PR moves content from old assebly to the new ones. 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.

You can see the original assembly here: Common monitoring configuration scenarios

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.

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.

[lahinson]

Nice work! I checked the structure and links, and I left a couple of minor suggestions for your consideration.

[openshift-ci]

New changes are detected. LGTM label has been removed.

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

[eromanova97]

/label merge-review-needed