> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/monitoring.md). # Monitoring The Monitoring tab provides real-time and historical observability for your Oracle database service. Metrics are grouped into **OS Metrics**, **DB Metrics**, and **Performance Insights**. By default, graphs show metrics for the current primary node; for HA/RR/DR services you can select a specific node. *** ## What time range and granularity options are available? **Preset intervals:** 1h, 3h, 6h, 12h, 24h (default: 1h). Graphs display averaged values over the selected period. **Custom range:** 1. Select **Custom**. 2. Choose the desired start date and time. 3. Click **Apply**. **Granularity** controls the interval between data points. Options: 1m, 5m, 15m, 30m, 1h, 6h, 12h, 1d. By default, Tessell auto-calculates granularity to return approximately 121 data points per chart. The minimum granularity is 1 minute; a maximum of 1,441 data points are returned per query. *** ## What interactive features are available on each monitoring chart? | Feature | How to use | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | **Full-screen view** | Click the full-screen icon (top-right of graph) to open an expanded view with 1m/5m/15m/30m/1h granularity options and Avg/Min/Max statistics | | **Zoom** | Click and drag over a section of the graph to zoom in for granular analysis | | **Drag and explore** | Use the crosshair cursor to pan across a portion of the graph | | **Download** | Click the menu icon (top-right) → choose **SVG/PNG** for an image or **CSV** for tabular data | Use the **refresh button** (top-right of the Monitoring tab) to manually refresh all metrics. Use the **search bar** to locate a specific metric chart by name. *** ## What does the Service Availability graph show? The Service Availability graph displays database service uptime, with green indicating availability and gray representing unavailability. Data is updated every five minutes. > **Note:** This graph represents the availability of the current primary node. For HA services, select a specific node using the node selector at the top of the Monitoring tab. *** ## What OS metrics does the Monitoring tab provide? The OS Metrics section graphs the following operating system metrics (default interval: 10 minutes): | Metric | What it shows | | -------------------------------- | ------------------------------------------------------------------------------------- | | **CPU Usage** | CPU utilisation as a percentage. Shows latest used % value. | | **System load average** | Load average over 1m, 5m, and 15m (three lines on same graph). | | **Memory Usage** | Used and available memory in GiB (two lines). | | **Swap Usage** | Used and free swap space in GiB (two lines). | | **Network Usage** | Sent and received network data in MiB/s (two lines). | | **Filesystem: Root** | Used and free root filesystem space in GiB. | | **Filesystem: Data** | Used and free data filesystem space in GiB. | | **Filesystem: Archive** | Used and free archive filesystem space in GiB. | | **Filesystem: DB Software** | Used and free filesystem for Oracle binaries in GiB. | | **Throughput: Data disk (KiB)** | Read and write throughput on the data disk in KiB. | | **Throughput: Archive disk** | Read and write throughput on the archive disk in KiB. | | **IOPS: Data disk (Per Second)** | Read and write IOPS on the data disk. | | **IOPS: Archive disk** | Read and write IOPS on the archive disk. | | **Latency: Data disk** | Read and write latency on the data volume in seconds. | | **Latency: Archive disk** | Read and write latency on the archive volume in seconds. | | **Queue Depth: Data disk** | In-flight I/O operations on the data volume. High values indicate I/O bottlenecks. | | **Queue Depth: Archive disk** | In-flight I/O operations on the archive volume. High values indicate I/O bottlenecks. | | **Top Processes by CPU** | Table: PID, process name, average CPU % (current data only, not historical). | | **Top Processes by Memory** | Table: PID, process name, average memory % (current data only, not historical). | *** ## What Oracle DB metrics does the Monitoring tab provide? The DB Metrics section graphs the following Oracle database metrics (default interval: 10 minutes): | Metric | What it shows | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | **Session Stats** | Count of active users, inactive users, and active background processes. | | **Disk IO** | Read and write operations per second. | | **PGA Memory Stats** | Allocated, freeable, maximum, and used PGA memory in MiB (four lines). | | **SGA Stats** | Used, free, and total SGA memory in GiB (three lines). | | **Blocking Sessions** | Number of blocking sessions. | | **Sessions Utilization** | Maximum limit vs. current utilisation of sessions (two lines). | | **Process Utilization** | Maximum limit vs. current utilisation of processes (two lines). | | **Transactions Utilization** | Maximum limit vs. current utilisation of transactions (two lines). | | **Wait times** | Wait time in seconds across administrative, application, commit, concurrent, configuration, network, scheduler, and system categories. | | **Activity** | Counts of query executions, query parses, user commits, and user rollbacks. | | **FRA Utilization** | Percentage of the allocated Fast Recovery Area currently in use. | *** ## How does Performance Insights work and how do I enable it? Performance Insights is a database load analysis tool that identifies bottlenecks by measuring the **Average Active Sessions (AAS)** — the average number of sessions concurrently active on the database. **Prerequisites:** Create a **Monitoring Performance Insights Infrastructure** in the **Monitoring Performance Insights Infrastructure** application under the **DB Services** app family. After the infrastructure is deployed, enable Performance Insights per service either at provisioning time or from the [Settings tab](/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/settings.md). **Key concepts:** | Concept | Description | | ------------------ | ---------------------------------------------------------------------------------------- | | **DBLoad** | The key metric — collected every second and expressed as AAS | | **Active session** | A session that has submitted work and is either running on CPU or waiting for a resource | | **AAS** | Total sessions sampled divided by number of samples in the time period | **Top Dimensions** — dimensions of database load within a timeframe: | Dimension | Description | | ----------------- | ---------------------------------------------------------------- | | **Top Waits** | Wait events contributing most to DB load | | **Top SQLs** | Top SQL queries by DB load (masked and grouped by type) | | **Top Hosts** | Client hosts contributing most to DB load | | **Top Users** | Database users contributing most to DB load | | **Top Databases** | Databases contributing most to DB load (multi-database services) | ### Steps to view Performance Insights 1. Click **View Detailed Insights** on the Monitoring tab. 2. Select a time interval: 1h, 3h, 6h, 12h, or 24h (default: 1h). 3. For a custom range, select **Custom**, choose a date and time, and click **Apply**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tessell.com/tessell/database-engines/tessell-for-oracle/db-services/my-services/database-service-home-page/monitoring.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.