diff --git a/docs/Data-insights/Features/Explore-servers.md b/docs/Data-insights/Features/Explore-servers.md
index 7b890a9..4187269 100644
--- a/docs/Data-insights/Features/Explore-servers.md
+++ b/docs/Data-insights/Features/Explore-servers.md
@@ -1,502 +1,7 @@
# Servers
+The Servers view provides a visual overview of all monitored servers, enabling quick identification of performance issues, health states, and environment status across your entire fleet.
-The Servers Overview, accessible under the **Explore** tab, provides a visual and intuitive representation of all monitored servers across various environments. This dashboard is designed to enable quick identification of performance issues, health states, and environment status at a glance.
-
-
-
-
-## Key features
-
-- **Quick status check**: Visually assess the health and performance of your server fleet without needing to drill down into individual metrics.
-
-- **Environment segregation**: Servers are grouped by environment (e.g.,`canary`, `stg_staging`, `prod`), allowing for easy filtering and environment-specific health checks.
-
-- **Immediate issue identification**: Color-coding and visual states quickly draw attention to servers or groups experiencing issues.
-
-### Component breakdown
-
-This table describes the key elements you'll see on the **Overview** dashboard.
-
-| **Component** | **Description** |
-|----------------|-----------------|
-| **Filter Bar (Group, All)** | Use this bar to filter the displayed server cubes based on server groups. |
-| **System Overview** | The main area where all monitored servers or server groups are displayed as 3D cube icons. |
-| **Server Cube Icon** | Each cube represents an individual server or a cluster/group of servers (e.g., `group: canary`). |
-| **Cube Labeling** | Provides the Group/Environment name (top line) and the **instance name** on the bottom line for clear identification. |
-| **Live Toggle** | Indicates if the view is displaying real-time data updates. |
-| **Quick Nav** | A dropdown menu that provides immediate, centralized access to the main areas of the platform from any screen. |
-
-
-## Visual indicators
-
-The visual elements attached to each cube are the most critical tools for rapid assessment.
-
-
-### Color codes (Health status)
-
-The main color of the server cube or an indicator light changes to signal overall health or alert level.
-
-| **Color** | **Indication** | **Notes** |
-|------------|----------------|------------|
-| 🟦 **Blue** | Healthy / Optimal | All key metrics are within normal operating thresholds. |
-| 🟧 **Orange** | Warning / Elevated Risk | One or more metrics (e.g., CPU, Memory) are approaching their critical threshold. Action may be required. |
-| 🟥 **Red** | Critical / Alert | One or more key metrics have exceeded the critical threshold, potentially impacting service availability or performance. Immediate action is required. |
-
-
-
-### Metric bars (M, C, R, D)
-
-Small indicator bars displayed on the cube provide instantaneous utilization and performance data. The color intensity or fill level of each bar shows the current load or alert status for that specific metric.
-
-| **Metric bar** | **Meaning** | **What it Measures** |
-|-----------------|-----------------------------------------------|----------------------|
-| **M** | **Memory** Usage | Current usage of heap and non-heap memory. |
-| **C** | **CPU** Load | Current processor utilization. |
-| **R** | Web **Request** count | The rate of incoming requests or the average time taken to process a request. |
-| **D** | App **Database** Throughput Count | Monitors the number of database operations/queries handled by the application per unit time.
-
-## Quick Nav
-
-The Quick Nav is a dropdown menu providing immediate, centralized access to the most frequently used views - **Home, Overview, Applications, Servers, and Configuration**.
-
-
-
-
-## Server Details
-
-
-When you click on a Server cube from the System Overview dashboard, you'll be taken to a detailed management and monitoring view for that specific instance.
-
-This detailed view is organized into top-level tabs that provide comprehensive diagnostics and monitoring capabilities:
-
-- **UI Tunnel** - Access your on-premises application's user interface directly through FusionReactor Cloud.
-
-- **Metrics** - Performance metrics and resource utilization data.
-
-- **Traces** - Deep-dive request tracing for diagnostics.
-
-- **Logs** - Application and system log analysis.
-
-- **Info** - Client and server configuration information.
-
-Each tab provides specialized tools for monitoring and troubleshooting your FusionReactor agent instance.
-
-
-
-## UI Tunnel
-
-The **UI Tunnel** in FusionReactor is a specialized feature that enables secure remote access to the detailed, local user interface (UI) of an on-premises FusionReactor Agent through the FusionReactor Cloud platform. You can also filter the UI Tunnel view by **job** to focus on specific tasks or workloads.
-
-
-
-
-### Changing the UI theme (Dark/Light Mode)
-
-
-The **UI Tunnel** defaults to light mode but can be changed to dark mode for optimal viewing during extended monitoring sessions. You can easily switch between dark and light themes using the theme toggle (sun or moon) in the header bar.
-
-
-
-
-## Metrics
-
-
-The **Metrics** tab provides an historic view of your server’s performance and health. Data updates automatically if an auto-refresh interval is set, or manually when a new time range is selected.
-
-
-
-The boxes at the top display the latest collected performance metrics for the selected instance, based on the selected time range.
-
-| **Metric** | **Description** | **Why It’s Useful** |
-| ---------------------------------- | --------------------------------------------------------- | -------------------------------------------------------------- |
-| **Process CPU Usage** | Percentage of CPU used by this specific process. | Detects CPU-intensive applications or bottlenecks. |
-| **System CPU Usage** | Overall CPU usage across the system. | Helps identify if the host system is under load. |
-| **Memory Heap Usage** | Amount of heap memory currently in use. | Useful for monitoring memory leaks or high memory consumption. |
-| **GC Collection Time** | Time spent performing garbage collection. | High values may indicate inefficient memory management. |
-| **Web Request Duration** | Average time to complete a web request. | Reveals latency or slow response trends. |
-| **Web Request Throughput** | Number of requests handled per minute. | Shows traffic volume and server load. |
-| **Database Throughput** | Number of database operations per minute. | Helps track query load and database responsiveness. |
-| **Error Count / 4xx / 5xx Errors** | Number of failed or client/server-side errors per minute. | Quickly highlights failing transactions or service issues. |
-
-!!! note
- Panels refresh automatically if an auto-refresh interval is set using the top icon. Otherwise, they update when a new time range is selected.
-
-### Detailed graphs
-
-
-Each graph provides **historical trends** for the metrics shown below.
-
-
-
-You can:
-
-* **Zoom in or out** on a time range to analyze spikes or anomalies.
-* **Hover over data points** to see exact metric values.
-* **Compare multiple metrics** to find correlations (e.g., CPU spikes vs. increased error count).
-
-Graphs include:
-
-* CPU and Memory trends
-* Garbage Collection behavior
-* Request and error rates
-* Database and trace throughput
-
-This helps with **root-cause analysis** - understanding what led to a performance change or incident.
-
-
-### Metric graph actions
-
-
-
-The top-right corner of each metric graph contains action icons that may vary depending on the dashboard and metric type:
-
-1. **Edit Threshold** - Configure alert thresholds for this metric to receive notifications when values exceed defined limits (available on select dashboards).
-
-2. **View Logs** - Access related log entries for the time period and service shown in the graph to investigate issues.
-
-3. **Ask OpsPilot** - Send this metric to OpsPilot AI for natural language explanations and analysis of patterns or anomalies.
-
-4. **Expand Graph** - Open the metric in full-screen view for detailed analysis and extended time ranges.
-
-These actions provide quick access to troubleshooting and monitoring capabilities directly from the metric visualization. Note that not all actions are available for every metric or dashboard type.
-
-
-### Threshold Configuration
-
-The **Configuration** page allows you to set and manage warning and critical thresholds for key performance metrics across your application. Thresholds help you identify performance degradation early - when a metric exceeds a configured limit, it triggers visual alerts in dashboards and monitoring panels.
-
-You can adjust thresholds individually on certain graphs using the icon in the top right, or view and edit all thresholds in one place via **Quick Nav** → **Configuration**.
-
-
-
-
-#### Setting threshold values
-
-The **Edit Threshold** dialog allows you to configure two levels:
-
-- **Warning** - Set a threshold for early notification of potential issues (e.g., CPU at 50%)
-- **Critical** - Set a threshold for urgent alerts requiring immediate attention (e.g., CPU at 80%)
-
-Enter numeric values appropriate for the metric type. Percentage-based metrics use values from 0-100, while other metrics accept values based on their unit of measurement.
-
-Once configured, thresholds appear as visual indicators in metric panels across the application. When a metric value exceeds:
-
-- The **Warning** threshold - displayed with a yellow/orange indicator.
-- The **Critical** threshold - displayed with a red indicator.
-
-This visual feedback helps you quickly identify performance issues across your monitored services.
-
-Click **Update Thresholds** to apply your configuration. The new thresholds take effect immediately and will be used for all future metric evaluations.
-
-
-### Filters & Controls
-
-At the top of the screen, you can:
-
-* **Select Group, Node, Job, Instance** - to view data for specific servers or services. You can select multiple servers to compare metrics across your infrastructure.
-* **Set Time Range** - focus on the last hour, day, or a custom range.
-* **Add Adhoc Filters** - isolate data for specific endpoints, users, or environments.
-
-These dynamic filters make it easy to **narrow down the view** when diagnosing an issue. **Filters persist across tabs**, so when you switch between different dashboard views, your selected filters remain applied for consistent analysis.
-
-
-## Traces
-
-The **Traces** tab provides deep insights into the performance of individual requests (spans) as they move through the system. This view is critical for identifying slow transactions, latency issues, and service dependencies.
-
-
-
-Four key graphs display at the top of the view:
-
-1. **50th Percentile Span Duration** - Shows the median response time for requests, indicating typical performance.
-2. **95th Percentile Span Duration** - Displays response times for 95% of requests, helping identify slower outliers.
-3. **Status (Top spans by status code)** - Breaks down request volume by HTTP status codes (errors vs. successful requests).
-4. **Top 20 Span Throughput** - Shows request volume for the most active endpoints or operations.
-
-Use the filter bar to narrow down traces by:
-
-- **Job** - The service or application name (e.g., quote-service-lucee).
-- **Span Name** - Specific operation or endpoint.
-- **Status** - HTTP status code (All, error, ok, unset).
-- **Flavor** - Request type or protocol.
-- **Min/Max Duration** - Filter by response time range.
-- **Adhoc Filters** - Add custom filters with the + button.
-
-Below the metrics, the trace list shows individual requests with:
-
-- **Trace ID** - Unique identifier for the request (click to view detailed trace timeline).
-- **Start time** - When the request began.
-- **Service** - Which service handled the request.
-- **Name** - The HTTP method (GET, POST, etc.).
-- **Duration** - Total request processing time in milliseconds.
-
-
-### Trace Details
-
-When you click on a specific Trace ID from the Traces list, you navigate to the **Trace Details** view. This view is the core of distributed tracing, presenting the entire transaction flow as a precise waterfall diagram.
-
-
-
-The header displays key information about the selected trace:
-
-- **Service and Method** - The originating service and HTTP method (e.g., load-generator: POST).
-- **Total Duration** - End-to-end request time (e.g., 513.22ms).
-- **Timestamp** - Exact date and time the request started.
-- **Status Code** - HTTP response code with visual badge (e.g., 200, POST).
-- **Endpoint Path** - The API endpoint or route accessed.
-
-#### Navigation Tabs
-
-The trace details interface includes multiple tabs:
-
-- **Detail** - The default view showing the waterfall diagram of the trace spans.
-- **Profile** - When available, this tab displays a hierarchical flame graph showing method execution times and call stacks. Each entry shows the percentage of total execution time and duration (e.g., "100% - 1.61s") along with the full method path, allowing you to identify performance hotspots at the code level.
- 
-
-- **[Event Snapshot](https://docs.fusionreactor.io/Data-insights/Features/Debugger/Event-Snapshot/)** - This tab appears when a snapshot is associated with the trace, providing deep diagnostics including decompilation, frames, and request/response details captured at the point of the event.
- 
-
-#### Trace Actions
-
-Three action buttons in the top-right allow you to:
-
-1. **Analyze Trace** - Send the trace to OpsPilot AI for natural language analysis of performance bottlenecks, errors, and optimization recommendations.
-
-2. **Trace ID** - Copy the unique trace identifier to your clipboard for sharing or external analysis.
-
-3. **Export** - Download the trace data in a portable format for offline analysis or archival.
-
-## Logs
-
-The **Logs** tab allows you to view, filter, and analyze the log messages generated by the specific server instance in real time. This is essential for debugging errors and understanding system events.
-
-
-
-### Log Rate graph
-
-The top graph displays the volume of log entries over time, measured in requests per second (req/s). This visualization helps you:
-
-- Identify spikes in logging activity that may indicate issues.
-- Correlate log volume with performance problems or errors.
-- Understand normal logging patterns for your services.
-
-#### Filtering logs
-
-Use the filter bar to narrow down log entries:
-
-- **Job** - Filter by service or application name (e.g., quote-service-lucee).
-- **Instance** - Select a specific container or server instance (e.g., quote-6c4d97dbcc-4hf7q).
-- **Filter Text** - Search for specific keywords, error messages, or patterns within log content.
-- **Adhoc Filters** - Add custom filters with the + button to refine results further.
-
-Filters work together to help you quickly locate relevant log entries in high-volume environments.
-
-### Log stream
-
-The **All Logs** section displays individual log entries in chronological order. Each entry shows:
-
-- **Timestamp** - Exact date and time the log was generated (YYYY-MM-DD HH:MM:SS.mmm format).
-- **Level** - Log severity (e.g., SEVERE, WARNING, INFO, DEBUG).
-- **Message** - The complete log message, including stack traces for errors.
-
-### Log details
-
-When you click the arrow next to a log entry, it expands to show three sections:
-
-- **Log Line** - The complete, raw log message exactly as written by the application. This includes the timestamp, severity level (e.g., SEVERE), and the full message text with any error details or stack traces.
-
-- **Fields** - Structured metadata about the log entry, including the application name, service, instance ID, source file, and environment. Each field has icons that let you toggle visibility, view statistics, or add it as a filter.
-
-- **Links** - Quick actions to explore related data:
- - **Trace** button - Opens the associated distributed trace to see the full request flow that generated this log
- - **Ask OpsPilot AI** button - Sends the log to OpsPilot for AI-powered analysis, explanations, and troubleshooting recommendations
-
-
-
-
-## Info
-
-The **Client Information** panel provides detailed configuration and environment data for the selected job. Click any category to expand and view specific details.
-
-
-
-
-
-- **OS** - Operating system details including name, version, and architecture.
-- **Server** - Application server information such as type, version, and configuration.
-- **ENV Vars** - Environment variables configured for the instance.
-- **Client** - Client-specific settings and identifiers.
-- **System** - System-level properties and resource information.
-- **JVM** - Java Virtual Machine details including version, memory settings, and runtime parameters.
-- **Product** - Product or application version information.
-- **Network** - Network configuration including hostnames, ports, and IP addresses.
-- **Docker** - Container-specific information such as image name, container ID, and orchestration details.
-
-### Usage
-
-Select a job from the dropdown at the top to view its configuration. Expand any category to see the detailed key-value pairs associated with that job. This information is useful for troubleshooting configuration issues, verifying deployment settings, or understanding the runtime environment.
-
-## Crash Protection
-
-Crash Protection is a new diagnostic feature available starting in **version 2025.2**. It provides deep visibility into runtime behavior when a Crash Protection (CP) event occurs. The feature uploads detailed crash snapshots to the cloud, enabling analysis of system state at the moment a triggering exception or condition occurred.
-
-
-
-Crash Protection captures key runtime metrics:
-
-* **Heap memory usage** at the time of the event
-* **CPU utilization**
-* **Active web request count**
-* **Current database activity**
-
-Each report also includes the exception or condition that triggered the protection event (e.g., an `ArrayIndexOutOfBoundsException`, memory threshold breach).
-
-When a CP event occurs, the system captures a snapshot and uploads it to the cloud. These reports include:
-
-* The triggering request
-* Active threads at the time of capture
-* System resource utilization
-* Database activity
-* Lock information
-* Stack traces
-
-A **time picker** allows filtering events by any time range.
-
-
-### Viewing Crash Protection events
-
-On the left side of the **Crash Protection** page, a **Protection Events** panel lists all captured CP events for the selected job and time range. Each event shows the type (e.g., runtime, memory, quantity) and timestamp.
-
-Clicking any event in this list opens its full details in the **Crash Protection Report** section on the right. This report provides a complete breakdown of the system state at the moment the event was triggered.
-
-
-
-### Crash Protection Report structure
-
-Each **Crash Protection Report** contains several key sections that provide context and diagnostics for the event:
-
-#### Alert summary
-
-The notification banner at the top explains the nature of the protection event:
-
-- **Current State** - Key metrics at the time of trigger (e.g., free memory: 87%, used memory: 13%).
-- **Threshold Value** - The configured limit that triggered the alert (e.g., 3% memory threshold).
-- **Trigger Timing** - When the protection activated and for how long.
-- **Action Taken** - Whether this was notification-only or if protective measures were applied.
-
-#### Trigger information
-
-Displays the exact conditions that caused the alert:
-
-- **Triggered At** - Exact timestamp when the threshold was exceeded.
-- **Next Possible Trigger** - When the system will check again (helps prevent alert fatigue).
-- **Actual Value** - The metric value that exceeded the threshold.
-- **Threshold** - The configured limit for triggering protection.
-
-#### Server Load panel
-
-Real-time server metrics at the moment of capture:
-
-- **Active Web Requests** - Current HTTP requests being processed (with average timing).
-- **Active JDBC Transactions** - Database connections in use (with average timing).
-- **Heap Memory Usage** - Current memory consumption vs. total available.
- - Displayed as both a progress bar with percentage and actual values (e.g., 124.81 / 910.30 MB).
-- **CPU Usage**
- - **Instance** - This specific application instance.
- - **System** - Overall server CPU utilization.
-
-#### Triggering Request
-
-
-
-Details about the specific request that was active when protection triggered. The interface highlights the request responsible for the crash protection event:
-
-**Request identification:**
-- **URL** - The endpoint being accessed.
-- **User Agent** - Client making the request (browser, tool, API client, etc.).
-
-**Timing information:**
-- **Started** - When the request began.
-- **Duration** - How long the request has been running.
-- **GPU Time** - Graphics processing time (if applicable).
-- **DB Time** - Database query time.
-- **API Time** - External API call time.
-
-**System information:**
-- **Request ID** - Unique identifier for tracking and correlation.
-- **Thread** - The execution thread handling this request (e.g., `http-nio-8500-exec-5`).
-- **Memory** - Memory consumed by this specific request.
-- **Type** - HTTP method (GET, POST, PUT, DELETE, etc.).
-
-**Request details:**
-- **Status** - HTTP response code.
-- **Client IP** - Originating client address.
-
-#### Associated requests
-
-Other requests or threads running at the same time are also displayed in the **Running Requests** section. These may be related to the triggering condition or show overall system load during the event. If empty, displays "No running requests" - indicating the system has completed processing and may have recovered from the condition.
-
-
-
-
-
-#### Stack Trace section
-
-
-
-The **Stack Trace** panel provides thread-level debugging information:
-
-- **Thread State Filter** - View specific thread states (Running, Waiting, Blocked, etc.).
-- **Thread ID Filter** - Filter by specific thread identifiers.
-- **Search Field** - Text search within stack traces to quickly locate relevant code.
-
-The stack trace section helps developers identify which code was executing during the alert, enabling them to pinpoint potential memory leaks, deadlocks, or inefficient operations.
-
-### Thread analysis
-
-You can click on any **thread ID** to filter the report to only that thread's activity.
-
-#### Thread filtering
-
-Selecting a thread automatically shows:
-
-* Its current stack trace.
-* Its active operation (e.g., database call, waiting behavior).
-* Any objects or locks the thread is waiting on.
-
-
-### Lock inspection
-
-Clicking on a lock filters the display to show only the threads waiting on that specific lock. This allows you to:
-
-
-
-* See which objects threads were waiting on.
-* Identify whether multiple threads are blocked on the same resource.
-
-This is particularly helpful during deadlock investigations or performance bottleneck analysis.
-
-
-
-
-
-## Using Crash Protection Reports
-
-Follow this workflow to diagnose issues effectively:
-
-1. **Immediate Assessment** - Review the alert summary to understand severity and type of event.
-2. **Identify Culprit** - Examine the triggering request details to see what operation caused the event.
-3. **Analyze Load** - Use server load metrics to understand overall system pressure and resource utilization.
-4. **Debug Code** - Examine stack traces to identify problematic code paths.
-5. **Check for Contention** - Review lock information and associated requests to identify blocking conditions.
-6. **Prevent Recurrence** - Adjust protection thresholds or optimize identified code sections based on findings.
-
-Reports are retained for historical analysis and can help establish patterns in system behavior over time.
-
-
-## OpsPilot Integration
-
-Each Crash Protection alert can be forwarded to **OpsPilot** directly from the interface. This sends the full report to Ops Pilot for automated analysis and guidance.
-
-
\ No newline at end of file
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/Explore-servers/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/FR-Agent-Metrics.md b/docs/Data-insights/Features/FR-Agent-Metrics.md
index 9b1ef9c..89c4c09 100644
--- a/docs/Data-insights/Features/FR-Agent-Metrics.md
+++ b/docs/Data-insights/Features/FR-Agent-Metrics.md
@@ -1,440 +1,7 @@
-
-
# FusionReactor Agent Metrics
-The **FusionReactor Agent Metrics** page provides a comprehensive reference for all metrics collected by the FusionReactor agent across application, JVM, request, and cloud infrastructure layers. These metrics are essential for performance monitoring, alerting, and anomaly detection in both traditional and cloud-native environments.
-
-Metrics are grouped into categories based on the type of data they represent (e.g., CPU, memory, disk, transactions), and each entry includes a description and unit of measurement. Many of these metrics are designed to support real-time observability and are commonly used to configure alerts and build custom dashboards.
-
-
-Use this reference to:
-
-* Understand what each metric represents
-* Identify which metrics are alertable
-* Configure meaningful dashboards and threshold-based alerts
-
-
-## Understanding metric labels
-
-All FusionReactor Agent metrics include a standard set of **default labels**. These provide important context and make it easier to filter, group, and analyze data in cloud or containerized environments.
-
-### Default labels (applied to all metrics):
-
-| Name | Description |
-| ---------------------------- | ---------------------------- |
-| `client_id` | Unique ID for an FR instance |
-| `container_id`| The container ID for docker, kubernetes or ECS |
-| `docker` | Boolean value for if the container is running in docker |
-| `fusionreactor` | Boolean for if the metric is generated by FusionReactor |
-| `group` | The group specified in the FR Agent config |
-| `instance` | The hostname of the FR instance |
-| `job` | The name of the FR instance |
-
-These labels are automatically attached to each metric and do not need to be configured manually.
-
-
-Some metrics also include **[additional labels](/Data-insights/Features/FR-Agent-Metrics/#labels)** to provide more specific context. For example:
-
-* `jvm_threads_state` includes a `state` label (e.g. `RUNNABLE`, `WAITING`, `BLOCKED`).
-* `fr_cf_requests_throughput_error_time` may include `status` to distinguish between successful vs. failed requests (e.g., 200, 404, 500) and `type` to categorize request origin or type - such as api, static, internal, etc.
-
-When extra labels are used, they are shown in the **Labels** column of the tables below. If a metric only uses the default labels, this is marked as **Default**.
-
-
-### Adding custom labels to metrics
-
-In addition to the default labels listed above, you can also add your own custom labels to all metrics, logs, and traces generated by FusionReactor. This is useful for injecting environment-specific metadata such as region, team, or deployment ID.
-
-To add custom labels, use the `fr.observability.labels` system property with the `-D` flag when starting the JVM. The format is:
-
-```
--Dfr.observability.labels=labelKey1:labelValue1,labelKey2:labelValue2
-```
-
-For example:
-
-```
--Dfr.observability.labels=region:us-east-1,team:payments
-```
-
-This will automatically attach `region=us-east-1` and `team=payments` to every metric, log, and trace output.
-
-!!! info "Learn more"
- [System Properties documentation](/Monitor-your-data/FR-Agent/Configuration/FusionReactor-System-Properties/)
-
-
-## Metrics
-### Service uptime & Instance info
-
-| Name | Description | Labels | Unit |
-| ---------------------------- | ---------------------------- | ---- |---- |
-| up | Indicates the instance is up | [Labels](/Data-insights/Features/FR-Agent-Metrics/#up) | |
-| fusionreactor\_build\_info | FusionReactor build info | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fusionreactor_build_info) | |
-| fr\_server\_info | FusionReactor server info | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_server_info) |
-| fusionreactor\_license\_info | FusionReactor license info | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fusionreactor_license_info) | |
-
-
-### CPU usage
-
-| Metric Name | Description | Labels | Unit |
-| ------------------------------- | ------------------------------------------------------------ | ---- |---- |
-| process\_cpu\_usage | CPU utilization (%) of the instance across all cores | Default | % |
-| process\_cpu\_total\_usage | Total CPU utilization (%) across all cores and all processes | Default | % |
-
-
-
-### Memory usage
-
-| Metric Name | Description | Labels | Unit |
-| -------------------------------------- | --------------------------------- | ------ | ----- |
-| jvm\_memory\_pool\_bytes\_committed | Committed memory per memory pool | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_memory_pool_bytes_committed-jvm_memory_pool_bytes_used-jvm_memory_pool_bytes_max) | MiB |
-| jvm\_memory\_pool\_bytes\_max | Maximum memory per memory pool | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_memory_pool_bytes_committed-jvm_memory_pool_bytes_used-jvm_memory_pool_bytes_max) | MiB |
-| jvm\_memory\_pool\_bytes\_used | Used memory per memory pool | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_memory_pool_bytes_committed-jvm_memory_pool_bytes_used-jvm_memory_pool_bytes_max) | MiB |
-| jvm\_memory\_pool\_bytes\_total | Total memory pool size | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_memory_pool_bytes_committed-jvm_memory_pool_bytes_used-jvm_memory_pool_bytes_max) | MiB |
-| jvm\_memory\_bytes\_committed | Committed memory | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_memory_bytes_used-jvm_memory_bytes_committed-jvm_memory_bytes_ma-jvm_memory_bytes_used_percentage-jvm_memory_bytes_committed_percentage) | MiB |
-| jvm\_memory\_bytes\_max | Maximum available memory | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_memory_bytes_used-jvm_memory_bytes_committed-jvm_memory_bytes_ma-jvm_memory_bytes_used_percentage-jvm_memory_bytes_committed_percentage) | MiB |
-| jvm\_memory\_bytes\_used | Used memory | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_memory_bytes_used-jvm_memory_bytes_committed-jvm_memory_bytes_ma-jvm_memory_bytes_used_percentage-jvm_memory_bytes_committed_percentage) | MiB |
-| jvm\_memory\_bytes\_used\_percent | Percentage of memory used | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_memory_bytes_used-jvm_memory_bytes_committed-jvm_memory_bytes_ma-jvm_memory_bytes_used_percentage-jvm_memory_bytes_committed_percentage) | % |
-| jvm\_memory\_bytes\_committed\_percent | Percentage of memory committed | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_memory_bytes_used-jvm_memory_bytes_committed-jvm_memory_bytes_ma-jvm_memory_bytes_used_percentage-jvm_memory_bytes_committed_percentage) | % |
-| jvm\_gc\_collection\_seconds | Time spent in GC, per GC type | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_gc_collection_seconds-jvm_gc_collection_calls) | ms/s |
-| jvm\_gc\_collection\_calls | Number of GC invocations, per GC type | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_gc_collection_seconds-jvm_gc_collection_calls) | GC/s |
-
-
-### Thread & Class activity
-
-| Metric Name | Description | Labels | Unit |
-| --------------------------- | -------------------------------------- | ---- | ---- |
-| jvm\_threads\_current | Number of live JVM threads | Default | |
-| jvm\_threads\_state | JVM threads by state | [Labels](/Data-insights/Features/FR-Agent-Metrics/#jvm_threads_state)| |
-| jvm\_classes\_loaded | Count of classes loaded in the JVM | Default | |
-| jvm\_classes\_unloaded | Count of classes unloaded from the JVM | Default | |
-| jvm\_classes\_loaded\_total | Cumulative total of loaded classes | Default | |
-
-### Application
-
-
-| Metric Name | Description | Labels | Unit |
-| ------------------------------ | ------------------------------------------------------------------------------------------ | ------ | ----- |
-| app\_database\_throughput | Per-application average duration (ms) of database transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_database_throughput-app_database_error)| ms |
-| app\_database\_throughput\_cnt | Per-application count of database transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_database_throughput-app_database_error) | |
-| app\_database\_throughput\_sum | The application's total database transaction duration (in ms) for the last minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_database_throughput-app_database_error) | ms |
-| app\_database\_error | Per-application average duration (ms) of database error transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_database_throughput-app_database_error) | ms |
-| app\_database\_error\_cnt | Per-application count of database error transactions over the past minute. | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_database_throughput-app_database_error) | |
-| app\_database\_error\_sum | Per-application total duration (ms) of database error transactions over the past minute. | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_database_throughput-app_database_error)| ms |
-| app\_cpu | Per-application total CPU time (ms) over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory) | ms |
-| app\_cpu\_cnt | Per-application total CPU time (ms) over the past minute. (Count) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory) | |
-| app\_cpu\_sum | Per-application total CPU time (ms) over the past minute. (Sum) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory) | ms |
-| app\_memory | Per-application total memory usage (bytes) over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory) | bytes |
-| app\_memory\_cnt | Per-application total memory usage (bytes) over the past minute. (Count) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory) | |
-| app\_memory\_sum | Per-application total memory usage (bytes) over the past minute. (Sum) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory) | bytes |
-| app\_client\_error\_count | Per-application average duration (ms) of WebRequest 4xx responses over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory-app_client_error_count-app_server_error_count) | ms |
-| app\_client\_error\_count\_cnt | Per-application count of WebRequest 4xx responses over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory-app_client_error_count-app_server_error_count) | |
-| app\_client\_error\_count\_sum | Per-application total duration (ms) of WebRequest 4xx responses over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory-app_client_error_count-app_server_error_count) | ms |
-| app\_server\_error\_count | Per-application average duration (ms) of WebRequest 5xx responses over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory-app_client_error_count-app_server_error_count) | ms |
-| app\_server\_error\_count\_cnt | Per-application count of WebRequest 5xx responses over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory-app_client_error_count-app_server_error_count) | |
-| app\_server\_error\_count\_sum | Per-application total duration (ms) of WebRequest 5xx responses over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_cpu-app_memory-app_client_error_count-app_server_error_count) | ms |
-| app\_WebRequest | Per-application average duration (ms) of WebRequest transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_webrequest) | ms |
-| app\_WebRequest\_cnt | Per-application count of WebRequest transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_webrequest)| |
-| app\_WebRequest\_sum | Per-application total duration (ms) of WebRequest transactions over the past minute. | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_webrequest) | ms |
-| app\_up | Indicates the application was active in the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_up-app_error_count-app_throughput) | |
-| app\_error\_count | Per-application total errors over the last minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_up-app_error_count-app_throughput) | |
-| app\_error\_count\_cnt | Per-application total errors over the last minute. (Count) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_up-app_error_count-app_throughput) | |
-| app\_error\_count\_sum | Per-application total errors over the last minute. (Sum) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_up-app_error_count-app_throughput) | |
-| app\_throughput | Per-application average duration (ms) of master transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_up-app_error_count-app_throughput) | ms |
-| app\_throughput\_cnt | Per-application count of master transactions over the past minute. | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_up-app_error_count-app_throughput) | |
-| app\_throughput\_sum | Per-application total duration (ms) of master transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_up-app_error_count-app_throughput) | ms |
-| app\_txn\_error\_count | Per-transaction total errors over the last minute. | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_txn_error_count-app_txn_throughput) | |
-| app\_txn\_error\_count\_cnt | Per-transaction total errors over the last minute (Count) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_txn_error_count-app_txn_throughput) | |
-| app\_txn\_error\_count\_sum | Per-transaction total errors over the last minute (Sum) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_txn_error_count-app_txn_throughput) | |
-| app\_txn\_throughput | Per-transaction average duration (ms) of master transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_txn_error_count-app_txn_throughput) | ms |
-| app\_txn\_throughput\_cnt | Per-transaction count of master transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_txn_error_count-app_txn_throughput) | |
-| app\_txn\_throughput\_sum | Per-transaction total duration (ms) of master transactions over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#app_txn_error_count-app_txn_throughput) | ms |
-
-### Transactions
-
-
-| Metric Name | Description | Labels | Unit |
-| --------------------------- | --------------------------------------------------------------------------------- | ------ | ---- |
-| txn\_active\_activity | Number of active transactions per second, per-flavor, 1-min avg | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_active\_activity\_cnt | Number of samples taken for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_active\_activity\_sum | Total sum of values from all samples for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_active\_time | Avg. duration of active transactions per second (ms), per-flavor, 1-min avg | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error)| ms/s |
-| txn\_active\_time\_cnt | Number of samples taken for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_active\_time\_sum | Total sum of values from all samples for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_error\_activity | Number of transactions with errors per second, per-flavor, 1-min avg | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_error\_activity\_cnt | Number of samples taken for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error)| |
-| txn\_error\_activity\_sum | Total sum of values from all samples for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_error\_time | Avg. duration of transactions with errors per second (ms), per-flavor, 1-min avg. | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | ms/s |
-| txn\_error\_time\_cnt | Number of samples taken for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_error\_time\_sum | Total sum of values from all samples for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error)| |
-| txn\_history\_activity | Number of completed transactions per second, per-flavor, 1-min avg | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_history\_activity\_cnt | Number of samples taken for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_history\_activity\_sum | Total sum of values from all samples for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error)| |
-| txn\_history\_time | Avg. duration of completed transactions per second (ms), per-flavor, 1-min avg. | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error)| ms/s |
-| txn\_history\_time\_cnt | Number of samples taken for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error) | |
-| txn\_history\_time\_sum | Total sum of values from all samples for the base metric over the past minute | [Labels](/Data-insights/Features/FR-Agent-Metrics/#txn_activity-txn_history-txn_error)| |
-
-
-
-### System
-
-| Metric Name | Description | Labels | Unit |
-| ----------------------------------- | ------------------------------------------------ | ------ | ---- |
-| fr\_filesystem\_transmitted\_bytes | Data transmitted since boot (per network device) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_system_cpu_seconds_total) | B |
-| fr\_filesystem\_received\_bytes | Data received since boot (per network device) | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_network_received_bytes_total-fr_network_transmitted_bytes_total) | B |
-| fr\_filesystem\_read\_bytes\_total | Total disk read since boot | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_filesystem_read_bytes_total) | B |
-| fr\_filesystem\_write\_bytes\_total | Total disk write since boot | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_filesystem_read_bytes_total) | B |
-| fr\_filesystem\_avail\_bytes | Available disk space | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_filesystem_read_bytes_total) | B |
-| fr\_filesystem\_total\_bytes | Total disk space | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_filesystem_read_bytes_total) | B |
-| fr\_filesystem\_used\_bytes | Used disk space | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_filesystem_read_bytes_total) | B |
-| fr\_system\_cpu\_seconds\_total | Cumulative CPU seconds by system, per-CPU-category | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_system_cpu_seconds_total) | s |
-| fr\_cf\_system\_cached\_queries | ColdFusion cached query count, 1-min avg | Default | count |
-| fr\_cf\_system\_cached\_templates | ColdFusion template cache count | Default | count |
-| fr\_cf\_system\_template\_cache\_hit\_ratio | ColdFusion template cache hit ratio, 1- | Default | ratio (%) |
-| fr\_cf\_system\_throttled\_memory | ColdFusion total throttle memory used, 1-min avg | Default | bytes |
-| fr\_cf\_system\_throttled\_queue\_size | ColdFusion throttle queue size, 1-m | Default | count |
-| fr\_cf\_system\_concurrent\_users | ColdFusion concurrent user count, 1- | Default | count |
-| fr\_cf\_system\_cf\_thread\_throughput | ColdFusion thread count per 5 seconds, per-thread-status, 1-min avg | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_cf_system_cf_thread_throughput)| count/5s |
-| fr\_cf\_system\_scopes\_size\_kilobytes | ColdFusion cache/scope size (KB), per-cache/scope, 1-min avg | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_cf_system_scopes_size_kilobytes) | kilobytes |
-| fr\_cf\_requests\_throughput | ColdFusion request count per 5 seconds, per-request-type and per-request-status, 1-min avg | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_cf_requests_throughput) | count/5s |
-
-
-### Sessions
-
-| Metric Name | Description | Unit |Labels |
-| ------------------------- | -------------------------------- | ---- | ---- |
-| sessions\_created\_total | Total number of sessions created | Default | |
-| sessions\_active\_total | Total number of active sessions | Default | |
-| sessions\_rejected\_total | Total number of rejected sessions | Default | |
-sessions\_destryed\_total | Total number of sessions destroyed, 1-min avg | Default | |
-
-### Coldfusion Metrics
-
-| Metric Name | Description | Unit |Labels |
-| --------------------------------- | -------------------------------- | ---- | ---- |
-| fr\_cf\_hitcounts\_total | Total ColdFusion template hits | [Labels](/Data-insights/Features/FR-Agent-Metrics/#fr_cf_hitcounts_total) | |
-| fr\_cf\_system\_cached\_templates | ColdFusion cached template count | Default | |
-
-
-
-## Labels
-
-
-**Labels** are key-value pairs attached to metrics that provide additional context. They help distinguish between different dimensions of the same metric, such as the source, type, or environment. Labels are essential for querying, filtering, grouping, and visualizing metric data effectively.
-
-
-
-#### app\_database\_throughput / app\_database\_error
-
-| Name | Description | Example | More info |
-| --------- | -------------------- | ------------- | --------- |
-| app\_name | Application Name | JSP Test App | |
-| database | The database by name | DerbyMemoryDB | |
-| table | Database table | company\_d | |
-| action | Database action | insert | |
-
----
-
-#### app\_cpu / app\_memory / app\_client\_error\_count / app\_server\_error\_count
-
-| Name | Description | Example | More info |
-| --------- | ---------------- | ------------ | --------- |
-| app\_name | Application Name | JSP Test App | |
-
-
----
-
-#### app\_WebRequest
-
-| Name | Description | Example | More info |
-| --------- | ---------------- | ------------ | -------------------------- |
-| app\_name | Application Name | JSP Test App | |
-| status | Status code | | Not present on status code |
-
----
-
-#### app_up / app_error_count / app_throughput
-
-| Name | Description | Example | More info |
-| --------- | ---------------- | ------------ | --------- |
-| app\_name | Application Name | JSP Test App | |
-
----
-
-#### app_txn_error_count / app_txn_throughput
-
-| Name | Description | Example | More Info |
-| --------- | ---------------- | ------------------------------- | -------------- |
-| app\_name | Application Name | JSP Test App | |
-| txn\_name | Transaction name | controls.print\_00… (truncated) | max 2048 chars |
-
----
-
-
-#### fusionreactor\_build\_info
-
-| Name | Description | Example | More info |
-| --------- | --------------- | -------- | --------- |
-| version | FR version | 12.1.1 | |
-| build\_no | CI Build number | 11408 | |
-| branch | Git branch name | 12.1.1 | |
-| revision | Git commit hash | c83b8bbf | |
-
----
-
-#### fr\_server\_info
-
-| Name | Description | Example | More info |
-| ------------------- | ------------------ | ----------------- | --------------------------- |
-| java\_runtime\_name | Java runtime name | OpenJDK Runtime | |
-| java\_runtime\_version | Java runtime ver | 13.0.2+8 | |
-| type | Server type | TOMCAT | Can be UNKNOWN |
-| home | Server home | /home/luke/app/fr | Not present if not defined |
-| version | Server version | 9.0.50 | |
-| server\_name | Server name | page | UNKNOWN if not detected |
-| engine | ColdFusion engine | | |
-| lucee\_version | Lucee version | | UNKNOWN if not detected |
-| tomcat\_version | Tomcat version | 9.0.93 | Not present if not detected |
-| coldfusion\_version | ColdFusion version | | CommandBox only |
-| coldfusion\_product\_name | ColdFusion prod ID | CF only | |
-| coldfusion\_build | ColdFusion build | 330808 | CF only |
-| coldfusion\_major | ColdFusion major | 2023 | CF only |
-| coldfusion\_minor | ColdFusion minor | 0 | CF only |
-| coldfusion\_service | ColdFusion service | | CF only |
-| coldfusion\_hotfix | ColdFusion hotfix | hf-2023-00010-3 | CF only |
-
----
-
-#### fusionreactor\_license\_info
-
-| Name | Description | Example | More info |
-| ----- | ------------- | ------- | --------- |
-| type | License type | ULT | |
-| state | License state | active | |
-| cloud | Is Cloud lic | true | |
-
----
-
-#### fr\_cf\_hitcounts\_total
-
-| Name | Description | Example | More info |
-| ---- | -------------- | ---------------- | --------- |
-| type | Hit count type | One of: ref, web | |
-
----
-
-#### fr_cf_system_cf_thread_throughput
-
-| Name | Description | Example | More info |
-| ------ | ---------------- | ------- | --------- |
-| status | CF thread status | running | |
-
----
-
-#### fr_cf_system_scopes_size_kilobytes
-
-| Name | Description | Example | More info |
-| ----- | ------------- | -------------- | --------------- |
-| scope | CF scope type | session\_scope | template\_cache |
-
----
-
-#### fr_cf_requests_throughput
-
-| Name | Description | Example | More info |
-| ------ | -------------- | ----------- | --------- |
-| status | Request status | running | |
-| type | Request type | web service | |
-
----
-
-#### fr_system_cpu_seconds_total
-
-| Name | Description | Example | More info |
-| ---- | -------------------- | ------- | --------- |
-| mode | Category of CPU time | nice | |
-
----
-
-#### fr_network_received_bytes_total / fr_network_transmitted_bytes_total
-
-| Name | Description | Example | More info |
-| ------ | -------------- | --------- | --------- |
-| device | Network device | enp59s0f1 | |
-
----
-
-#### fr_filesystem_read_bytes_total
-
-| Name | Description | Example | More info |
-| ------ | ----------- | -------------- | --------- |
-| device | Disk name | /dev/nvme0n1p1 | |
-
----
-
-#### jvm_gc_collection_seconds / jvm_gc_collection_calls
-
-| Name | Description | Example | More info |
-| ---- | ----------- | ------------ | --------- |
-| gc | GC type | G1 Young Gen | |
-
-
----
-
-#### jvm_threads_state
-
-| Name | Description | Example | More info |
-| ----- | ------------ | -------- | --------- |
-| state | Thread state | runnable | |
-
----
-
-
-
-#### jvm_memory_pool_bytes_committed \ jvm_memory_pool_bytes_used \ jvm_memory_pool_bytes_max
-
-| Name | Description | Example | More info |
-| ---- | ------------ | ---------- | --------- |
-| pool | Memory space | G1 Old Gen | |
-
----
-
-#### jvm_memory_bytes_used / jvm_memory_bytes_committed / jvm_memory_bytes_ma / jvm_memory_bytes_used_percentage / jvm_memory_bytes_committed_percentage
-
-| Name | Description | Example | More info |
-| ---- | ----------- | ------- | --------- |
-| area | Memory area | heap | |
-
-
-
----
-
-#### txn_activity / txn_history / txn_error
-
-| Name | Description | Example | More info |
-| ------ | ------------------ | ---------- | ------------------------------------------------ |
-| flavor | Transaction flavor | WebRequest | Can only be one of: WebRequest, CFML, REST, etc. |
-
-
----
-
-#### uem
-
-| Name | Description | Example | More info |
-| ---- | ----------- | ------- | --------- |
-| type | UEM type | wr | |
-
----
-
-#### up
-
-| Name | Description | Example | More info |
-| --------- | ----------------- | ------------ | --------- |
-| start\_ts | Start time of the JVM in milliseconds | 173838589214 | |
-
----
-
-
-
-
+The FusionReactor Agent Metrics page provides a comprehensive reference for all metrics collected by the FusionReactor agent across application, JVM, request, and infrastructure layers - useful for alerting and anomaly detection.
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/FR-Agent-Metrics/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/Incidents/Settings.md b/docs/Data-insights/Features/Incidents/Settings.md
index bfe5769..03e8be8 100644
--- a/docs/Data-insights/Features/Incidents/Settings.md
+++ b/docs/Data-insights/Features/Incidents/Settings.md
@@ -1,64 +1,7 @@
-# Settings
+# Incidents Settings
-
+The Incidents Settings page lets you configure key elements of the Incidents module, including labels, severities, statuses, and roles.
-
-The **Settings** page allows users to configure key elements of the **Incidents** module, including **Labels**, **Severities**, **Statuses**, and **Roles**.
-
-## Access Settings
-
-
-
-
-1. Click the **cog icon** in the top-right of the screen.
-2. Navigate to the relevant section: **Labels**, **Severities**, **Statuses**, and **Roles**.
-
-
-
-
-### Labels
-
-Labels help categorize incidents for better tracking and filtering.
-
-- To add a label, click **+ Add Label** and enter a name, color and description and click **Save**.
-
-- Labels can be edited or deleted at any time.
-
-- By default, there will be a label called customers-affected. This label can be edited or deleted.
-
-- No minimum label requirements exist.
-
-### Severities
-
-Severities define the impact level of an incident. The available severities are:
-
-- **Pending** - Severity not yet determined.
-- **Low** - Limited impact on business operations.
-- **Medium** - Some impact on business operations.
-- **High** - Significant impact on business operations.
-- **Critical** - Severe business impact requiring immediate attention.
-
-
-### Statuses
-
-Statuses indicate the current state of an incident.
-
-- 🟠 **Active** - The incident is currently ongoing.
-- 🟢 **Resolved** - The incident has been resolved.
-
-
-### Roles
-
-Roles define responsibilities within an incident response.
-
-- **Default Roles:**
- - **Commander** - Manages the incident response.
- - **Investigator** - Handles the technical investigation.
-
-- To add a role, click **+ Add Role**, enter a name and description.
-
-!!! info
- Checking the **"Important"** box ensures the role appears on all incidents by default.
-
-
-- **Editing/Deleting:** Roles can be updated or removed, but at least **two roles** must always exist.
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/Incidents/Settings/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/Incidents/incidents.md b/docs/Data-insights/Features/Incidents/incidents.md
index 58761f9..57704ea 100644
--- a/docs/Data-insights/Features/Incidents/incidents.md
+++ b/docs/Data-insights/Features/Incidents/incidents.md
@@ -1,486 +1,7 @@
+# Incidents
-
-
-Available in public preview
-
-
-The **Incident Management Application** is a robust tool for tracking and resolving incidents in real-time. It streamlines incident workflows, enabling teams to manage tasks, update statuses, and maintain detailed activity logs with ease.
-
-
-
-
-Incidents can be challenging, particularly during the critical initial stages of investigation and identification. FusionReactor's **Incidents** feature is packed with powerful, time-saving tools designed to help you respond swiftly and efficiently, minimizing downtime and streamlining your resolution process.
-
-The application provides:
-
-- Real-time incident tracking and resolution.
-- Task assignment and progress monitoring.
-- Comprehensive activity logs for auditing actions.
-- Tools for efficient collaboration and communication.
-
-## Incidents dashboard
-
-The **Incidents** dashboard helps teams track, prioritize, and resolve incidents efficiently by centralizing relevant details and offering quick filtering and reporting options.
-
-
-
-The dashboard features **Incident Cards**, each representing a specific incident with essential details. These details include:
-
-- A **Title**, which provides a brief summary of the issue (e.g., Network Security Vulnerability).
-- The **Status** indicating whether the incident is Active or Resolved.
-- The **Severity**, categorized as Pending, Low, Medium, High, Critical to signify priority.
-- **Labels/Tags** based on areas such as Security, Infrastructure, API, or Database.
-- The **Declared On** date and time the incident was reported, along with the **Reported By** field, which identifies the user who logged the incident.
-- An **Incident Duration Timer** located at the bottom-right corner displays the total time the incident has been active, starting from the moment it was declared. The time is always shown in white, but if the incident is still active (i.e., not yet resolved), an orange clock icon appears to the left of the time to indicate that it is still live.
-
-### Filtering
-
-The filtering feature allows you to refine the list of incidents displayed on the **Incidents** page. This helps users quickly identify incidents based on their status, severity, associated labels or whether they are drills.
-
-
-- Click the filter button (top-right corner) to open a dropdown menu containing the following options:
- - Status
- - Severity
- - Labels
- - Show drills only? (Checkbox to filter and display only drill incidents)
-
-
-!!! info
- A red notification badge (e.g., 1) will appear on the button to indicate active filters.
-
-
-## Key features & workflows
-
-
-### Create a new incident
-
-To create a new incident:
-
-1. Navigate to the **Incidents** page.
-2. Click the **Declare Incident** button to open the incident creation form.
-
- 
-
-3. Fill in the required information:
-
- 
-
- - **Title**: A brief description of the incident.
- - **Severity**: Select from predefined levels (e.g., Pending, Low, Medium, High, Critical).
- - **Status**: Set the initial status (typically **Active**).
- - **Labels**: (Optional) Add tags to categorize the incident.
- - **Description**: Provide detailed information about the incident. The Description field allows up to 1,200 characters, enabling detailed documentation of the incident.
-
-4. Click **Save** to create the incident.
-
-!!! info
- Incident details such as title, start time, and labels can be updated at any time.
-
-
-
-### Manage tasks
-
-FusionReactor's integrated task management system helps you coordinate incident response by organizing critical actions and assignments. Using the built-in task manager, your team can collaborate effectively, monitor progress, and ensure swift completion of all necessary response activities.
-
-
-#### Add tasks
-
-To add a task within a specific incident:
-
-1. Navigate to the Tasks section of the incident, located on the right-hand sidebar.
-2. Provide a brief description of the task.
-3. Click on the +Task button.
-
-#### Edit tasks
-
-To edit a task:
-
-1. Click on a task to edit details.
-3. Assign tasks to different team members as needed.
-4. Mark tasks as complete when finished.
-
-#### Filter tasks
-
-Tasks can be filtered by status within a specific incident using the status dropdown/dropdown filter.
-
-
-#### Update task status
-
-Tasks have three statuses:
-
-- **To Do**
-- **In Progress**
-- **Done**
-
-To update a task's status:
-
-1. Click the checkbox next to the task.
-2. Each click cycles the task through the statuses in the following order:
- - **To Do → In Progress → Done**
-
-#### Assign tasks
-
-Task assignment ensures clear accountability and provides visibility into ongoing activities.
-
-To assign a task:
-
-1. Click on the people + icon next to the task.
-2. Search for and select the user you want to assign the task to.
-
-!!! tip
- Tasks can be unassigned or reassigned at any time. Simply click the assigned user, then choose Unassign User or search for another team member to reassign the task.
-
-### Real-time updates & notifications
-FusionReactor’s Incidents feature provides real-time collaboration capabilities, ensuring that teams stay informed and aligned while responding to incidents. These live updates reduce miscommunication and improve response efficiency.
-
-
-### Label management
-
-Labels transform your incident data into actionable insights by capturing key details like affected services, team involvement, and customer impact. Apply consistent labels to easily track patterns, filter similar incidents, and analyze trends across your incident history. This metadata becomes invaluable for identifying recurring issues, measuring team performance, and strengthening your incident response process over time.
-
-#### Add labels
-Labels are added during incident creation or via the **Add Label** button on the incident details page.
-
-#### New labels
-
-
-1. Navigate to the **Settings** page using the cog icon.
- 
-2. Select **+ Add label**
-2. Enter a name.
-2. Choose a color.
-3. Add a description.
-
-
-
-
-!!! tip
- Remove labels from an incident by clicking the **x** on the label badge.
-
-
-
-### Add comments/activities
-
-Keep the incident timeline organized by adding formatted notes and updates about response activities.
-
-1. In the **Activity** section, use the rich text editor to:
- - Write comments.
- - Format text or add links.
-2. Click **Add note** to post your comment.
-3. Comments appear chronologically in the activity timeline.
-
-!!! info
- The ellipsis button on comments in the activity timeline allows users to edit their posts.
-
-
-
-
-
-### Update incident status
-
-An incident's status instantly communicates whether your team is actively responding or has resolved the issue. Active incidents show there's ongoing work to restore service, while resolved status signals that normal operations have resumed. This clear indicator helps everyone from responders to stakeholders know at a glance if they need to take action or can stand down.
-
-To update an incident status:
-
-1. Use the **Status** dropdown on the incident details page.
-2. Select a new status:
- - **Active** or **Resolved**.
-3. If resolving the incident:
- - Provide a resolution summary.
- - Confirm the status change.
-
-
-
-### Adjust severity
-
-Incident severity levels tell you how serious an incident is and how quickly you need to act. By using consistent severity ratings, everyone in your organization can immediately understand how urgent each incident is and what response is needed.
-
-Setting clear severity levels helps your team know who to involve and what actions to take. Define each severity level with specific criteria and response requirements so your team can respond effectively and consistently.
-
-To adjust severity:
-
-1. Click the **Severity** indicator on the incident.
-2. Select the desired severity level (e.g., Pending, Low, Medium, High, Critical).
-3. Changes are automatically logged in the activity timeline.
-
-### Email notifications
-
-Users will receive automatic email notifications for key updates related to incidents they are involved in. These notifications ensure that all relevant stakeholders stay informed about important changes and assignments.
-
-Users will receive an email notification in the following situations:
-
-- **Role Assignment**: When they are assigned to a role on an incident.
-- **Task Assignment**: When they are assigned a task related to an incident.
-- **Incident Status Change**: If the status of an incident they are assigned to changes.
-- **Incident Severity Change**: If the severity level of an incident they are assigned to changes.
-
-!!! note
- Currently, there is no option to opt out of these email notifications. Notifications will always be sent to ensure users remain updated on critical incident developments.
-
-
-
-### Drill incidents
-
-The **Drill Incidents** feature allows teams to simulate real-world incident scenarios in a controlled environment. These drills help improve response readiness, validate processes, and identify areas for improvement.
-
-
-
-
-#### Create a drill
-
-
-To create a new drill incident:
-
-1. Navigate to the **Incidents** page.
-2. Click the **Create Drill** button to open the **Create a Drill Incident** form.
-
- 
-
- 
-
-4. Fill in the required details:
- - **Title**: A brief description of the drill incident.
- - **Severity**: Select from predefined levels (e.g., Pending, Low, Medium, High, Critical).
- - **Status**: Set the initial status (typically **Active**).
- - **Labels**: (Optional) Add tags to categorize the incident.
- - **Description**: Provide detailed information about the drill incident.
-
-5. Click **Save** to launch the drill.
-
-#### Manage a drill
-
-Once a drill incident is created, it functions like a regular incident but does not impact production workflows. Key features include:
-
-- **Task Assignments**: Assign and track drill-specific tasks.
-- **Status Updates**: Change the status from **Active** to **Resolved** once the drill is complete.
-- **Activity Timeline**: Monitor actions taken during the drill for later review.
-
-
-
-
-## Special features
-
-### Activity timeline
-
-The interactive timeline serves as your incident command center, providing a chronological view of all incident activities and enabling seamless collaboration. Responders can quickly scan past actions, review relevant context, and determine next steps without switching between multiple tools.
-
-
-
-The Incident Activity timeline:
-
-1. Automatically logs all actions, including:
- - Status changes
- - Comments
- - Task updates
-2. Provides a clear audit trail of who made changes and when.
-
-### Tasks on Active Incidents
-
-Task management streamlines incident response by keeping teams coordinated and accountable for specific actions. The **Tasks on Active Incidents** dashboard provides a comprehensive view of all incident-related tasks, organized into clear sections.
-
-!!! info
- Access this view by clicking the task page icon in the navigation menu.
- 
-
-#### Overview
-
-
-
-
-The overview dashboard displays tasks in three key categories:
-
-1. The Team: Shows overall task distribution
-
- - Todo: The number of tasks that have not been started by any team member.
- - In Progress: The number of tasks the team are currently working on.
- - Done: The number of tasks successfully completed by the team.
- - Unassigned: The number of tasks that have not yet been assigned to any team member.
-
-
-2. My Tasks: Displays your personal task breakdown.
-
- - My Todo: The number of tasks assigned to you that have not been started.
- - My In Progress: The number of tasks you are currently working on.
- - My Done: The number of tasks you have completed.
- - My Progress: The percentage of tasks you've completed out of your total assigned tasks for active incidents.
-
-
-
- !!! info
- Tasks marked as **done** will only appear in the **My Done** section while the incident remains **active**. Once the incident is **resolved**, they will no longer be shown there.
-
-3. Task list view: Displays your assigned task information as a list.
-
- - Task description
- - Current status (Todo, Progress, Done)
- - Related incident
-
- !!! tip
- Edit a task here by clicking on the task title or selecting the edit icon on the right. Quickly modify its status, reassign it to another team member, or update the task description.
-
-#### Kanban view
-
-The Kanban view on **All Tasks** is designed to streamline task management related to incidents. It organizes tasks into three primary columns: **To Do**, **In Progress**, and **Done**, allowing users to easily track the status and progress of incident-related activities.
-
-
-
-##### Key Features
-
-1. **Columns:**
- - **To Do**: Contains tasks that are yet to be started. Each task is assigned to a specific team member, whose name and avatar are displayed.
- - **In Progress**: Displays tasks currently being worked on, with a clear indication of the assignees.
- - **Done**: Shows completed tasks with a green checkmark for quick identification.
-
-2. **Task Cards:**
-Each task is represented by a card with the following details:
-
- - **Task Title**: A concise description of the task (e.g., "Reproduce the login crash issue").
- - **Assigned User**: Displays the name and profile avatar of the user responsible for the task.
- - **Actions**: Includes the option to delete a task for cleanup or reorganization.
-
-3. **Search and Filter:**
- - A **search bar** at the top allows users to find specific tasks quickly.
- - Users can filter tasks by assignee using the dropdown menu labeled **All Users**.
-
-!!! tip
- The task status can be changed by clicking the checkbox next to the task.
-
-
-This Kanban system enables efficient collaboration and task prioritization for incident resolution. It provides a visual representation of task progress, ensuring all team members are aligned on the current workload and priorities.
-
-#### Incident view
-
-View and manage tasks grouped by their associated incidents to track progress across multiple response efforts.
-
-
-
-Each incident section shows:
-
-- Incident name (e.g., "Service Latency Spike")
-- Progress summary showing total tasks and their status (todo, in progress, done)
-- Visual progress bar indicating overall completion
-- Task cards displaying:
- - Task description
- - Assigned team member with avatar
- - Task status indicator
- - Quick-access delete button
-
-##### Key Features
-
-- Filter tasks by incident using the dropdown menu
-- Filter by team member using the **All Users** selector
-- Search across all incident tasks using the search bar
-- View completed tasks with strikethrough formatting
-- Access additional options via the menu (⋮) button:
- - Go to incident
- - Add task
-
-
-
-
-
-
-
-
-
-### User assignments
-
-Strengthen your incident response by instantly bringing in the right experts and stakeholders using the **Add a user** feature. Whether you need hands-on responders or observers keeping track of progress, you can seamlessly expand your incident team with just a few clicks. Team members join with appropriate permissions, allowing them to immediately contribute to incident resolution or maintain situational awareness.
-
-1. Assign users to tasks or roles directly from the incident view.
-2. Track user involvement with activity logs.
-
-
-
-## Tips & best practices
-
-
-Incident creation
-
-- Use clear, descriptive titles.
-
-- Assign severity levels thoughtfully.
-
-- Add relevant labels for easy categorization.
-
-- Provide comprehensive descriptions to minimize follow-ups.
-
-
-
-Task management
-
-- Break down complex incidents into smaller, manageable tasks.
-
-- Assign tasks promptly to ensure accountability.
-
-- Regularly update task statuses to maintain visibility.
-
-
-
-Activity logging
-
-- Document all significant actions and decisions.
-
-- Use rich text formatting for clarity.
-
-- Include links or references to related resources.
-
-
-
-Label usage
-
-- Apply consistent naming conventions for labels.
-
-- Regularly review and update labels to reflect current needs.
-
-
-
-Status updates
-
-- Keep incident statuses current.
-
-- Use comments to explain status changes when needed.
-
-
-
-Drills
-
-- Ensure every drill has a goal, such as testing a specific process or response time.
-
-- Clearly define participant roles to simulate real incident conditions.
-
-- Base drills on past incidents or potential threats to improve preparedness.
-
-- After completion, analyze the drill’s performance and document lessons learned.
-
-
-
-
-## Troubleshooting
-
-Address common incident management challenges with these quick solutions.
-
-| **Issue** | **Resolution** |
-|-------------------------------|------------------------------------------------------------------|
-| **Cannot Create Incident** | Ensure all required fields are filled, valid severity selected. |
-| **Task Updates Not Saving** | Refresh the page or check your connection. |
-| **Labels Not Appearing** | Refresh the label list or check permissions. |
-| **Status Changes Not Working**| Verify permissions and valid status transitions. |
-
-___
-
-!!! question "Need more help?"
- Contact support in the chat bubble and let us know how we can assist.
-
+Incident Management is a tool for tracking and resolving incidents in real-time, with task assignment, activity logs, and collaboration features to help teams respond quickly and minimise downtime.
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/Incidents/incidents/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/alerting-examples.md b/docs/Data-insights/Features/alerting-examples.md
index cef1e2b..c5b74fb 100644
--- a/docs/Data-insights/Features/alerting-examples.md
+++ b/docs/Data-insights/Features/alerting-examples.md
@@ -1,369 +1,7 @@
-The following examples demonstrate how to create common FusionReactor alert rules using the Grafana Ruler-based alerting system. Each example covers the full configuration - query, condition, folder, evaluation group, No Data handling, and notifications.
+# Alerting Examples
-Before following these examples, make sure you have:
+Common examples for creating FusionReactor alert rules, covering full configuration including queries, conditions, evaluation groups, no-data handling, and notifications.
-- At least one **folder** created for your alert rules.
-- At least one **evaluation group** configured (or create one as part of the steps below).
-- At least one **contact point** configured. See [Contact Points](Alerting/Contact-points.md).
-
-### Routing your notifications
-
-There are two ways to route notifications when creating an alert rule:
-
-| Approach | When to use | Setup required |
-| --- | --- | --- |
-| **Direct contact point** | You want all notifications from this rule to go to one specific destination. | No extra setup - select the contact point in the rule editor. |
-| **Label-based routing** | You want flexible routing through notification policies (such as, routing by severity or team). | Requires **Advanced Alerting** to be enabled and notification policies configured. See [Notification Policies](Alerting/Notifications.md). |
-
-Each example below covers both options in the notifications step.
-
----
-
-## Performance checks
-
-### 1. When any instance goes offline for 5 minutes
-
-This rule monitors all FusionReactor instances on your Cloud license and fires when any of them stops reporting data.
-
-Offline detection works in two ways: if `app_up` drops to `0`, the alert condition (**IS BELOW 1**) triggers directly. If the instance stops reporting entirely and metrics disappear, the **No Data → Alerting** setting fires the alert. Both cases are covered by this rule.
-
-Because the rule produces one alert instance per time series, each FusionReactor instance is monitored independently. If one instance goes offline, only that instance's alert fires.
-
-#### Configuration
-
-Navigate to **Alerting** > **Alert rules** and click **+ New alert rule**.
-
-**1. Name**
-
-Enter a name such as `Any Instance Offline`.
-
-**2. Query and condition**
-
-- Select your FusionReactor data source.
-- Select the `app_up` metric. Leave instance and job filters unset to monitor all instances.
-- Set the alert condition to **IS BELOW 1**. When an instance is online, `app_up` returns `1` - so the condition is false and the alert stays normal. When an instance goes offline, `app_up` drops to `0` or stops reporting entirely, which triggers the alert.
-
-!!! tip
- Click **Preview alert rule condition** to confirm data is being returned before continuing.
-
-**3. Folder and evaluation group**
-
-- Select or create a folder (such as, `FusionReactor Alerts`).
-- Select or create an evaluation group with an interval of `1m`.
-- Set the **Pending period** to `5m`. The alert will only fire after the instance has been consistently offline for 5 minutes.
-
-**4. No Data handling**
-
-Under **Configure no data and error handling**, set **No Data** to **Alerting**. When an instance stops reporting, the query returns no data and this setting transitions the alert to Firing.
-
-**5. Notifications**
-
-- **Direct contact point (simple):** Under **Notifications**, select your contact point directly from the **Contact point** dropdown.
-- **Label-based routing (advanced alerting):** Leave the contact point unset and add a label to route through your notification policies - for example, `channel` = `slack`.
-
-**6. Annotations**
-
-- **Summary:** `Instance offline: {{ $labels.instance }}`
-- **Description:** `The instance {{ $labels.instance }} has not reported data for 5 minutes and may be offline.`
-
-**7. Save**
-
-Click **Save rule and exit**.
-
-
-
----
-
-### 2. When a single job goes offline for 5 minutes
-
-This rule monitors a specific FusionReactor instance or job and fires when it stops reporting data. Use this for named, business-critical instances where you want a dedicated alert rather than relying on the broad monitoring of Example 1.
-
-#### Configuration
-
-Navigate to **Alerting** > **Alert rules** and click **+ New alert rule**.
-
-**1. Name**
-
-Enter a name such as `Instance Offline - [instance name]`.
-
-**2. Query and condition**
-
-- Select your FusionReactor data source.
-- Select the `app_up` metric and filter by the specific **Job** or **Instance** label you want to monitor (such as, `instance = "production-server-01"`).
-- Set the alert condition to **IS BELOW 1**. When the instance is online, `app_up` returns `1` - so the condition is false and the alert stays normal. When the instance goes offline, `app_up` drops to `0` or stops reporting, which triggers the alert.
-
-!!! tip
- Click **Preview alert rule condition** to confirm data is being returned before continuing.
-
-**3. Folder and evaluation group**
-
-- Select or create a folder.
-- Select or create an evaluation group with an interval of `1m`.
-- Set the **Pending period** to `5m`.
-
-**4. No Data handling**
-
-Under **Configure no data and error handling**, set **No Data** to **Alerting**. When the monitored instance stops reporting, this transitions the alert to Firing.
-
-**5. Notifications**
-
-- **Direct contact point (simple):** Under **Notifications**, select your contact point directly from the **Contact point** dropdown.
-- **Label-based routing (advanced alerting):** Leave the contact point unset and add a label to route through your notification policies - for example, `channel` = `slack`.
-
-**6. Annotations**
-
-- **Summary:** `Instance offline: {{ $labels.job }}`
-- **Description:** `The instance {{ $labels.job }} ({{ $labels.instance }}) has not reported data for 5 minutes.`
-
-**7. Save**
-
-Click **Save rule and exit**.
-
-
-
----
-
-### 3. When any instance is using over 90% CPU for 2 minutes
-
-This rule fires when any FusionReactor instance sustains high system CPU usage, helping you catch runaway processes or capacity issues before they affect users.
-
-!!! tip
- You can also use a **less than** threshold for underflow alerts - for example, alert when request volume drops below a baseline. This is useful for high-traffic services where unexpectedly low activity may indicate requests are not reaching the service.
-
-#### Configuration
-
-Navigate to **Alerting** > **Alert rules** and click **+ New alert rule**.
-
-**1. Name**
-
-Enter a name such as `High CPU - Any Instance`.
-
-**2. Query and condition**
-
-- Select your FusionReactor data source.
-- Select the **System CPU usage** metric. Leave instance and job filters unset to monitor all instances.
-- Set the alert condition to **IS ABOVE 90**.
-
-!!! tip
- Click **Preview alert rule condition** to confirm data is being returned before continuing.
-
-**3. Folder and evaluation group**
-
-- Select or create a folder.
-- Select or create an evaluation group with an interval of `1m`.
-- Set the **Pending period** to `2m`. The alert only fires if CPU remains above 90% for at least 2 consecutive minutes, avoiding notifications for momentary spikes.
-
-**4. Notifications**
-
-- **Direct contact point (simple):** Under **Notifications**, select your contact point directly from the **Contact point** dropdown.
-- **Label-based routing (advanced alerting):** Leave the contact point unset and add a label to route through your notification policies - for example, `channel` = `slack`.
-
-**5. Annotations**
-
-- **Summary:** `High CPU on {{ $labels.instance }}: {{ $values.A.Value | printf "%.1f" }}%`
-- **Description:** `CPU usage has been above 90% for over 2 minutes on {{ $labels.instance }}.`
-
-**6. Save**
-
-Click **Save rule and exit**.
-
-
-
----
-
-### 4. When any instance in a group is using over 90% allocation memory for 10 minutes
-
-This rule monitors memory allocation across all instances sharing a specific group label, and fires when any of them sustains high memory usage for an extended period.
-
-Instances can be assigned a group in FusionReactor, which appears as a label on their metrics. Filtering by group lets you scope an alert to a logical subset of your estate - for example, all instances in a production environment or a specific application tier.
-
-#### Configuration
-
-Navigate to **Alerting** > **Alert rules** and click **+ New alert rule**.
-
-**1. Name**
-
-Enter a name such as `High Memory - [Group Name] Group`.
-
-**2. Query and condition**
-
-- Select your FusionReactor data source.
-- Select the **Allocation memory usage** metric.
-- Filter by the **group** label to target the specific group (such as, `group = testfr`). This scopes the rule to only the instances in that group.
-- Set the alert condition to **IS ABOVE 90**.
-
-!!! tip
- Click **Preview alert rule condition** to confirm data is being returned before continuing.
-
-**3. Folder and evaluation group**
-
-- Select or create a folder.
-- Select or create an evaluation group with an interval of `1m`.
-- Set the **Pending period** to `10m`. This prevents noise from short-lived spikes - the alert only fires if memory pressure is sustained for 10 full minutes.
-
-**4. Notifications**
-
-- **Direct contact point (simple):** Under **Notifications**, select your contact point directly from the **Contact point** dropdown.
-- **Label-based routing (advanced alerting):** Leave the contact point unset and add a label to route through your notification policies - for example, `channel` = `slack`.
-
-**5. Annotations**
-
-- **Summary:** `High memory on {{ $labels.instance }} (group: {{ $labels.group }}): {{ $values.A.Value | printf "%.1f" }}%`
-- **Description:** `Allocation memory usage has been above 90% for over 10 minutes on {{ $labels.instance }} in the {{ $labels.group }} group.`
-
-**6. Save**
-
-Click **Save rule and exit**.
-
-
-
----
-
-## Billing checks
-
-Billing alerts let you monitor your FusionReactor Cloud usage against thresholds before you exceed a plan limit or incur unexpected on-demand charges.
-
-!!! warning "Always filter by `servicename`"
- All billing metrics aggregate usage across **all services** unless you filter by the `servicename` label. Failing to specify a `servicename` will result in aggregated usage data, leading to inaccurate alerts. Always add a `servicename` filter as shown in the examples below.
-
-The following billing metrics are available:
-
-| Metric | What it measures |
-| --- | --- |
-| `fr_billing_usage_current` | Current monthly usage for the selected service |
-| `fr_billing_charges_metered` | On-demand usage charges for the selected service |
-| `fr_billing_usage` | Total billable data usage for the selected service |
-| `fr_billing_charges_total` | Total current billing charges for the selected service |
-
----
-
-### 5. On-demand usage alert
-
-Triggers when on-demand usage charges for a service exceed a threshold, using the `fr_billing_charges_metered` metric.
-
-#### Configuration
-
-Navigate to **Alerting** > **Alert rules** and click **+ New alert rule**.
-
-**1. Name**
-
-Enter a name such as `On-Demand Charges - [Service Name]`.
-
-**2. Query and condition**
-
-- Select your FusionReactor data source.
-- Select the `fr_billing_charges_metered` metric.
-- Filter by `servicename` and specify the target service name. This is required to avoid aggregated data across all services.
-- Set the alert condition to **IS ABOVE** and specify your threshold value (in the units your billing reports use).
-
-!!! tip
- Click **Preview alert rule condition** to confirm data is being returned before continuing.
-
-**3. Folder and evaluation group**
-
-- Select or create a folder.
-- Select or create an evaluation group with an appropriate interval (such as, `1h` for billing checks).
-
-**4. Notifications**
-
-- **Direct contact point (simple):** Under **Notifications**, select your contact point directly from the **Contact point** dropdown.
-- **Label-based routing (advanced alerting):** Leave the contact point unset and add a routing label - for example, `channel` = `email`.
-
-**5. Annotations**
-
-- **Summary:** `On-demand charges threshold exceeded for {{ $labels.servicename }}`
-- **Description:** `On-demand usage charges for {{ $labels.servicename }} have exceeded the configured threshold.`
-
-**6. Save**
-
-Click **Save rule and exit**.
-
-
-
----
-
-### 6. Billable data usage alert
-
-Triggers when total billable data usage for a service exceeds a threshold, using the `fr_billing_usage` metric. Use this to monitor data volume before you approach a plan limit.
-
-#### Configuration
-
-Navigate to **Alerting** > **Alert rules** and click **+ New alert rule**.
-
-**1. Name**
-
-Enter a name such as `Billable Data Usage - [Service Name]`.
-
-**2. Query and condition**
-
-- Select your FusionReactor data source.
-- Select the `fr_billing_usage` metric.
-- Filter by `servicename` and specify the target service name.
-- Set the alert condition to **IS ABOVE** and specify your threshold in bytes. For example, to alert at 80 GB, enter `80000000000`.
-
-!!! tip
- Click **Preview alert rule condition** to confirm data is being returned before continuing.
-
-**3. Folder and evaluation group**
-
-- Select or create a folder.
-- Select or create an evaluation group with an appropriate interval (such as, `1h`).
-
-**4. Notifications**
-
-- **Direct contact point (simple):** Under **Notifications**, select your contact point directly from the **Contact point** dropdown.
-- **Label-based routing (advanced alerting):** Leave the contact point unset and add a routing label - for example, `channel` = `email`.
-
-**5. Annotations**
-
-- **Summary:** `Data usage threshold exceeded for {{ $labels.servicename }}`
-- **Description:** `Billable data usage for {{ $labels.servicename }} has exceeded the configured threshold.`
-
-**6. Save**
-
-Click **Save rule and exit**.
-
-
-
----
-
-### 7. Total billing charges alert
-
-Triggers when total billing charges for a service exceed a threshold, using the `fr_billing_charges_total` metric. Use this for a high-level cost ceiling alert covering all charge types.
-
-#### Configuration
-
-Navigate to **Alerting** > **Alert rules** and click **+ New alert rule**.
-
-**1. Name**
-
-Enter a name such as `Total Billing Charges - [Service Name]`.
-
-**2. Query and condition**
-
-- Select your FusionReactor data source.
-- Select the `fr_billing_charges_total` metric.
-- Filter by `servicename` and specify the target service name.
-- Set the alert condition to **IS ABOVE** and specify your threshold value.
-
-!!! tip
- Click **Preview alert rule condition** to confirm data is being returned before continuing.
-
-**3. Folder and evaluation group**
-
-- Select or create a folder.
-- Select or create an evaluation group with an appropriate interval (such as, `1h`).
-
-**4. Notifications**
-
-- **Direct contact point (simple):** Under **Notifications**, select your contact point directly from the **Contact point** dropdown.
-- **Label-based routing (advanced alerting):** Leave the contact point unset and add a routing label - for example, `channel` = `email`.
-
-**5. Annotations**
-
-- **Summary:** `Total billing charges threshold exceeded for {{ $labels.servicename }}`
-- **Description:** `Total billing charges for {{ $labels.servicename }} have exceeded the configured threshold.`
-
-**6. Save**
-
-Click **Save rule and exit**.
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/alerting-examples/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/applications.md b/docs/Data-insights/Features/applications.md
index aed3525..aa570ae 100644
--- a/docs/Data-insights/Features/applications.md
+++ b/docs/Data-insights/Features/applications.md
@@ -1,148 +1,7 @@
# Applications
-🔎**Find it**: **FusionReactor** > **Applications**
+The Applications view displays an overview of all your applications running on servers monitored by FusionReactor, giving you visibility into performance across your entire application estate.
-
-
-The **Applications** list view on FusionReactor Cloud displays an overview of all your applications on servers running FusionReactor.
-
-## Applications filtering
-
-Applications can be filtered by **View**, **Filter**, **Sort by** and **Sort order**.
-
-
-
-* In the **View** dropdown, you can choose to display your applications in either a **Grid** or **Row** view.
-
-* Use the **Filter** dropdown to filter the applications in a state of **Slow** or **Error**.
-
-* You can also filter for applications that have been **deleted**.
-
-* Use the **Sort by** dropdown to filter applications by:
-
- 1. **Attribute**
-
- * Name
-
- * Last updated
-
- 2. **Metric**
- * Request throughput
- * Error count
- * Average response
-
- * Max response
-
-* In the **Sort order** dropdown, you can view your applications in **Ascending** or **Descending** order.
-
-* To clear all filters, select the icon at the far right of the screen.
-
-
-
-!!! tip
- Search directly for an application **name** (or **alias**) using the search box inside the filter bar.
-
-
-## Applications details
-
-The applications details screen is displayed when an application is selected.
-
-
-
-## Transaction bars
-
-🔎**Find it**: **FusionReactor** > **Applications** > **Performance**
-
-
-
-The transaction list displays all the transactions associated with that application for the set timeframe as well as the selected tab in the filter bar.
-
-Transactions can be filtered by selecting the relevant tab:
-
-1. **Time taken** - This displays the percentage of time the application running that transaction.
-2. **Average time** - This shows the average time for each transaction, with a line displayed across all transactions showing the average for the entire application. The application average time is displayed below the transaction list.
-3. **Slowest** - This displays the longest response time for each transaction, with the total of the longest times shown below the transactions list.
-4. **Throughput** - This shows the number of requests for each transaction, with the total number of requests displayed below the transaction list.
-5. **Errors** - This displays the number of errors for each transaction that has caused errors, with the total number of errors displayed below the transaction list.
-
-## Transactions graphs
-
-🔎**Find it**: **FusionReactor** > **Applications** > **Graphs**
-
-
-
-
-The graph data is displayed by:
-
-* **Time Taken**
-
-* **Average Response Time**
-
-* **Max Response Time**
-
-* **Error Count**
-
-
-The graph can be manipulated in a number of ways:
-
-1. Hovering the mouse over the graph will show all the data for that time point.
-
-
-
-2. The graphs can be filtered by:
-
-
-
-* **Profile** - either **System** or **Custom**
-
-* **Graphs** - **Average Response Time**, **Error Count** and more...
-
-* **Hide empty** - either **True** or **False**
-
-* **View** - **Grid** or **Row**
-
-
-
-
-
-
-
-## **Interesting transactions**
-
-
-
-This list shows all the interesting transactions related to the selected application.
-
-A transaction is regarded as *interesting* if it is:
-
-1. **Slow** - The slowest four transactions over 500ms for every minute.
-2. **Very slow** - The first four transactions over the slow request threshold as set in the FR Client (by default this is 8 seconds) for every minute.
- * Set the threshold in the FR client by going to **Requests** > **Settings** > **WebRequest History** > **Slow Request Threshold** (seconds).
-3. **Error** - The transaction returned an error.
-
-The following information is displayed by the interesting transactions list:
-
-1. **Started** - The start time and date of the transaction.
-2. **Status** - The status code that the transaction returned, for example 200, 500, etc.
-3. **Flavor** - The type of transaction, for example Web Request, JDBC request, etc.
-4. **Txn (Transaction)** - Transaction name.
-5. **Description** - A description of the transaction. For example, the URL of the request, database query, etc.
-6. **Reason** - The reason the transaction is interesting (Slow, Very slow or Error).
-7. **Dur (Duration)** - Duration of the transaction in MS.
-8. **Actions** - Two actions:
-
- * View the details page of that transaction.
- * Save the transaction under the saved transactions view for that application / instance.
-
-## Filtering
-
-The interesting transactions list has two ways to filter and sort it:
-
-
-
-1. The **Reason** dropdown will filter by reason type, with the options of **Slow** and **Errors**.
-
-2. The **Min duration** dropdown will filter the list to only show transactions with a duration time over the specified time.
-
-!!! question "Need more help?"
- Contact support in the chat bubble and let us know how we can assist.
\ No newline at end of file
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/applications/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/dashboards.md b/docs/Data-insights/Features/dashboards.md
index c8a155d..45cad25 100644
--- a/docs/Data-insights/Features/dashboards.md
+++ b/docs/Data-insights/Features/dashboards.md
@@ -1,123 +1,7 @@
-# Overview
+# Dashboards
-**Dashboards** allow you to visualize your Cloud data with superior, unparalleled depth.
+Dashboards let you visualize your observability data by combining metrics, logs, and traces in one place, giving you a complete picture of your environment.
-Combine metrics, logs and traces in one place to give you a complete picture of your data.
-
-
-
-
-
-
-## Central FusionReactor dashboard
-
-**Find it**: **FusionReactor** > **Dashboards**
-
-The central **Dashboard** contains links to all dashboards and can be used to quickly navigate between all dashboards.
-
-Log dashboards will be added and improved over time, including adding new categories of dashboards, new log views and new filters to gain insight and value from your logs.
-
-### Using dashboards
-
-Navigate to individual dashboards from the new **Dashboard** tab of FusionReactor Cloud. Use the links in the top right to navigate back to the main FusionReactor dashboards.
-
-
-
-
-The dashboard user interface provides a number of features that you can use to customize the presentation of your data.
-
-The following image and descriptions highlights all of the dashboards features.
-
-
-
-1. **Dashboard title**: When you click the dashboard title you can search for dashboard contained in the current folder.
-
-2. **Star icon**: This feature allows you to place the corresponding dashboard in your favorites view, for easier access.
-
-3. **Share dashboard**: Use this option to share the current dashboard by link or snapshot. You can also export the dashboard definition from the share modal.
-
-4. **Add a new panel**: Use this option to add a panel, dashboard row, or library panel to the current dashboard.
-
-5. **Dashboard settings**: Use this option to change dashboard name, folder, and tags and manage variables and annotation queries.
-
-6. **Time picker dropdown**: Click to select relative time range options and set custom absolute time ranges. Highlighting a specific timeframe of a chart will modify the timeframe for all graphs on the dashboard.
-
-7. **Zoom out time range**: Click to zoom out the time range.
-
-8. **Refresh dashboard**: Click to immediately trigger queries and refresh dashboard data.
-
-9. **Refresh dashboard time interval**: Click to select a dashboard auto refresh time interval.
-
-10. **View mode**: Click to display the dashboard on a large screen such as a TV or a kiosk. View mode hides irrelevant information such as navigation menus.
-
-### Build custom dashboards
-
-Transform your raw data into actionable insights by building custom dashboards. Using our intuitive dashboard builder, you can connect to multiple data sources, write targeted queries (LogQL, PromQL, or TraceQL), and arrange visualizations to create a real-time view of your application's health.
-
-!!! info
- [Learn how to create a dashboard →](https://docs.fusionreactor.io/Getting-started/Tutorials/create-dashboard/)
-
-
-## Dashboard index
-
-### FusionReactor dashboards
-
-**Databases** - Observe database activity including throughput, time, total queries and error rate, broken down by database, collection / table and action.
-
-**Instances** - Observe throughput, response time and error count broken down per instance.
-
-**Request Performance** - Observe throughput, response time and error count, broken down by application, txn route and status code.
-
-**System Resource Usage** - Observe the CPU, memory, GC and JIT statistics broken down by instance or application.
-
-**Total System Resource Usage** - Observe the CPU, memory, GC and JIT statistics for your entire application stack.
-
-**Web Applications** - Observe throughput, response time and error count broken down per application.
-
-### Infrastructure dashboards
-
-**Instance Map** - Observe instance health based on process CPU, system CPU or JVM memory usage. This view is similar to what you would see in the Enterprise Dashboard
-
-### Log dashboards
-
-For the list of log dashboards see the [log dashboard index](#).
-
-### Integration dashboards
-
-**MySQL** - Observe metrics from the [MySQL exporter](/Monitor-your-data/Observability-agent/overview/#exporters).
-
-
-
-**MSSQL** - Observe metrics from the [MSSQL exporter](/Monitor-your-data/Observability-agent/overview/#exporters).
-
-
-**Node exporter** - Observe metrics from the [Node exporter](/Monitor-your-data/Observability-agent/overview/#exporters)
-
-
-
-**NGINX community** - Observe metrics from the [NGINX exporter](/Monitor-your-data/Observability-agent/overview/#exporters)
-
-
-
-**NGINX pro** - Observe metrics from the [NGINX exporter](/Monitor-your-data/Observability-agent/overview/#exporters)
-
-
-**Kafka** - Observe metrics from the [Kafka exporter](/Monitor-your-data/Observability-agent/overview/#exporters)
-
-
-
-**OracleDB Monitor**- Observe metrics from the [OracleDB Monitor](/Monitor-your-data/Observability-agent/overview/#exporters)
-
-
-
-
-### Experimental dashboards
-
-Some dashboards have been marked as experimental, this allows us to continually roll out new concepts for dashboards.
-
-These dashboards may contain issues, as we continue to refine and develop them.
-
-___
-
-!!! question "Need more help?"
- Contact support in the chat bubble and let us know how we can assist.
\ No newline at end of file
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/dashboards/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/database.md b/docs/Data-insights/Features/database.md
index eb7f36d..00216ee 100644
--- a/docs/Data-insights/Features/database.md
+++ b/docs/Data-insights/Features/database.md
@@ -1,60 +1,7 @@
# Database
-The **Database** page gives you full visibility into how your databases are performing across your entire environment. Use it to pinpoint slow or expensive queries, detect errors before users report them, understand which applications are generating the most database load, and compare performance across multiple instances - all from a single dashboard.
+The Database page gives you full visibility into how your databases are performing across your entire environment, helping you pinpoint slow queries, detect errors before users report them, and understand which applications are generating the most database load.
-## Filters
-
-Use the filter bar to focus the dashboard on exactly what you need:
-
-| Filter | Description |
-|---|---|
-| **Job** | Isolate metrics for a specific job label |
-| **Application Name** | See which application is responsible for the database traffic |
-| **Instance** | Compare performance across individual database instances |
-| **Database** | Drill into a specific database by name |
-| **Action** | Filter by SQL action type (e.g. SELECT, INSERT) |
-| **TopK** | Limit results to the top K entries by value |
-| **Time range** | Control the time window for all panels - defaults to the last 1 hour but can be adjusted to cover longer periods for trend analysis |
-
-## Tabs
-
-| Tab | Description |
-|---|---|
-| **Metrics** | Pre-built panels showing database performance metrics |
-| **Traces** | Distributed traces for individual database calls |
-| **Integrations** | View database integration status |
-| **Kubernetes** | Database metrics scoped to Kubernetes workloads |
-| **Anomaly Detection** | Anomaly alerts detected on database signals |
-| **Custom** | Add and arrange your own panels |
-
-## Metrics panels
-
-### Database Time Spent on Commands
-
-Shows the proportion of total execution time spent on each command type (e.g. SELECT, INSERT). If one command type dominates - for example SELECT accounting for 95% of time - this is a strong signal of where to focus optimisation efforts.
-
-### Database Throughput by Job / Application / Instance
-
-Tracks the rate of database commands per minute over time. Use this to identify which services are generating the most database traffic, spot unexpected spikes, and support capacity planning decisions.
-
-### Database Errors by Job / Application / Instance
-
-Shows the rate of database errors per minute. Spikes here typically precede or coincide with user-facing failures - catching them early means you can act before users report problems.
-
-### Database Query Throughput per Job / Application / Instance
-
-Shows query volume per minute broken down by job, application, and instance. Useful for understanding load distribution and identifying a specific application that may be overwhelming the database.
-
-### Database Total Query Time by Command / Job / Application / Instance
-
-Shows cumulative query execution time broken down by SQL command, job, application, and instance. This is the most direct panel for identifying slow or expensive query patterns - a sharp increase here points to a query that needs attention.
-
----
-
-!!! tip "Troubleshooting slow applications"
- If an application feels sluggish, filter by **Application Name** and check the Total Query Time and Error panels first. A spike in either confirms the database is the bottleneck.
-
----
-
-!!! question "Need more help?"
- Contact support in the chat bubble and let us know how we can assist.
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/database/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/explore-logs.md b/docs/Data-insights/Features/explore-logs.md
index e5bd013..020cf6c 100644
--- a/docs/Data-insights/Features/explore-logs.md
+++ b/docs/Data-insights/Features/explore-logs.md
@@ -1,98 +1,7 @@
-# Overview
+# Logs Drilldown
+Logs Drilldown makes log exploration effortless with an intuitive, no-query interface that automatically turns your log data into interactive visualizations - no LogQL required.
-
-FusionReactor’s **Logs Drilldown** makes log exploration effortless with an intuitive, no-query interface. It automatically turns your log data into interactive visualizations, enabling engineers of all experience levels to investigate and gain insights-no LogQL required.
-
-
-
-
-
-## Key features
-
-
-- Easily find logs and log volumes across all your services.
-
-- Effortlessly filter logs by labels, fields, or patterns.
-
-- Drill into data using volume trends and text patterns.
-
-- Uncover related logs and track changes over time.
-
-- Browse auto-generated visualizations tailored to your log data.
-
-- Skip the LogQL - no queries required.
-
-
-
-## **Getting Started with Logs Drilldown**
-
-1. **Open Logs Drilldown**
-
- * From the FusionReactor Cloud dashboard, go to: **Explore → Logs**
- * This opens the **Overview page** showing time series and log visualizations for all services in your selected Loki data source.
-
- > ⚠️ If no services appear, make sure a Loki data source is connected.
-
-
-2. **Select a data source**
-
- * At the top left, choose your **Loki data source** (if you have more than one).
-
- > Note: Logs Drilldown only supports **Loki**.
-
-
-
-3. **Set a time range**
-
- You can adjust the time range in two ways:
-
- * Use the **time range picker** (top right).
- * Click and drag on a **time series chart** to zoom into a specific time window.
-
-4. **Find a service**
-
- * Browse services by **log volume**
- * Or use the **Search Services** field to find a service by name
- * To view services by label instead, click **+ Add label**, then choose or search for a label
-
-
-
-5. **View logs for a service**
-
- * Click **Show logs** on any service chart
- → This opens the **Logs tab** for that service, showing raw logs
-
-
-6. **Explore labels**
-
- * Click the **Labels** tab to see log volume by label
- * To drill into a specific label, click **Select** to view volume by label value
-
- > Useful for understanding trends across environments, components, etc.
-
- !!! info "Learn more"
- [Labels](https://grafana.com/docs/grafana/latest/explore/simplified-exploration/logs/labels-and-fields/)
-
-
-
-7. **Explore fields**
-
- * Go to the **Fields** tab to view logs grouped by field
- * Click **Select** next to any field to explore details like frequency or trends
-
- !!! info "Learn more"
- [Fields](https://grafana.com/docs/grafana/latest/explore/simplified-exploration/logs/labels-and-fields/)
-
-8. **Explore log patterns**
-
- * Click the **Patterns** tab to see automatically detected log patterns
- * You can:
-
- * Focus on useful patterns
- * Hide noisy or repetitive ones
-
- > Great for identifying common issues or anomalies in log content
-
- !!! info "Learn more"
- [Patterns](https://grafana.com/docs/grafana/latest/explore/simplified-exploration/logs/patterns/)
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/explore-logs/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/explore-metrics.md b/docs/Data-insights/Features/explore-metrics.md
index eca660f..b19c52e 100644
--- a/docs/Data-insights/Features/explore-metrics.md
+++ b/docs/Data-insights/Features/explore-metrics.md
@@ -1,108 +1,7 @@
-# Overview
+# Metrics Drilldown
-FusionReactor’s **Metrics Drilldown** offers a seamless, query-free way to explore Prometheus-compatible metrics. With just a few clicks, you can uncover related metrics and insights - no need to write a single PromQL query.
+Metrics Drilldown offers a query-free way to explore Prometheus-compatible metrics and uncover related insights with just a few clicks - no PromQL required.
-
-
-
-## Key features
-
-- Segment metrics by labels to quickly spot anomalies and pinpoint issues.
-
-- Auto-visualize metric types (e.g., gauges vs. counters) with no manual configuration.
-
-- Discover related metrics to broaden context and deepen analysis.
-
-- Pivot seamlessly to related telemetry, including logs, for end-to-end visibility.
-
-## Getting started
-
-At the top center of the screen, you'll see a welcome panel:
-
-
-
-
-* Click the **Let’s start!** button to open the **Explore > Metrics** interface.
-* A dynamic grid of metric panels is displayed, each representing a specific Prometheus metric (e.g., apiserver_client_certificate_expiration_seconds_count, apiserver_audit_event_total, apiserver_delegated_authz_request_duration_seconds).
- 
-* Below the launch panel, you’ll see a list of your **recently run metric queries** for quick re-access.
-
-### Search & filter metrics
-
-Use search and filters to quickly narrow down the metrics you want to investigate - by system, service, or time frame. This helps you focus on what matters most.
-
-
-
-To filter:
-
-* Use the Filter by label values dropdown to select specific services or tags.
-
-* Or type in the Search metrics box (e.g., type cpu), then press **Enter**.
-
-Matching metrics will appear. From here, you can dive deeper into your analysis.
-
-
-### Investigate the data
-
-Once you've filtered your metrics, it’s time to analyze the data for patterns or unusual behavior. Understanding your system’s normal (baseline) performance makes it easier to spot issues.
-
-To start:
-
-1. Review the metric panels and look for ones with noticeable changes.
-
- * Metrics with little variation (e.g., JVM Uptime) are typically less insightful.
-
- * Focus on dynamic and performance-critical metrics (e.g., CPU Usage, Heap Memory Used, Active JDBC Connections, or Request Throughput) to uncover system trends and potential issues.hat show clear trends.
-
-2. Click **Select** on a metric to view it in more detail.
-
-3. Adjust the time range using the time picker in the top right if needed.
-
-4. Use the **Breakdown** and **Related metrics** tabs:
-
- * **Breakdown:** Visualizes each label-value pair for the selected metric. You can drill down further or add filters directly.
- * **Related metrics:** Lists similar metrics based on keywords. You can continue your analysis from here.
-
- 
-
-### Open a metric in Explore
-
-Explore lets you interact with your data in real time. You can build, test, and refine queries without needing to create a dashboard. If your data source supports it, you’ll see results in both graph and table views-perfect for quick and detailed analysis.
-
-To drill deeper into a specific metric using Explore:
-
-1. Click **Select** on the metric panel you want to investigate in more detail.
-
-2. Once the panel expands, click the explore icon in the bottom-right corner of the graph.
-
-
- 
-
-3. This opens the metric in **Explore** view, where you’ll see the full query.
-
-4. From here, you can modify the query, change the time range, and switch between graph and table views to further analyze the data.
-
- 
-
-Explore is great for experimenting with queries and uncovering deeper insights-without needing to build a full dashboard.
-
-### Add metrics visualization to a dashboard
-
-1. At the top of the **Explore** page, click **Add to dashboard**.
-
-2. Choose one of the following:
-
- * New dashboard - to create a new one
-
- * Existing dashboard - and pick one from the list
-
-3. Click **Open dashboard** to view it.
-
-4. Click **Save dashboard** in the top-right corner.
-
-5. Give your dashboard a name and description, choose a folder (if needed), and click **Save**.
-
- 
-
-!!! info "Learn more"
- [Metrics](https://grafana.com/docs/grafana/latest/explore/simplified-exploration/metrics/)
\ No newline at end of file
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/explore-metrics/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/explore-traces.md b/docs/Data-insights/Features/explore-traces.md
index ae37c98..33cd314 100644
--- a/docs/Data-insights/Features/explore-traces.md
+++ b/docs/Data-insights/Features/explore-traces.md
@@ -1,41 +1,7 @@
-## Overview
+# Traces Drilldown
-Distributed traces enable you to monitor and troubleshoot applications by following the path of requests as they travel through various services. Each trace captures detailed information about a request-such as timing, errors, and service interactions - providing valuable context to help you diagnose performance issues or pinpoint failures.
+Traces Drilldown provides intuitive visualizations of distributed trace data, helping you identify bottlenecks, latency spikes, and service dependencies across your services.
-FusionReactor's **Traces** feature enhances your observability workflow by offering intuitive visualizations of trace data collected by Grafana Tempo. It helps you quickly identify bottlenecks, latency spikes, and service dependencies, giving you actionable insights directly from your distributed traces.
-
-
-
-
-## Key features
-
-Using Traces in Explore, you can:
-
-- Leverage Rate, Errors, and Duration (RED) metrics derived directly from trace data to investigate and understand application behavior.
-
-- Identify related issues and monitor how they evolve over time for proactive troubleshooting.
-
-- Explore your data through automatically selected visualizations tailored to the metric type and structure.
-
-- Get powerful insights without the need to write TraceQL queries - everything works out of the box.
-
-## Get started
-
-Most investigations follow a few core steps:
-
-1. **Select the primary signal**: Begin by identifying the key signal to focus your investigation.
-
-2. **Choose a metric**:
- Select from Rate, Errors, or Duration (RED metrics) to guide your analysis.
-
-3. **Apply filters**:
- Refine your view by filtering on relevant labels or dimensions.
-
-4. **Drill down into the issue**:
- Use the structural view or trace list to explore detailed trace data and uncover the root cause.
-
-
-
-### Need a worked example?
-
-If you want a step-by-step example of investigating the source of errors, [click here](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/traces/get-started/#example-investigate-source-of-errors) to see a detailed walkthrough using real trace data.
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/explore-traces/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/explore.md b/docs/Data-insights/Features/explore.md
index 1f182fd..fb8940f 100644
--- a/docs/Data-insights/Features/explore.md
+++ b/docs/Data-insights/Features/explore.md
@@ -1,176 +1,7 @@
# Explore
-🔎**Find it**: **FusionReactor** > **Explore**
+Explore lets you query and analyse all metrics, logs, and traces ingested to your cloud account, with flexible filtering and the ability to create custom data views.
-
-
-**Explore** allows you to query and analyse all metrics, logs and traces ingested to your cloud account. Create new data views and filter data in any way you require.
-
-!!! warning
- While with **Explore** you can technically search for any amount of data within your cloud account, there are strict execution times on queries that will restrict performance heavy queries.
-
-## Datasource selection
-
-Within **Explore** there are three datasource configures. They are accessed using the dropdown located to the left of the screen. The default datasource is **Metrics**.
-
-
-
-- Metrics will contain any metric sent from a FusionReactor agent, plus some additional metrics created within our ingest engine.
-- Traces will contain any slow or error transactions sent from a FusionReactor agent, requests viewed in the recent or running tabs of the server view will not appear here as they are not ingested.
-- Logs will contain any logs sent to FusionReactor, either from a FusionReactor agent or log shipper.
-
-!!! note
- Going forward we will allow ingest for traces and metrics from a non FusionReactor agents, however at this time this feature is unavailable.
-
-## Metric queries
-
-🔎**Find it**: **FusionReactor** > **Explore** > **Metrics**
-
-To explore metrics, use the **Metric** browser.
-
-
-
-Within the **Metric** browser you can:
-
-- Select one or more metrics to view.
-
-- Filter metrics by any label, such as **instance**, **group** or **application**.
-
-- Execute functions such as **Sum**, **Count**, or **Avg** on metrics.
-
-- Compare metrics by using mathematical functions.
-
-- Combine multiple queries in a single view.
-
-- View data as various chart types, or as raw data in a table.
-
-The metrics browser will create data views for you using [Promql](https://prometheus.io/docs/prometheus/latest/querying/basics/).
-
-Using Promql directly you can create powerful and complex queries to get the most out of your FusionReactor data.
-
-## Trace queries
-
-🔎**Find it**: **FusionReactor** > **Explore** > **Traces** > **Search**
-
-To explore traces we advise using the **Search** feature.
-
-
-
-Within search, you can specify:
-
-|Type | Description |
-|--------------|-----------|
-| Service Name | Instance from which the trace originates.|
-| Span Name | The URL or action of a transaction.|
-| Tag | A label applied to a trace, for example ```txnId``` or ```status.code```. A full list of tags can be searched within the input field.|
-| Min Duration | The minimum duration of a transaction. |
-| Max Duration | The maximum duration of a transaction. |
-|Limit | How many results you wish to view.|
-
-You can view the trace information by clicking on the trace ID, which will open a window on the right of the screen.
-
-
-
-## Log queries
-
-🔎**Find it**: **FusionReactor** > **Explore** > **Logs**
-
-To explore logs, use the **Logs** browser.
-
-The **Logs** browser allows you to filter and view any ingested logs.
-
-
-
-
-
-The log browser lets you:
-
-- Filter logs by labels like **job**, **filename** or **instance**.
-
-- Perform calculations like **Sum**, **Count**, or **Avg** to extract metrics from logs.
-
-- Combine multiple queries in one view.
-
-- Display data as charts or raw tables.
-
-The browser automatically builds log queries and generates [LogQL](https://grafana.com/docs/loki/latest/logql/) for you.
-
-You can also use **Explore** to run custom LogQL queries.
-
-!!! info
- LogQL, developed by Grafana Labs, is a query language for filtering, searching, and generating metrics from log data.
-
-
-
-### LogQL examples
-#### Search for logs with a specific job
-
-!!! example
- ````{job="job1"}````
-
-
-
-#### Search for specific filename
-
-!!! example
- ````{filename=~"request"}````
-
-
-
-#### Search for logs with a job using wildcard
-
-!!! example
- ````{job=~"job.*"}````
-
-#### Search for any stdout or stderr logs for any jobs matching the wildcard
-
-!!! example
- ````{job=~"job.*",filename=~"std.*"}````
-
-
-#### Query for the volume of jobs per job and instance
-
-!!! example
- ````sum(count_over_time({job=~".+"}[5m])) by (job,instance)````
-
-#### Query for the top IP addresses triggering requests in FusionReactor
-
-!!! example
- ````topk(10,sum by (clientAddress)(rate({filename="request"} | logfmt | line_format "{{.clientAddress}}" | __error__="" [1m])))````
-
-#### Query nginx for the top IP address hitting the load balancer
-
-!!! example
- ````topk(10,sum by (remote_address)(rate({filename="/opt/access.log"} | logfmt | line_format "{{.remote_address}}" | __error__="" [1m])))````
-
-#### Search all logs for the text exception
-
-!!! example
- ````{ job=~".+"} |= "Exception"````
-
-#### Process the request log for top hit page URLs
-
-!!! example
- ````sum by (url)(rate({filename="request"} | logfmt | line_format "{{.url}}" | __error__="" [10s]))````
-
-#### Graph the number of error or exception error lines
-
-!!! example
- ````sum by (job) (count_over_time({job=~"store-.*"} |= "error" != "exception" [5m]))````
-
-
-#### Process the avg CPU time per page URL
-
-!!! example
- ````topk(10, sum by (url)(avg_over_time({ filename="request"} | logfmt | __error__="" | unwrap cpuTime[5m])))````
-
-
-#### Graph previous crashes caused by OutOfMemory errors
-
-!!! example
- ````sum by (job) (count_over_time({job=~".+"} |= "java.lang.OutOfMemory" [1m]))````
-
-___
-
-!!! question "Need more help?"
- Contact support in the chat bubble and let us know how we can assist.
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/explore/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Data-insights/Features/images/Servers/new-servers.png b/docs/Data-insights/Features/images/Servers/new-servers.png
new file mode 100644
index 0000000..e3c0459
Binary files /dev/null and b/docs/Data-insights/Features/images/Servers/new-servers.png differ
diff --git a/docs/Data-insights/Features/overview.md b/docs/Data-insights/Features/overview.md
index 6de6780..5f50b6a 100644
--- a/docs/Data-insights/Features/overview.md
+++ b/docs/Data-insights/Features/overview.md
@@ -1,122 +1,7 @@
# Overview
-The **Overview** page is your observability dashboard at a glance. It gives you an immediate, high-level summary of your entire environment - services, servers, applications, alerts, anomaly detection, and usage - all in one place.
+The **OpsPilot Overview** page is your observability dashboard at a glance. It gives you an immediate, high-level summary of your entire environment - services, servers, applications, alerts, anomaly detection, and usage - all in one place.
-## Active account view
-
-Once your environment is sending data, the Overview page shows a full observability summary.
-
-
-
-### Services
-
-The **Services** section displays key performance metrics aggregated across all your monitored services for the last hour.
-
-| Metric | Description |
-|---|---|
-| **Overview (All Service Avg)** | Average latency across all services |
-| **P95** | 95th percentile latency |
-| **P99** | 99th percentile latency |
-| **Error Rate** | Percentage of requests resulting in errors |
-| **Throughput** | Number of requests per second |
-| **Total Time** | Cumulative request time |
-
-#### Services by latency
-
-Below the summary metrics, **Services by latency** lists your top 10 services ranked by average latency over the last hour. Each service card shows:
-
-- **Avg Latency**
-- **P95 / P99**
-- **Alerts** count
-- **Throughput**
-
-Click any service card to drill into that service's detailed performance data.
-
-### Servers
-
-The **Servers** section provides a summary of all servers running a FusionReactor agent, including:
-
-- **Total Servers**
-- **Avg Request Duration**
-- **Error Count**
-- **Throughput**
-- **CPU Usage**
-- **Memory Usage**
-
-**Servers by latency** lists your top servers ranked by average latency, with CPU and memory breakdowns per server.
-
-Click **Servers ->** to go to the full [Servers](/Data-insights/Features/servers/) view.
-
-### Applications
-
-The **Applications** section summarises all monitored applications, showing:
-
-- **Total Applications**
-- **Avg Request Duration**
-- **Error Count**
-- **Throughput**
-
-**Applications by latency** lists your top applications ranked by average latency.
-
-Click **Applications ->** to go to the full [Applications](/Data-insights/Features/applications/) view.
-
-### Alerts
-
-The **Alerts** panel shows a live count of alerts grouped by state:
-
-| State | Description |
-|---|---|
-| **Firing** | Alerts currently breaching their threshold |
-| **Pending** | Alerts that have triggered but not yet confirmed |
-| **Recovering** | Alerts returning to a normal state |
-| **Normal** | Alert rules currently within threshold |
-
-Click **Alerts ->** to go to the full [Alerts](/Data-insights/Features/Alerting/Active-alerts/) view.
-
-### Anomaly Detection
-
-The **Anomaly Detection** panel shows a live count of anomaly alerts by state, mirroring the same Firing / Pending / Recovering / Normal breakdown.
-
-Click **Anomaly Detection ->** to go to the full [Anomaly Detection](/Data-insights/Features/Anomaly-Detection/ADoverview/) view.
-
-### Usage
-
-The **Usage** panel shows your current consumption against your plan limits for the current pay period:
-
-| Signal | Description |
-|---|---|
-| **Logs** | Log volume ingested (MB / GB) |
-| **Traces** | Trace volume ingested (MB / GB) |
-| **Metrics** | Active metric series |
-| **Agents** | Number of connected FusionReactor agents |
-| **OpsPilot** | OpsPilot AI tokens consumed |
-
-A progress bar indicates how much of your plan allowance has been used.
-
-## No Data view
-
-If your account has no data yet, each section of the Overview displays a **Get Started** prompt to guide you through setup:
-
-
-
-| Section | Prompt |
-|---|---|
-| **Services** | You'll need an API key to instrument your application with OpenTelemetry. |
-| **Servers** | Install FusionReactor on your servers to start monitoring. You'll need a license key. |
-| **Applications** | Install FusionReactor to monitor your applications. You'll need a license key. |
-| **Alerts** | Configure alert rules to monitor your infrastructure. |
-| **Anomaly Detection** | Enable anomaly detection to automatically detect unusual behavior in your data. |
-
-The **Servers** and **Applications** prompts also display your **FusionReactor Cloud license key** directly on the page so you can copy it for use during agent installation.
-
-The **Usage** panel shows your plan limits with all values at zero until data starts flowing (for example, `0 bytes / 27 GB` for Logs).
-
-Once data starts flowing in, the Overview automatically populates with your live metrics and telemetry.
-
-!!! tip "Getting started"
- Follow the prompts on the Overview page to install the right agent or instrumentation for your stack, then return to the Overview to see your data appear.
-
----
-
-!!! question "Need more help?"
- Contact support in the chat bubble and let us know how we can assist.
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Data-insights/Features/overview/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Getting-started/Tutorials/new-ui-faq.md b/docs/Getting-started/Tutorials/new-ui-faq.md
index 1753e07..ac0cb61 100644
--- a/docs/Getting-started/Tutorials/new-ui-faq.md
+++ b/docs/Getting-started/Tutorials/new-ui-faq.md
@@ -1,84 +1,7 @@
# New UI FAQ
-Frequently asked questions about finding features in the new OpsPilot UI.
+Frequently asked questions about finding features in the OpsPilot UI.
----
-
-## Where do I find request history?
-
-Request history is available through the **UI Tunnel** tab on a server. This connects directly to the FusionReactor on-premise agent UI, where you can access the full **Requests** section including history, slow requests, and error history.
-
-Navigate to **Servers**, select a server, then open the **UI Tunnel** tab.
-
----
-
-## Where do I view running requests?
-
-**Live / real-time data**
-Use the **UI Tunnel** tab on a server, then navigate to **Requests > Activity** to see all currently running requests in real time.
-
-
-
-
-
----
-
-## Where do I view metrics graphs?
-
-Metrics graphs are available in two places:
-
-- **Metrics tab** on a server - select a server, open the **Metrics** tab, and use the time-frame selector to view metric graphs over your chosen period.
-
-
-
-
-- **UI Tunnel tab** on a server - for live, agent-level metrics graphs directly from FusionReactor, navigate to **Metrics > Web Metrics**.
-
----
-
-## How do I set up alerting?
-
-The new alerting system is built on Grafana Alertmanager and is more powerful than the previous system. Alert rules must be placed in a folder and assigned to an evaluation group.
-
-!!! info "Learn more"
- [Alerting overview](/Data-insights/Features/Alerting/Alerts-overview/) for a full walkthrough of rules, contact points, and notification policies.
-
----
-
-## How do I purchase a subscription?
-
-To purchase a subscription, navigate to **Administration** in the left-hand menu and click the gear icon on either the **Cloud Trial** or **On-Premise Subscription** box, then select **Manage Settings**.
-
-!!! info "Learn more"
- [Cloud - Purchasing a Subscription](/Admin-and-data/Billing/Cloud/overview/#purchasing-a-subscription)
-
- [On-Premise - Purchasing a Subscription](/Admin-and-data/Billing/On-Premise/billing/#purchasing-a-subscription)
-
----
-
-## How do I update my credit card details?
-
-To update your credit card or billing information:
-
-1. Go to **Administration > Invoices**.
-2. In the **Upcoming Bill** panel on the right, click **Edit Details**.
-3. Update your card or billing information and save your changes.
-
-!!! info "Learn more"
- [Invoices](/Admin-and-data/invoices/) for full details on managing your invoices and billing.
-
----
-
-## The FR tunnel isn't working
-
-If the UI Tunnel tab is not connecting to your FusionReactor instance, the most common cause is a blocked port.
-
-**Ensure port 443 is open** on the server running FusionReactor. The tunnel uses outbound HTTPS (port 443) to establish the connection.
-
-!!! info "Learn more"
- [Required endpoints](/Getting-started/Tutorials/Common-issues/endpoints/) for the full list of hostnames and ports that must be accessible.
-
----
-
-!!! question "Need more help?"
- Contact support in the chat bubble and let us know how we can assist.
+!!! info "This feature is part of OpsPilot"
+ This functionality is available in **OpsPilot**, our cloud-native observability platform.
+ [View the OpsPilot documentation](https://docs.opspilot.com/Getting-started/Tutorials/new-ui-faq/) or [start a free trial](https://app.opspilot.com).
diff --git a/docs/Latest-updates/release-notes.md b/docs/Latest-updates/release-notes.md
index 76b00cb..674a9b3 100644
--- a/docs/Latest-updates/release-notes.md
+++ b/docs/Latest-updates/release-notes.md
@@ -31,7 +31,7 @@
| New Feature | Add option to add query parameters to request metrics' route label/attribute |
| Improvement | Update automatic installer (FRAM) to use correct debug library for Mac ARM64. |
-## 2025.2.1 - 3rd feb. 2026
+## 2025.2.1 - 3rd Feb. 2026
| Issue Type | Summary |
|------------|-------------------------------------------------------------------------------------------------|
@@ -53,10 +53,10 @@
| Improvement | Update the JRE bundled with FRAM. |
-!!! Warning
+!!! warning
If you are upgrading to **FusionReactor 2025.2** and are already using **OTel**, FusionReactor will now automatically use any existing configured endpoints. To ensure you continue receiving data in **FusionReactor Cloud** while using an OTel Collector, you must update your `collector.yaml` configuration file. Please refer to the [documentation linked here](https://docs.fusionreactor.io/Monitor-your-data/FR-Agent/Configuration/OTel-shipping-config/) for the required changes.
-## 2025.1.0 - 3rd March 2025
+## 2025.1.0 - 3rd Mar. 2025
| Issue Type | Summary |
@@ -287,7 +287,7 @@
| FR8309 | Improvement | In web request details, service time has been renamed to API time |
| FR8307 | Improvement | Included CFHTTP in the request API time |
-##8.7.5
+## 8.7.5
| Key | Issue Type | Summary |
| --- | --- | --- |
| FR8301 | Improvement | Added the ability to preview Headers in the transaction history summary views via a settings page |
diff --git a/docs/UI/Screenshot 2026-03-20 114507.png b/docs/UI/Screenshot 2026-03-20 114507.png
new file mode 100644
index 0000000..d3842d2
Binary files /dev/null and b/docs/UI/Screenshot 2026-03-20 114507.png differ
diff --git a/docs/UI/image.png b/docs/UI/image.png
new file mode 100644
index 0000000..622b344
Binary files /dev/null and b/docs/UI/image.png differ
diff --git a/mkdocs.yml b/mkdocs.yml
index 94a0dec..93f5198 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -54,7 +54,6 @@ nav:
- Downloads: Latest-updates/Downloads.md
- TUTORIALS & WALKTHROUGHS:
- Overview: Getting-started/Tutorials/Overview.md
- - New UI FAQ: Getting-started/Tutorials/new-ui-faq.md
- Performance analysis:
- Post-crash troubleshooting: Getting-started/Tutorials/crash-troubleshoot-onprem.md
- Getting-started/Tutorials/resolve-slow-queries.md
@@ -347,6 +346,7 @@ nav:
- Troubleshooting/storing-fr-logs.md
- Troubleshooting/OP-setting-up-reports.md
- OpsPilot UI:
+ - New UI FAQ: Getting-started/Tutorials/new-ui-faq.md
- Overview: Data-insights/Features/overview.md
- Servers: Data-insights/Features/Explore-servers.md
- Applications: Data-insights/Features/applications.md