⚙️ 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:
|
Item |
|
|---|---|
|
1 |
User sessions |
|
2 |
Navigation |
|
3 |
Clicks |
|
4 |
User interactions |
|
5 |
Page performance |
|
6 |
Browser errors |
|
7 |
Network requests |
|
8 |
Analytics workflows |
🎥 2. Configure Session Replay
Enable Session Replay when authorized.
Configure applicable:
|
Setting |
|---|
|
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:
|
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:
|
Dimension |
|---|
|
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:
|
Content |
|---|
|
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:
|
Action |
|---|
|
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:
|
Click Type |
|---|
|
Standard clicks |
|
Dead clicks |
|
Error clicks |
|
Rage clicks |
Use these signals to identify:
|
Signal |
|---|
|
Unresponsive controls |
|
Failed navigation |
|
Repeated user attempts |
|
Browser errors |
|
User friction |
⏱️ 8. Configure Browser Performance
Analyze:
|
Metric |
|---|
|
Page response time |
|
Interaction response time |
|
Browser processing |
|
Network-request duration |
|
Failed requests |
|
Resource-loading performance |
Compare performance by:
|
Dimension |
|---|
|
User |
|
Session |
|
Dashboard |
|
Browser |
|
Device |
|
Geography |
|
Time period |
9. Configure Browser Error Monitoring
Monitor:
|
Error Type |
|---|
|
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:
|
Field |
|---|
|
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:
|
Issue |
|---|
|
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:
|
Measure |
|---|
|
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:
|
Metric |
|---|
|
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:
|
Setting |
|---|
|
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:
|
Item |
|---|
|
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:
|
Item |
|---|
|
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:
|
Metric |
|---|
|
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:
|
Setting |
|---|
|
Scenario |
|
Execution location |
|
Schedule |
|
Test account |
|
Credentials |
|
Timeout |
|
Validation |
|
Failure condition |
|
Alert |
|
Maintenance window |
Examples:
Login → Dashboard → Verify Content
Dashboard → Filter → Verify Results
Analysis → Execute → Verify Results
🏅 19. Configure KPIs
Configure KPIs appropriate for the monitoring sources enabled.
Depending on the GermainUX configuration, these can include:
|
KPI |
|---|
|
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:
|
Measure |
|---|
|
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:
|
Dimension |
|---|
|
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:
|
Action |
|---|
|
Alerts |
|
Watches |
|
Reports |
|
Approved diagnostics |
|
Approved automation |
🖥️ 25. Configure Dashboards
👥 User Experience
Monitor:
|
Metric |
|---|
|
Users |
|
Sessions |
|
Interactions |
|
Errors |
|
Performance |
|
Session Replay |
🚤 Oracle Analytics Performance
Monitor:
|
Metric |
|---|
|
Dashboard performance |
|
Analysis performance |
|
Query performance |
|
Query Capacity Usage |
|
Data Source Connection Errors |
🚀 Usage and Adoption
Monitor:
|
Metric |
|---|
|
Active users |
|
Sessions |
|
Dashboard usage |
|
Analysis usage |
|
Query activity |
|
Usage trends |
🏥 Data and Integration Health
Monitor:
|
Item |
|---|
|
Data sources |
|
Dataset reloads |
|
Data flows |
|
APIs |
|
Database performance |
✅ 26. Validate the Configuration
Verify:
-
User sessions are captured.
-
Oracle Analytics navigation is visible.
-
User interactions are captured.
-
Performance data is available.
-
Browser errors are detected.
-
Session Replay works when enabled.
-
Sensitive information is protected.
-
Usage Tracking data is available when configured.
-
Query performance is analyzed correctly.
-
OCI metrics are available when configured.
-
REST API monitoring works when configured.
-
Dataset and data-flow monitoring works when configured.
-
Data-source monitoring works when configured.
-
Synthetic transactions execute correctly.
-
SLAs evaluate correctly.
-
Alerts and Watches operate as expected.
🔧 Troubleshooting
🔎 No Browser Monitoring Data
Verify:
|
Check |
|---|
|
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:
|
Check |
|---|
|
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:
|
Check |
|---|
|
OAC instance URL |
|
OAuth configuration |
|
Access token |
|
Application role |
|
Endpoint |
|
Network connectivity |
|
Engine availability |
📊 OCI Metrics Are Missing
Verify:
|
Check |
|---|
|
OCI authentication |
|
Tenancy |
|
Compartment |
|
OAC instance |
|
IAM permissions |
|
Required metric is available for the instance |
❓ Dashboard Is Slow but OAC Metrics Look Normal
Investigate:
|
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.
Component: Engine, JS Profiler, Mobile, RPA Bot Recorder, RUM JS
Feature Availability: 2017.1 or later