Breadcrumbs

Configuring Monitoring for Olark: Analyzing Chat Events, Agent Availability, and Response Times

Configure Monitoring for Oracle Database

Configure GermainUX Oracle Database monitoring to collect Oracle telemetry, execute custom SQL, monitor sessions, locks, storage, logs, backups, create KPIs and SLAs, and configure alerts and automation.

This guide assumes that the Oracle Database data source, credentials, permissions, and GermainUX Engine have already been deployed.

🔍 Configure a Database Query Monitor

Navigate to:

Germain Workspace → Left Menu → Wizards → Database Query Monitor Deployment

Use the Wizard to create an Oracle Database Query Monitor.

A Database Query Monitor executes configured SQL according to a schedule and converts the returned information into GermainUX monitoring telemetry.

🗄️ Select the Oracle Data Source

Select the Oracle Database connection configured during deployment.

Verify that the data source:

  • Connects to the correct Oracle environment

  • Uses the appropriate credentials

  • Targets the correct database

  • Has the permissions required by the query

For RAC environments, verify that the monitor is configured for the appropriate cluster or instance scope.

✏️ Configure the SQL Query

Enter the SQL that GermainUX should execute.

Queries can retrieve permitted information from:

  • Oracle V$ views

  • Oracle GV$ views

  • DBA views

  • System tables

  • Application tables

  • Business data

This allows Oracle monitoring to be extended beyond the preconfigured metrics.

📈 Configure Database Performance Monitoring

Configure Oracle performance monitoring using the system views required for your environment.

Monitor conditions related to:

  • CPU

  • Memory

  • Disk I/O

  • Network

  • Database activity

  • Resource utilization

Use historical analytics to identify recurring performance degradation and capacity trends.

⏳ Configure SQL Performance Monitoring

Configure monitoring for SQL important to application performance.

Analyze:

  • SQL response time

  • Slow-running SQL

  • SQL execution

  • Execution plans

  • Index usage

  • SQL statistics

Use V$SQL, V$SQLSTATS, and related views for single-instance monitoring and their GV$ equivalents where appropriate for RAC.

👥 Configure Session Monitoring

Monitor active Oracle sessions.

Use session telemetry to identify:

  • Active sessions

  • Long-running sessions

  • Session activity

  • Unexpected session growth

  • Application-related database activity

For RAC, session telemetry can be analyzed across instances using the appropriate global views.

🔒 Configure Locks & Deadlocks

Configure monitoring for database locking conditions.

Analyze:

  • Locked objects

  • Blocked sessions

  • Table locks

  • Lock contention

  • Deadlocks

GermainUX provides preconfigured KPIs including:

  • Database Deadlocks

  • Database Table Locks

Configure SLAs and alerts for locking conditions requiring immediate operational attention.

🔗 Configure Database Connection Monitoring

Monitor database connection activity and resource limits.

Analyze:

  • Active connections

  • Connection utilization

  • Excessive connections

  • Resource limits

  • Potential connection leaks

Configure thresholds according to the expected workload and Oracle configuration.

📂 Configure Cursor Monitoring

Monitor Oracle cursor activity.

GermainUX provides KPIs including:

  • Database Open Cursor Count

  • Database Active Cursors

Configure thresholds where excessive cursor usage could affect application or database performance.

💾 Configure Tablespace Monitoring

Configure monitoring for Oracle tablespaces.

GermainUX can use Oracle tablespace views to analyze:

  • Tablespace utilization

  • Available capacity

  • Growth

  • Temporary space

  • Space-related risk

Preconfigured KPIs include:

  • Database Tablespace Utilization

  • Database Temp Space

Configure alerts before utilization reaches levels that could affect database operation.

🗄️ Configure Datafile Monitoring

Monitor Oracle datafiles and their contribution to database storage.

Analyze:

  • Datafile size

  • Tablespace association

  • Database size

  • Storage growth

GermainUX provides a Database Size KPI that can be used as part of capacity monitoring.

🔄 Configure Redo Log Monitoring

Monitor Oracle redo-log activity and utilization.

Use V$LOG and other permitted Oracle telemetry to analyze redo-log conditions relevant to database reliability and recovery.

Configure appropriate KPIs and thresholds for your Oracle environment.

📦 Configure Archive & Recovery Area Monitoring

Monitor archive-log and recovery-area conditions using the Oracle information available to the monitoring account.

Analyze:

  • Archive activity

  • Recovery-area utilization

  • Log-space conditions

  • Capacity trends

GermainUX provides a Database Logspace Utilization KPI.

🛡️ Configure Backup & Recovery Monitoring

Configure monitoring for Oracle backup and recovery activity.

Analyze conditions such as:

  • Backup execution

  • Backup completion

  • Backup failure

  • Recovery activity

  • Recovery time

Create KPIs, SLAs, and alerts according to the organization's backup and recovery requirements.

🚨 Configure Database Error Monitoring

Monitor Oracle diagnostic information for database errors and warnings.

Oracle diagnostic telemetry can be accessed through permitted views such as:

V$DIAG_ALERT_EXT

or, for RAC:

GV$DIAG_ALERT_EXT

GermainUX provides a Database Errors KPI.

Use categorization to distinguish critical errors from informational database events.

🗄️ Configure Oracle RAC Monitoring

For Oracle RAC, use the corresponding global GV$ views where supported.

This enables analysis across multiple Oracle instances.

Configure analytics according to whether the required perspective is:

  • Entire RAC environment

  • Individual instance

  • Comparison between instances

