Skip to main content
ComponentsEngineJS ProfilerMobileRPA Bot RecorderRUM JS
Availability2017.1 or later

24. Configure Alerts and Watches

Conditions that need attention

25. Configure Dashboards

Build views for teams

26. Validate the Configuration

Verify monitoring is working

Troubleshooting

Resolve common OAC issues
Configure Monitoring for Oracle Analytics Cloud Configure GermainUX to analyze Oracle Analytics Cloud user experience, dashboards, queries, usage, APIs, OCI metrics, synthetic workflows, and supporting data sources.

​
1. Configure User Experience Monitoring

Configure the browser monitoring profile associated with Oracle Analytics Cloud. Depending on the authorized monitoring scope, analyze:

​
2. Configure Session Replay

Enable Session Replay when authorized. Configure applicable:
  • Session timeout
  • Recording duration
  • User exclusions
  • IP exclusions
  • Privacy controls
  • Sensitive content exclusions
Global Session Replay settings are available under: Germain Workspace > Settings > System > UX and Session Replay Settings

​
3. Configure Privacy

Configure appropriate masking, anonymization, and exclusions. Protect:
  • Authentication information
  • Passwords
  • Tokens
  • Personal information
  • Sensitive analytics content
  • Restricted business data
  • URL parameters containing identifiers
Validate privacy controls before broad production deployment.

​
4. Configure User Identification

When authorized user identity is available, configure GermainUX to associate activity with the appropriate OAC user. This enables analysis by:
  • User
  • Session
  • Department or organization when available
  • Dashboard
  • Analysis
  • Workflow
Do not collect user attributes that are unnecessary for monitoring.

​
5. Configure Dashboard and Analysis Monitoring

Identify critical Oracle Analytics content. Examples include:
  • Executive dashboards
  • Operational dashboards
  • Financial analytics
  • Sales analytics
  • Customer analytics
  • Regulatory reports
  • Critical analyses
  • Workbooks
Configure monitoring so that user activity can be analyzed by the relevant content when identifiable from the available telemetry.

​
6. Configure User Interaction Monitoring

Analyze important user actions such as:
  • Open dashboard
  • Open analysis
  • Open workbook
  • Navigate
  • Apply filter
  • Change prompt
  • Drill down
  • Refresh
  • Execute query
  • Export
  • Other critical interactions
Exact interaction visibility depends on the browser telemetry available in the deployed OAC version.

​
7. Configure Click Monitoring

Analyze:
  • Standard clicks
  • Dead clicks
  • Error clicks
  • Rage clicks
Use these signals to identify:
  • Unresponsive controls
  • Failed navigation
  • Repeated user attempts
  • Browser errors
  • User friction

​
8. Configure Browser Performance

Analyze:
  • Page response time
  • Interaction response time
  • Browser processing
  • Network-request duration
  • Failed requests
  • Resource-loading performance
Compare performance by:
  • User
  • Session
  • Dashboard
  • Browser
  • Device
  • Geography
  • Time period

​
9. Configure Browser Error Monitoring

Monitor:
  • JavaScript errors
  • Browser console errors
  • HTTP failures
  • Failed network requests
  • Resource-loading failures
Correlate errors with the affected OAC session and workflow.

​
10. Configure Usage Tracking

When Oracle Analytics Usage Tracking is available, configure GermainUX to analyze the required Usage Tracking tables. Analyze available information such as:
  • User
  • Session
  • Query
  • Query start time
  • Query duration
  • Logical query
  • Physical query
  • Rows processed
  • Query status

​
11. Configure Query Performance Analysis

Use Usage Tracking information to identify:
  • Slow queries
  • Frequently executed queries
  • High-volume queries
  • Query performance regressions
  • Queries associated with slow dashboards
  • Queries associated with reported user issues
Analyze query performance over time to establish expected behavior.

​
12. Configure Usage and Adoption Analysis

Use browser telemetry and Usage Tracking to analyze adoption. Measures can include:
  • Active users
  • Sessions
  • Dashboard usage
  • Analysis usage
  • Query count
  • User engagement
  • Usage frequency
Analyze usage trends across appropriate populations and time periods.

​
13. Configure OCI Metrics — Optional

When OCI Monitoring access is configured, collect applicable Oracle Analytics Cloud metrics. Examples can include:
  • Query Capacity Usage
  • Data Source Connection Errors
Use the metrics actually exposed by the configured OAC environment.

​
14. Configure REST API Monitoring — Optional

Configure approved OAC REST endpoints. Depending on the use case, configure:
  • Endpoint
  • HTTP method
  • OAuth authentication
  • Headers
  • Timeout
  • Expected HTTP status
  • Response validation
  • Monitoring frequency
Use read-only operations whenever they satisfy the monitoring requirement.

​
15. Configure Dataset Monitoring — Optional

When supported OAC APIs expose the required information, monitor dataset reload activity. Analyze:
  • Latest reload
  • Reload history
  • Execution status
  • Failure
  • Duration when available

​
16. Configure Data Flow Monitoring — Optional

When supported OAC APIs expose data-flow information, monitor:
  • Run history
  • Latest run
  • Job status
  • Failures
Use this information to detect analytics content that may be using stale or incomplete data.

​
17. Configure Data Source Monitoring — Optional

When GermainUX monitors customer-controlled OAC data sources, correlate analytics activity with:
  • Database availability
  • Query performance
  • Connections
  • Locks
  • CPU
  • Memory
  • Disk
  • Network
  • Errors

