> ## Documentation Index > Fetch the complete documentation index at: https://docs.germainux.com/llms.txt > Use this file to discover all available pages before exploring further. # Oracle Analytics Cloud Observability > Monitor the availability, performance, user experience, usage, and operational health of Oracle Analytics Cloud (OAC) with GermainUX. Components [`Engine`](/main/germain-ux-engine) [`JS Profiler`](/main/germain-ux-js-profiler) [`Mobile`](/main/germain-ux-mobile-app) [`RPA Bot Recorder`](/main/germain-ux-rpa-bot-recorder) [`RUM JS`](/main/germain-ux-rum-js) Availability 2017.1 or later > **[Real User Experience Monitoring](#real-user-experience-monitoring)** > > Browser-based user experience > **[Session Replay](#session-replay)** > > Replaying workflow issues > **[Query Performance Analysis](#query-performance-analysis)** > > Usage Tracking query insights > **[Root Cause Analysis](#root-cause-analysis)** > > Linking experience to telemetry **Oracle Analytics Cloud Observability** Monitor the availability, performance, user experience, usage, and operational health of Oracle Analytics Cloud (OAC) with GermainUX. GermainUX combines Real User Monitoring, Session Replay, browser performance analysis, Oracle Analytics usage data, API monitoring, OCI metrics, synthetic transactions, and automated analytics to help teams identify issues affecting Oracle Analytics users, dashboards, analyses, workbooks, and queries. ## Real User Experience Monitoring Monitor how users experience Oracle Analytics Cloud in their browsers. Depending on the deployment method and authorized browser access, GermainUX can analyze: * User sessions * Page navigation * User interactions * Clicks * Dashboard activity * Analysis activity > **Show all 11** > > * Page and interaction response time > * Browser errors > * Network requests > * Failed requests > * User workflows This provides visibility into the experience of individual users as well as trends across the OAC user population. ## Session Replay Use GermainUX Session Replay to investigate user activity and issues affecting Oracle Analytics workflows. Analyze sessions involving: * Slow dashboards * Slow analyses * Failed navigation * Errors * Dead clicks * Rage clicks > **Show all 10** > > * Error clicks > * Repeated actions > * Failed workflows > * Browser issues Session Replay can help support and engineering teams understand what occurred before an issue was reported. ## Dashboard and Analysis Performance Monitor the experience of users accessing Oracle Analytics content. Analyze: * Dashboard response time * Analysis response time * Workbook activity * Navigation performance * User interaction time * Network-request duration * Failed requests * Browser processing Use this information to identify which content, users, workflows, or environments are most affected by performance degradation. ## Query Performance Analysis When Oracle Analytics Usage Tracking is enabled and made available to GermainUX, analyze query-level activity. Depending on the available Usage Tracking data, this can include: * Logical queries * Physical queries * Query response time * Query frequency * Rows processed * User > **Show all 9** > > * Session > * Dashboard or analysis context > * Query timing Use this information to identify: * Slow queries * Frequently executed queries * Query-performance bottlenecks * Expensive analyses * Changes in query behavior * Users or workloads associated with performance degradation ## Usage and Adoption Analysis Analyze how Oracle Analytics Cloud is used. Depending on the monitoring sources enabled, analyze: * Active users * User sessions * Frequently accessed content * Dashboard usage * Analysis usage * Query frequency * User engagement * Usage trends This helps teams understand both technical performance and adoption. ### Transaction Performance Comparison When analyzing a slow or failed Oracle Analytics Cloud transaction, use Comparison to compare its performance with another execution of the same transaction, such as the fastest, slowest, most recent, first seen, or last seen. Comparison can reveal: * Differences in execution time for the same Oracle Analytics Cloud operation * Which steps, dashboard loads, or queries caused the slowdown * Performance differences between successful and failed Oracle Analytics Cloud transactions * Errors or bottlenecks affecting analytics workflows * Potential root causes of transaction performance degradation This helps pinpoint why an Oracle Analytics Cloud transaction is slower or failing, identify the underlying bottlenecks, and accelerate resolution to improve analytics performance and user productivity. More details on [**Transaction Performance Comparison**](/main/4-analysis-dashboard.md#comparison-of-bad-vs-good). ## Oracle Analytics Cloud Metrics Oracle Analytics Cloud exposes operational metrics through Oracle Cloud Infrastructure Monitoring. When authorized access is available, GermainUX can collect and analyze applicable OAC metrics. Examples can include: * Query Capacity Usage * Data Source Connection Errors * Other metrics exposed by the configured OAC and OCI environment Use these metrics to identify capacity, workload, and connectivity conditions affecting Oracle Analytics. ## Data Source Connection Monitoring Oracle Analytics Cloud depends on databases and other data sources. GermainUX can help identify: * Data source connection failures * Slow connections * API failures * Database performance degradation * Network issues * Downstream dependency failures When GermainUX also monitors the underlying customer-controlled data source, OAC performance can be correlated with database and infrastructure telemetry. ## Oracle Analytics REST API Monitoring GermainUX Engine can monitor authorized Oracle Analytics Cloud REST APIs. Depending on the required use case and permissions, monitor: * API availability * Response time * HTTP status * Authentication * Failures * Expected responses Oracle Analytics Cloud provides REST APIs for system information and operations involving content such as datasets, data flows, workbooks, snapshots, and other supported resources. ## Data Flow and Dataset Monitoring When authorized OAC REST APIs or other approved monitoring sources expose the required information, GermainUX can monitor operational activity associated with: * Data flows * Dataset reloads * Run history * Latest execution * Execution status * Failures This can help identify background processing conditions affecting analytics availability or freshness. ## Browser Error Monitoring Detect browser-side issues affecting Oracle Analytics users, including: * JavaScript errors * Browser console errors * HTTP failures * Failed network requests * Resource-loading failures * Browser freezes Correlate errors with the affected user, session, page, interaction, and analytics workflow. ## Synthetic Monitoring Use GermainUX RPA Bot Recorder to proactively test important Oracle Analytics Cloud workflows. Examples include: * Login → Open Dashboard → Verify Dashboard * Open Dashboard → Select Filters → Run Analysis → Verify Results * Open Workbook → Execute Workflow → Verify Expected Content Synthetic monitoring can identify availability, performance, or functional problems before users report them. Use authorized test accounts and safe test workflows. ## Data Source Monitoring When GermainUX has authorized access to customer-controlled data sources used by Oracle Analytics Cloud, monitor them separately. Examples include: * Oracle Database * SQL Server * MySQL * Other supported databases * APIs * Network * Cloud infrastructure This provides additional context for Root Cause Analysis. ## Root Cause Analysis Correlate Oracle Analytics user experience with available technical telemetry. For example: | Symptom | Possible Cause | | - | - | | Slow Dashboard | **Slow Dashboard → Slow Query → Database Performance Degradation** | | Dashboard Failure | **Dashboard Failure → Data Source Connection Error** | | Slow User Interaction | **Slow User Interaction → High Query Capacity Usage** | | Dataset Not Updated | **Dataset Not Updated → Dataset Reload Failure** | This helps teams move from identifying an affected user or dashboard to understanding the likely technical cause. ## Automated Analytics GermainUX can help identify conditions such as: * Slow dashboards * Slow user interactions * Query performance degradation * Increased browser errors * Failed network requests * Data source connection errors > **Show all 11** > > * High query capacity utilization > * API failures > * Dataset or data-flow failures > * Usage anomalies > * Performance regressions ## Alerts and Automation When GermainUX detects a condition requiring attention, it can: * Send an alert * Notify users through a Watch * Generate a report * Trigger approved diagnostics * Execute approved automation ## Monitoring Boundary Oracle Analytics Cloud is a managed Oracle Cloud service. GermainUX does not directly monitor Oracle-managed OAC servers, operating systems, internal databases, or private service components unless Oracle exposes the required information through an authorized monitoring interface. Instead, GermainUX can combine: * Browser telemetry * Oracle Analytics Usage Tracking * Oracle Analytics REST APIs * OCI Monitoring metrics * Customer-controlled data sources * Synthetic transactions ## Get More Information GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your OAC applications and supporting environment. [Contact GermainUX Support](/main/support.md). ## Get Help > **[Contact GermainUX Support](/main/support.md)** > > The Germain Team can help you set this up. > **Can't find what you need?** > > Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing. The content of this document is proprietary to GERMAIN SOFTWARE. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.