Use instance context when troubleshooting performance conditions isolated to a particular RAC node.

🏆 Configure KPIs

GermainUX provides Oracle Database KPIs including:

  • Database Deadlocks

  • Database Table Locks

  • Database Errors

  • Database Temp Space

  • Database Logspace Utilization

  • Database Size

  • Database Tablespace Utilization

  • Database Open Cursor Count

  • Database Active Cursors

Additional KPIs can be created for custom Oracle queries and application-specific database conditions.

📏 Configure SLAs

Create an SLA when an Oracle KPI should be evaluated against an expected condition or threshold.

For Database Query Monitors, create the base SLA using:

Fact-based SLA

Examples:

Tablespace Utilization > Threshold

Temp Space > Threshold

Database Deadlocks > 0

Database Errors > Threshold

Open Cursors > Threshold

SQL Response Time > Threshold

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

🔔 Configure SLA Actions

Select the actions GermainUX should execute when an SLA condition is met.

The Oracle Database Query Monitor workflow supports actions such as:

  • Alerts

  • Reports

  • Scripts

  • Other configured actions

The monitoring flow becomes:

Oracle Query → KPI → SLA → Alert / Report / Script

🔧 Configure Monitoring Node & Engine

For each Query Monitor, select:

Monitoring Node
The GermainUX Node from which the Engine operates.

Engine
The GermainUX Engine that executes the monitor.

The selected Engine must have connectivity to the Oracle environment.

⏱️ Configure the Schedule

Define how frequently each Oracle query should execute.

Consider:

  • Required detection speed

  • Data volatility

  • Query complexity

  • Database workload

  • Operational importance

Avoid executing resource-intensive Oracle queries more frequently than necessary.

🔍 Configure Application-Specific Database Monitoring

GermainUX can monitor permitted application and business tables in addition to Oracle system views.

For example:

Application Table → Oracle Query → KPI → SLA → Alert / Action

This can be used to monitor:

  • Processing states

  • Transaction counts

  • Failed operations

  • Queue conditions

  • Application workflows

  • Business conditions

  • Custom operational metrics

Grant the monitoring account only the access required for the selected tables.

🗂️ Configure Categorization

Categorize Oracle telemetry into useful operational groups.

For example:

  • Database Error

  • SQL Performance

  • Lock

  • Deadlock

  • Storage

  • Tablespace

  • Backup

  • RAC Instance

  • Application Condition

Categorization simplifies analytics, dashboards, reports, and alerting.

🔗 Configure Correlation

Correlate Oracle Database telemetry with other technologies monitored by GermainUX.

For example:

Application Transaction → SQL Query → Oracle Database

or:

Slow User Action → Application Transaction → Slow SQL → Oracle

or:

Application Error → Oracle Lock → Blocked Session

For RAC environments:

Application → SQL → Oracle RAC → Instance

Correlation helps teams move from application impact to the underlying database condition.

🔐 Configure Data Privacy

Review custom Oracle queries carefully when monitoring application or business tables.

Avoid collecting unnecessary:

  • Personal information

  • Authentication information

  • Financial data

  • Sensitive business data

  • Full application records

Select only the columns required for the monitoring objective and apply GermainUX privacy controls where appropriate.

📊 Configure Dashboards

Create dashboards for Oracle Database monitoring.

Examples include:

  • Database health

  • Availability

  • SQL performance

  • Sessions

  • Locks and deadlocks

  • Connections

  • Cursors

  • Tablespaces

  • Temp space

  • Database size

  • Redo/archive logs

  • Errors

  • RAC instances

  • SLA status

Combine Oracle telemetry with application and infrastructure monitoring where broader context is useful.

📄 Configure Automated Reports

Configure reports summarizing:

  • Database availability

  • Performance

  • SQL performance

  • Capacity

  • Tablespace utilization

  • Locks and deadlocks

  • Errors

  • Backup status

  • RAC health

  • SLA violations

  • Historical trends

Configure schedules and recipients according to the intended operational or management audience.

⚙️ Configure Automation

Oracle Database conditions can trigger GermainUX automation.

For example:

Oracle Condition → KPI → SLA → Alert / Action

Automation can include:

  • Notifications

  • Reports

  • Scripts

  • Operational workflows

  • Remediation actions where appropriate

✅ Verify in Germain State

After deploying or changing an Oracle Database Query Monitor, verify the monitor in:

Germain State

Confirm that:

  • Monitor is running

  • Oracle connectivity succeeds

  • Query executes successfully

  • Expected telemetry is collected

  • KPI receives values

  • SLA evaluates correctly

  • Configured actions operate as expected

🧪 Validate the Configuration

Validate representative normal and failure conditions.

Depending on monitoring scope, verify:

  • Availability

  • SQL telemetry

  • Sessions

  • Locks

  • Deadlocks

  • Connections

  • Cursors

  • Tablespace utilization

  • Temp space

  • Database size

  • Redo/archive telemetry

  • Errors

  • RAC instance data

  • Custom Oracle queries

  • KPIs

  • SLAs

  • Alerts

  • Automation

  • Dashboards and reports

Also verify that monitoring queries introduce acceptable load on the Oracle environment.

ℹ️ Advanced Configuration

Oracle Database monitoring can be extended to additional Oracle system views, DBA views, application tables, and business data accessible to the GermainUX monitoring account.

Use custom Database Query Monitors to extend monitoring while maintaining least-privilege database access and appropriate query schedules.

Please contact us for any help.

Component: Engine

Feature Availability: 8.6.0 or later