​
18. Configure Synthetic Monitoring — Optional

Configure Oracle Analytics scenarios created with GermainUX RPA Bot Recorder. Configure:
  • Scenario
  • Execution location
  • Schedule
  • Test account
  • Credentials
  • Timeout
  • Validation
  • Failure condition
  • Alert
  • Maintenance window
Examples:
LoginDashboardVerify Content
DashboardFilterVerify Results
AnalysisExecuteVerify Results

​
19. Configure KPIs

Configure KPIs appropriate for the monitoring sources enabled. Depending on the GermainUX configuration, these can include:
  • User Session
  • User Interaction
  • Page Performance
  • JavaScript Error
  • HTTP Request
  • Synthetic Transaction
  • Database
  • Application
Create or map additional analytics around OAC Usage Tracking and OCI metrics when required.

​
20. Configure Measures

Measures can include:
  • Users
  • Sessions
  • Interactions
  • Dashboard views
  • Analysis activity
  • Query count
  • Query response time
  • Page response time
  • Interaction response time
  • Error count
  • Error rate
  • Network-request duration
  • Query Capacity Usage
  • Data Source Connection Errors
  • Synthetic transaction duration

​
21. Configure Analysis Dimensions

Analyze Oracle Analytics Cloud activity by:
  • Environment
  • User
  • Session
  • Dashboard
  • Analysis
  • Workbook
  • Query
  • Browser
  • Device
  • Geography
  • Error
  • Data source
  • Time period
Use only dimensions available from the configured monitoring sources.

​
22. Configure SLAs

Examples include:

​
Availability

Oracle Analytics Availability < Expected SLA

​
Dashboard Performance

Dashboard Response Time > Threshold

​
User Interaction

Interaction Response Time > Threshold

​
Query Performance

Query Response Time > Threshold

​
Query Capacity

Query Capacity Usage > Threshold

​
Data Source

Data Source Connection Errors > Threshold

​
Synthetic Monitoring

Critical OAC Scenario = Failed

​
23. Configure Rules and Automated Analysis

Create Rules such as:
  • Slow Dashboard + Slow Query
  • Slow Query + Database Degradation
  • Slow Dashboard + High Query Capacity Usage
  • Dashboard Error + Data Source Connection Error
  • Browser Error + Affected Users
  • Dataset Reload Failure + Affected Analytics Content
  • Performance Regression + Increased User Impact

​
24. Configure Alerts and Watches

Examples include:
  • Oracle Analytics Unavailable → Alert Operations
  • Critical Dashboard Slow → Notify Analytics Team
  • Query Performance Degradation → Notify Analytics and Database Teams
  • Data Source Connection Errors → Notify Integration Team
  • High Query Capacity Usage → Notify OAC Administrator
  • Dataset Reload Failure → Notify Analytics Team
  • Synthetic Dashboard Failure → Alert Support
GermainUX can trigger:
  • Alerts
  • Watches
  • Reports
  • Approved diagnostics
  • Approved automation

​
25. Configure Dashboards

​
User Experience

Monitor:
  • Users
  • Sessions
  • Interactions
  • Errors
  • Performance
  • Session Replay

​
Oracle Analytics Performance

Monitor:
  • Dashboard performance
  • Analysis performance
  • Query performance
  • Query Capacity Usage
  • Data Source Connection Errors

​
Usage and Adoption

Monitor:
  • Active users
  • Sessions
  • Dashboard usage
  • Analysis usage
  • Query activity
  • Usage trends

​
Data and Integration Health

Monitor:
  • Data sources
  • Dataset reloads
  • Data flows
  • APIs
  • Database performance

​
26. Validate the Configuration

Verify:
1

User sessions are captured

2

Oracle Analytics navigation is visible

3

User interactions are captured

4

Performance data is available

5

Browser errors are detected

6

Session Replay works when enabled

7

Sensitive information is protected

8

Usage Tracking data is available when configured

9

Query performance is analyzed correctly

10

OCI metrics are available when configured

11

REST API monitoring works when configured

12

Dataset and data-flow monitoring works when configured

13

Data-source monitoring works when configured

14

Synthetic transactions execute correctly

15

SLAs evaluate correctly

16

Alerts and Watches operate as expected

​
Troubleshooting

​
No Browser Monitoring Data

Verify:
  • RUM Extension is installed.
  • Extension is enabled.
  • OAC domain is authorized.
  • Browser security policy permits the extension.
  • User or IP is not excluded.
  • Monitoring requests can reach GermainUX.

​
Usage Tracking Data Is Missing

Verify:
  • OAC Usage Tracking is enabled.
  • Usage Tracking database is configured.
  • OAC writes records to the tracking tables.
  • GermainUX Engine can reach the database.
  • Credentials have appropriate read permissions.

​
REST API Monitoring Fails

Verify:
  • OAC instance URL
  • OAuth configuration
  • Access token
  • Application role
  • Endpoint
  • Network connectivity
  • Engine availability

​
OCI Metrics Are Missing

Verify:
  • OCI authentication
  • Tenancy
  • Compartment
  • OAC instance
  • IAM permissions
  • Required metric is available for the instance

​
Dashboard Is Slow but OAC Metrics Look Normal

Investigate:
  • Usage Tracking query performance
  • Data source performance
  • Browser network requests
  • Database performance
  • Browser processing
  • Third-party dependencies
A slow user experience does not necessarily indicate an OAC infrastructure problem.

​
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.

​
Get Help

Contact GermainUX Support

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 LLC.