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

# OBIEE Observability

> Monitor actual user interactions with OBIEE while correlating the experience with the underlying web server, JVM, Java code, logs, and server performance.

Components
[`Engine`](/main/germain-ux-engine)
[`JS Profiler`](/main/germain-ux-js-profiler)
[`RPA Bot Recorder`](/main/germain-ux-rpa-bot-recorder)
[`RUM JS`](/main/germain-ux-rum-js)

Availability
2017.1 or later

> **[Real User Monitoring](#real-user-monitoring)**
>
> Sessions, actions and navigation

> **[Root Cause & User Impact](#root-cause-%26-user-impact)**
>
> Linking issues to affected users

> **[Real-Time Dashboards & Automated Reports](#real-time-dashboards-%26-automated-reports)**
>
> Live views and scheduled reports

> **[Get More Information](#get-more-information)**
>
> Links to configuration guides

**Monitor OBIEE User Experience, Performance & Reliability with GermainUX**

> [!NOTE]
>
> GermainUX provides real-time **Operational Experience Intelligence, Observability, Analytics, Alerting, and Automation for Oracle Business Intelligence Enterprise Edition (OBIEE)**.

## What GermainUX Monitors

Monitor actual user interactions with OBIEE while correlating the experience with the underlying web server, JVM, Java code, logs, and server performance.

### End-to-end Visibility

| Component | Details |
| - | - |
| GermainUX provides visibility across: | **User → Browser → OBIEE → Web Server → JVM / Java → Server** |

## Real User Monitoring

Monitor how actual users experience OBIEE.

GermainUX captures user sessions, actions, and navigation within the OBIEE application to provide visibility into:

* User activity
* User navigation
* Application usage
* User sessions
* Application responsiveness
* User experience

This helps teams understand not only whether OBIEE is operational, but how it is actually performing for users.

## Session-Level Analysis

Analyze individual OBIEE user sessions to understand the sequence of actions leading to slowdowns, errors, or other experience issues.

Session-level telemetry helps connect an affected user with the technical conditions occurring during the same period.

## OBIEE Performance Monitoring

Monitor OBIEE availability, uptime, and performance.

GermainUX helps identify conditions affecting the responsiveness and reliability of the OBIEE environment.

Performance can be analyzed alongside actual user activity to determine whether technical degradation is affecting users.

### Transaction Performance Comparison

When analyzing a slow or failed OBIEE 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 OBIEE operation
* Which steps, dashboard loads, or queries caused the slowdown
* Performance differences between successful and failed OBIEE transactions
* Errors or bottlenecks affecting analytics workflows
* Potential root causes of transaction performance degradation

This helps pinpoint why an OBIEE 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).

## Web Server Monitoring

Monitor the web server supporting the OBIEE application.

Analyze:

* Availability
* Response time
* Performance
* Operational health

Web-server telemetry provides an additional layer of context when investigating slow or unavailable OBIEE experiences.

## JVM Monitoring

Monitor the Java Virtual Machine supporting OBIEE.

GermainUX can monitor JVM telemetry such as:

* CPU usage
* Memory allocation
* Garbage collection
* Thread count
* JVM performance

This helps identify Java runtime conditions contributing to OBIEE performance degradation.

## Java Code Real-Time Profiling

Profile Java code executing within the OBIEE environment in real time.

Analyze:

* Function execution time
* CPU consumption
* Memory allocation
* Thread usage

Code profiling helps identify Java execution bottlenecks contributing to application performance issues.

## Log Monitoring

Capture and analyze logs generated by the OBIEE environment.

Detect:

* Errors
* Warnings
* Exceptions
* Recurring operational conditions

Log telemetry can be correlated with application performance, JVM behavior, and user activity to accelerate troubleshooting.

## Server Monitoring

Monitor the server infrastructure supporting OBIEE.

GermainUX provides visibility into the availability and performance of the OBIEE server environment so infrastructure conditions can be analyzed alongside application behavior.

## Root Cause & User Impact

Correlate OBIEE user experience with supporting technology.

For example:

Slow User Action
OBIEE
Web Server
JVM

or:

User Error
OBIEE Session
Application Log Error

or:

Slow OBIEE Response
Java Execution
JVM Resource Condition

This helps teams determine whether an issue originates in the user-facing application, web tier, Java runtime, code, or supporting server.

## Detect Issues in Real Time

GermainUX can help identify conditions such as:

* OBIEE unavailable
* Slow application response
* Web server unavailable or slow
* JVM performance degradation
* Java execution bottleneck
* Error, warning, or exception
* Server performance degradation

Detected conditions can be analyzed, alerted on, reported, or used to trigger operational actions.

## Real-Time Dashboards & Automated Reports

Analyze OBIEE telemetry using customizable real-time dashboards and automated reports.

Examples include:

* User activity
* User sessions
* OBIEE availability
* Application performance
* Web server performance
* JVM performance

> **Show all 10**
>
> * Java profiling
> * Errors and exceptions
> * Server health
> * Historical trends

Combine user-experience and technical telemetry to provide a unified operational view of OBIEE.

## Alerts & SLA Monitoring

Configure alerts and SLA thresholds for conditions requiring attention.

For example:

* OBIEE unavailable
* Response time exceeds threshold
* Web server unavailable
* JVM resource threshold exceeded
* Critical error detected
* Java execution exceeds expected duration

Configure thresholds according to the expected behavior of each OBIEE environment.

## Automation

OBIEE monitoring conditions can trigger GermainUX automation.

For example:

Monitor
Detect
Analyze
Alert
Automate

Depending on the use case, automation can include:

* Notifications
* Reports
* Scripts
* Operational workflows
* Remediation actions where appropriate

## End-to-End Operational Experience

GermainUX combines user experience and technical monitoring across the OBIEE stack.

User
Browser
OBIEE
Web Server
JVM / Java
Server

This allows teams to answer two important questions:

**What did the OBIEE user experience?**

and:

**What technical condition contributed to it?**

## Deployment

GermainUX provides an **OBIEE Server Wizard** to simplify deployment of OBIEE monitoring.

Depending on the required monitoring scope, GermainUX can use:

* Engine
* RUM JS
* RUM Browser Extension
* JS Profiler
* RPA Bot Recorder

See **Deploy Monitoring for OBIEE** for deployment instructions.

## Get More Information

OBIEE monitoring can be customized according to your environment, architecture, applications, user population, and operational requirements.

See **Configure Monitoring for OBIEE** for configuration options.

The GermainUX team can help configure the appropriate monitoring scope, privacy controls, analytics, alerts, and automation for your OBIEE environment. Please contact us [for any help.](/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.