OBSDOCS-3312: Restore restructured format for configuring-the-log-store.adoc

[johnwilkins]

Summary

Fix inadvertent reversion of OBSDOCS-3312 restructuring that occurred in OBSDOCS-3539 (PR #113999).

Problem

OBSDOCS-3539 added filtering documentation on 2026-07-13, but also inadvertently reverted the OBSDOCS-3312/OBSDOCS-3551 restructuring of configuring/configuring-the-log-store.adoc. The file was changed from the simplified 6.6 format back to the pre-restructuring format with embedded sizing/storage includes.

This created an inconsistency where:

• standalone-logging-docs-6.6 has the correct restructured format ✅
• standalone-logging-docs-main had the old pre-restructuring format ❌

Solution

Restore the simplified format to match 6.6 structure:

• Remove sizing/storage includes (they live in installing/ assemblies)
• Add NOTE block pointing users to deployment sizing and storage configuration docs
• Fix STS section leveloffset from +3 to +2
• Add [role="_abstract"] to abstract paragraph

Structure after this fix

• Sizing content: installing/loki-deployment-sizing.adoc
• Storage configuration: installing/configuring-storage-for-lokistack.adoc
• This file: Simplified with NOTE pointing to above docs

Testing

Compared resulting structure with upstream/standalone-logging-docs-6.6 to ensure consistency.

Related

• Original restructuring: OBSDOCS-3312 (May 2026)
• Inadvertent reversion: OBSDOCS-3539 / PR OBSDOCS-3539: Add use case guidance and examples for log filtering #113999 (July 13, 2026)
• 6.6 cherry-pick of OBSDOCS-3539: PR OBSDOCS-3539: Add use case guidance and examples for log filtering #116488 (maintained correct structure)

Note

This PR should NOT be cherry-picked to 6.6 since 6.6 already has the correct structure.

[openshift-ci-robot]

@johnwilkins: This pull request references OBSDOCS-3312 which is a valid jira issue.

Details

In response to this:

Summary

Fix inadvertent reversion of OBSDOCS-3312 restructuring that occurred in OBSDOCS-3539 (PR #113999).

Problem

OBSDOCS-3539 added filtering documentation on 2026-07-13, but also inadvertently reverted the OBSDOCS-3312/OBSDOCS-3551 restructuring of configuring/configuring-the-log-store.adoc. The file was changed from the simplified 6.6 format back to the pre-restructuring format with embedded sizing/storage includes.

This created an inconsistency where:

• standalone-logging-docs-6.6 has the correct restructured format ✅
• standalone-logging-docs-main had the old pre-restructuring format ❌

Solution

Restore the simplified format to match 6.6 structure:

• Remove sizing/storage includes (they live in installing/ assemblies)
• Add NOTE block pointing users to deployment sizing and storage configuration docs
• Fix STS section leveloffset from +3 to +2
• Add [role="_abstract"] to abstract paragraph

Structure after this fix

• Sizing content: installing/loki-deployment-sizing.adoc
• Storage configuration: installing/configuring-storage-for-lokistack.adoc
• This file: Simplified with NOTE pointing to above docs

Testing

Compared resulting structure with upstream/standalone-logging-docs-6.6 to ensure consistency.

Related

• Original restructuring: OBSDOCS-3312 (May 2026)
• Inadvertent reversion: OBSDOCS-3539 / PR OBSDOCS-3539: Add use case guidance and examples for log filtering #113999 (July 13, 2026)
• 6.6 cherry-pick of OBSDOCS-3539: PR OBSDOCS-3539: Add use case guidance and examples for log filtering #116488 (maintained correct structure)

Note

This PR should NOT be cherry-picked to 6.6 since 6.6 already has the correct structure.

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]

🤖 Mon Jul 27 15:44:33 - Prow CI generated the docs preview:

https://116489--ocpdocs-pr.netlify.app/openshift-logging/latest/configuring/configuring-the-log-store.html

[openshift-ci]

@johnwilkins: 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-sigs/prow repository. I understand the commands that are listed here.