docs: move Prysm into Observability & Audit subsection

- Move prysm.md into cloud-storage/observability/ so it sits alongside
  Prometheus and Perses as part of the unified observability story
- Rename the observability section to "Observability & Audit" to reflect
  Prysm's audit and compliance capabilities (log analysis, access audit)
- Update observability/index.md: add Prysm to the stack table, add Audit
  to the key metrics list, fix See Also links
- Update cloud-storage/index.md: remove standalone Prysm row, update
  component table, data flow diagram, and See Also links accordingly
- Fix prysm.md internal link: ceph.md path updated for new folder depth

Author: senolcolak

docs/architecture/cloud-storage/index.md

@@ -14,7 +14,7 @@ The storage stack is organized into three layers:
 
 **Operations** — [Rook](./rook.md) runs as a Kubernetes operator and manages the full lifecycle of Ceph daemons (monitors, managers, OSDs, MDS, RGW) as containerized workloads. [Arbiter](./arbiter.md) extends quorum into stretched cluster topologies by deploying external Ceph monitors that Rook does not manage directly.
 
-**Data Services** — [Chorus](./chorus.md) provides zero-downtime data replication and migration between object storage systems (S3 and Swift). [Liquid-Ceph](./liquid-ceph.md) enables dynamic, on-demand storage allocation across the cluster. [Prysm](./prysm.md) delivers a CLI-based observability layer over Ceph clusters and RGW deployments.
+**Data Services** — [Chorus](./chorus.md) provides zero-downtime data replication and migration between object storage systems (S3 and Swift). [Liquid-Ceph](./liquid-ceph.md) enables dynamic, on-demand storage allocation across the cluster.
 
 ## Components
 
@@ -25,8 +25,7 @@ The storage stack is organized into three layers:
 | [Arbiter](./arbiter.md) | Operations | External Ceph monitors for quorum in stretched clusters |
 | [Chorus](./chorus.md) | Data Services | Zero-downtime object storage replication and migration |
 | [Liquid-Ceph](./liquid-ceph.md) | Data Services | Dynamic storage allocation across the Ceph cluster |
-| [Prysm](./prysm.md) | Data Services | Observability CLI for Ceph clusters and RGW |
-| [Observability](./observability/) | Observability | Metrics, dashboards, and alerting for the storage stack |
+| [Observability & Audit](./observability/) | Observability | Metrics, dashboards, alerting, and audit — Prometheus, Perses, Prysm |
 
 ## Storage Interfaces
 
@@ -58,9 +57,10 @@ Applications / VMs
    └───────────┘   └─────────┘   └────────────┘
    (quorum)        (replication)  (allocation)
         │
-   ┌────┴──────┐
-   │   Prysm   │  ← observability CLI
-   └───────────┘
+   ┌────┴──────────────────────────┐
+   │  Observability & Audit        │
+   │  Prometheus · Perses · Prysm  │
+   └───────────────────────────────┘
 ```
 
 ## High Availability
@@ -69,6 +69,6 @@ Ceph achieves HA through monitor quorum (typically 3 or 5 monitors), OSD replica
 
 ## See Also
 
-- [Observability](./observability/) — Prometheus metrics and Perses dashboards for the storage stack
+- [Observability & Audit](./observability/) — Prometheus metrics, Perses dashboards, and Prysm CLI for the storage stack
 - [Ceph upstream architecture docs](https://docs.ceph.com/en/latest/architecture/)
 - [Rook documentation](https://rook.io/docs/rook/latest-release/Getting-Started/intro/)

docs/architecture/cloud-storage/observability/index.md

@@ -1,17 +1,18 @@
 ---
-title: Overview
+title: Observability & Audit
 ---
 
-# Observability Overview
+# Observability & Audit Overview
 
-CobaltCore monitors the cloud storage stack through a combination of Prometheus-based metrics collection and Perses dashboards. Together they provide real-time visibility into Ceph cluster health, OSD performance, RGW throughput, and storage capacity trends.
+CobaltCore monitors the cloud storage stack through a combination of Prometheus-based metrics collection, Perses dashboards, and the Prysm observability CLI. Together they provide real-time visibility into Ceph cluster health, OSD performance, RGW throughput, storage capacity trends, and audit compliance.
 
 ## Stack
 
 | Component | Role |
 |-----------|------|
 | [Prometheus](./prometheus.md) | Scrapes and stores time-series metrics from Ceph, Rook, and RGW exporters |
 | [Perses](./perses.md) | Dashboard platform for visualizing storage metrics and defining alerts |
+| [Prysm](./prysm.md) | CLI-based observability tool for Ceph clusters and RGW — real-time monitoring, SMART disk health, log compliance |
 
 ## Key Metrics
 
@@ -23,6 +24,7 @@ The following signal categories are covered by the observability stack:
 - **RGW** — request rates, error rates, bandwidth per bucket and user
 - **Replication** — Chorus replication lag, sync success/failure rates
 - **Availability** — Arbiter monitor reachability, MDS active/standby state
+- **Audit** — log compliance analysis and access audit via Prysm consumers
 
 ## Alerting
 
@@ -32,4 +34,4 @@ Alerts are defined as Prometheus rules and surfaced through the CobaltCore alert
 
 - [Prometheus](./prometheus.md)
 - [Perses](./perses.md)
-- [Prysm](../prysm.md) — CLI-based observability for Ceph and RGW
+- [Prysm](./prysm.md)

docs/architecture/cloud-storage/prysm.md …ure/cloud-storage/observability/prysm.mddocs/architecture/cloud-storage/prysm.md renamed to docs/architecture/cloud-storage/observability/prysm.md docs/architecture/cloud-storage/prysm.md renamed to docs/architecture/cloud-storage/observability/prysm.md

@@ -5,7 +5,7 @@ title: Prysm
 # Prysm 
 
 Prysm is a comprehensive observability CLI tool developed by CobaltCore for
-monitoring [Ceph](./ceph.md) storage clusters and RADOS Gateway (RGW)
+monitoring [Ceph](../ceph.md) storage clusters and RADOS Gateway (RGW)
 deployments. Prysm provides a multi-layered architecture designed to deliver
 real-time monitoring, data collection, and analysis across Ceph environments.