# Native Observability Dashboard

## Overview

The **Native Observability Dashboard** provides a lightweight observability interface directly inside Drupal.
Its goal is to give developers and administrators a **clear and immediate view of runtime request behavior** without
relying on external monitoring tools.

Instead of requiring a full external observability stack, this module leverages the telemetry collected by the **Native
Observability ecosystem** to expose key operational insights directly within the Drupal administration interface.

The dashboard is designed to provide a **quick situational overview** of the application state, helping developers
understand how the system is behaving in real time.

---

## Vision

Modern applications rely heavily on observability tools to understand performance, detect failures, and monitor system
health.

The vision of this module is to bring **core observability insights natively into Drupal**, offering:

* immediate visibility of request activity
* lightweight performance diagnostics
* developer-friendly runtime metrics
* a clear overview of system health

The dashboard acts as a **first-level operational view**, allowing administrators and developers to quickly understand
if the system is behaving as expected.

---

## Current Capabilities

The dashboard currently provides a **Primary KPIs section**, summarizing the most important runtime metrics collected
from request traces.

These metrics include:

* **Requests**
  Total number of processed requests within the selected time range.

* **Average Response Time**
  The average duration of all recorded requests.

* **P95 Latency**
  The 95th percentile response time, highlighting slow requests.

* **Error Rate**
  The percentage of requests that resulted in server errors.

Each metric includes a small visual sparkline that helps visualize the trend over time.

This allows administrators to quickly understand:

* if request volume is increasing
* if latency spikes are occurring
* if errors are affecting the system

All metrics are computed from the trace data stored by the **Native Observability core modules**.

---

## Purpose of the Dashboard

The dashboard is not intended to replace full observability platforms.

Instead, it serves as a **fast operational overview**, giving developers and administrators a quick snapshot of the
system state with a single glance.

This makes it particularly useful for:

* debugging runtime issues
* verifying deployment stability
* understanding request behavior
* quickly spotting anomalies

---

## Future Direction

The current implementation focuses on the initial request overview.
Future improvements will expand the dashboard with additional observability insights, including:

* deeper request performance analysis
* advanced latency metrics
* execution tracing insights
* richer visual analytics
* extended filtering and time range controls

The long-term goal is to provide a **native observability experience directly within Drupal**, reducing the friction
between application development and runtime diagnostics.

---

## Status

🚧 **Work in progress**

The dashboard is currently evolving as part of the broader **Native Observability project**.
