The Observability docs team is taking a number of steps to redirect Observability components to their own standalone docs pages
Phase 2: Create a landing page/splash page for Observability
Perform the following tasks in the OCP GitHub repo:
- Create an observability folder
- Nest the monitoring, logging, and tracing folders under the Observability folder
- Include other necessary files, folders, and symlinksÂ
- Create and store an index.adoc file containing Observability Overview content
- Create and store a new distro_map.yaml file for openshift-observability
- Create and store a topic map for observability-docs
- Update the OCP topic map to create an anchor for Observability
- Create a new branch for each Observability component that currently follows its own release cadence (e.g. Logging, Distributed Tracing, Network Observability)
Perform the following tasks in the OCP Layered Products GitLab repo:Â
- Add the project to the sync.yaml file
Perform the following tasks in Pantheon:
- Create a doc splash page for Observability
- Create a doc splash page for each Observability component per the brand-approved naming scheme
- depends on
-
OBSDOCS-686 Phase 1: Unify Observability Docs
- Closed
- is related to
-
OBSDA-953 Update Observability documentation - align with Observability strategy and changes on docs.openshift.com
- New