🚀 Deploying GermainUX Monitoring for Oracle Analytics Cloud: User Experience and Performance Tracking
Deploy GermainUX monitoring for Oracle Analytics Cloud to capture user experience, performance, usage, queries, APIs, OCI metrics, synthetic transactions, and supporting data-source telemetry.
⚙️ Monitoring Architecture
Components
GermainUX uses the following components to monitor Oracle Analytics Cloud:
|
Component |
Purpose |
|---|---|
|
RUM JS |
Monitors OAC user experience, interactions, browser performance, errors, and Session Replay. |
|
Engine |
Collects OAC Usage Tracking data, REST API data, OCI metrics, and telemetry from authorized supporting systems. |
|
RPA Bot Recorder |
Records critical OAC user workflows for synthetic monitoring. |
|
JS Profiler |
Provides deeper browser, JavaScript, and network diagnostics when applicable. |
📋 Prerequisites
Before deployment, identify:
|
Item |
|---|
|
Oracle Analytics Cloud instance |
|
OAC URL |
|
Authentication method |
|
OAC administrator |
|
GermainUX Component |
|
Required users and user populations |
|
Critical dashboards |
|
Critical analyses |
|
Critical workbooks |
|
Important business workflows |
|
Data sources |
|
Usage Tracking requirements |
|
REST API requirements |
|
OCI Monitoring requirements |
|
Privacy and security requirements |
1️⃣ Select the Browser Monitoring Method
Because Oracle Analytics Cloud is Oracle-managed SaaS, customer JavaScript cannot be assumed to be injectable directly into the OAC application.
Use the GermainUX RUM Extension for browser-side monitoring when appropriate.
The RUM Extension can provide visibility into the authorized user's Oracle Analytics browser activity without modifying Oracle-managed application code.
2️⃣ Configure the Browser Extension
Go to:
Germain Workspace > Left Menu > Wizards > Browser Extension Agent
Create the configuration required for the Oracle Analytics Cloud environment.
Configure the OAC domains that are authorized for monitoring.
Deploy the extension through the organization's approved browser-extension deployment mechanism.
🔒 Configure Privacy
Before production deployment, identify information that must not be collected.
Configure appropriate masking, anonymization, or exclusions for:
|
Item |
|---|
|
Passwords |
|
Authentication tokens |
|
Personal information |
|
Sensitive dashboard data |
|
Sensitive query information |
|
Restricted business information |
|
URL parameters containing identifiers |
Validate monitoring against the organization's security and privacy requirements.
🏭 Deploy a GermainUX Engine
Deploy or select a GermainUX Engine when server-side collection is required.
The Engine can be used for approved monitoring sources such as:
|
Source |
|---|
|
Oracle Analytics Usage Tracking |
|
Oracle Analytics REST APIs |
|
OCI Monitoring APIs |
|
Customer-controlled databases |
|
Supporting APIs |
|
Synthetic monitoring |
Select an Engine that can reach all required endpoints.
🔎 Configure Oracle Analytics Usage Tracking — Optional
Oracle Analytics Cloud can track detailed user query activity.
When this information is required, enable Oracle Analytics Usage Tracking according to Oracle's supported configuration.
Usage Tracking can record information about:
|
Recorded Item |
|---|
|
Users |
|
Sessions |
|
Logical queries |
|
Physical queries |
|
Query duration |
|
Query frequency |
|
Rows processed |
Oracle Analytics writes Usage Tracking information to configured database tables.
Provide GermainUX with authorized read access to the Usage Tracking database when this data needs to be monitored.
Use a least-privilege read-only account whenever possible.
✅ Validate the Usage Tracking Database
Confirm:
|
Check |
|---|
|
Usage Tracking is enabled. |
|
OAC writes query activity to the configured tables. |
|
GermainUX Engine can reach the database. |
|
Monitoring credentials are valid. |
|
Account has appropriate read permissions. |
|
Query activity is available. |
3️⃣ Configure Oracle Analytics REST API Access — Optional
Oracle Analytics Cloud provides REST APIs for supported administrative and analytics operations.
Before configuring GermainUX, identify:
|
Item |
|---|
|
OAC instance URL |
|
Required API endpoints |
|
Authentication |
|
Required API endpoints |
|
Authentication method |
|
OAuth configuration |
|
Required application roles |
|
Expected responses |
Use the minimum privileges required for monitoring.
☁️ Configure OCI Monitoring Access — Optional
Oracle Analytics Cloud exposes operational metrics through Oracle Cloud Infrastructure Monitoring.
When these metrics are required, configure authorized access to OCI Monitoring.
Identify:
|
Item |
|---|
|
OCI tenancy |
|
Compartment |
|
OAC instance |
|
Authentication |
|
IAM permissions |
|
Required metrics |
Use read-only monitoring permissions whenever they satisfy the requirement.
🗄️ Deploy Customer-Controlled Data Source Monitoring — Optional
If Oracle Analytics Cloud connects to customer-controlled data sources, deploy GermainUX monitoring for those systems when deeper Root Cause Analysis is required.
Examples include:
|
Data Source |
|---|
|
Oracle Database |
|
SQL Server |
|
MySQL |
|
APIs |
|
Network |
|
Cloud resources |
This enables correlation between OAC performance and the underlying systems serving analytics queries.
🤖 Deploy Synthetic Monitoring — Optional
Use GermainUX RPA Bot Recorder to record approved Oracle Analytics workflows.
Examples include:
Login → Open Dashboard → Verify Content
Open Dashboard → Apply Filter → Verify Results
Open Analysis → Execute Query → Verify Response
Open Workbook → Navigate → Verify Expected Visualization
Deploy the recorded scenario through GermainUX Engine.
Use:
|
Requirement |
|---|
|
Dedicated test account |
|
Minimum required privileges |
|
Safe test workflows |
|
Appropriate execution frequency |
4️⃣ Validate Browser Monitoring
Using an authorized test account:
-
Open Oracle Analytics Cloud.
-
Log in.
-
Open a monitored dashboard.
-
Navigate between analytics content.
-
Execute representative interactions.
-
Run an analysis.
-
Open a workbook when applicable.
Verify that GermainUX receives the expected browser telemetry.
5️⃣ Validate Usage Tracking
Execute representative OAC queries.
Verify:
|
Check |
|---|
|
Query activity reaches the Usage Tracking database. |
|
GermainUX can retrieve the required data. |
|
Users and sessions are identified appropriately. |
|
Query timing is available. |
|
Logical and physical query information is available as configured. |
6️⃣ Validate API Monitoring
When REST API monitoring is configured, verify:
|
Check |
|---|
|
Authentication succeeds. |
|
Endpoint is reachable. |
|
Expected HTTP status is returned. |
|
Response validation succeeds. |
|
Response time is recorded. |
7️⃣ Validate OCI Metrics
When OCI Monitoring is configured, verify that GermainUX receives the required Oracle Analytics Cloud metrics.
🏁 Validate the Deployment
Confirm:
|
Item |
|---|
|
Browser monitoring is operational. |
|
Privacy controls are effective. |
|
Session Replay works when enabled. |
|
Usage Tracking data is available when configured. |
|
REST API monitoring works when configured. |
|
OCI metrics are collected when configured. |
|
Data-source monitoring works when configured. |
|
Synthetic transactions execute successfully. |
Once deployment is validated, continue with Configure Monitoring for Oracle Analytics Cloud.
ℹ️ 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