Oracle Database integration

Oracle Database is a multi-model relational database management system used widely in enterprise environments. The Oracle Database integration monitors session and process activity, tablespace utilization, and wait events.


What it monitors	Sessions, processes, tablespace usage, wait times, resource limits, and `oracledb_up` availability
How it works	Grafana Alloy’s built-in OracleDB exporter scrapes metrics from your Oracle instance using Oracle Instant Client
What you get	3 alerts + 2 dashboards (Oracle Database overview and Oracle Database logs)
Prerequisites	Oracle Instant Client installed on the Alloy host with `ORACLE_HOME` set (Alloy 1.9.0+), plus a monitoring user with specific `SELECT` grants

What you’ll see in the dashboards

Sessions and processes: Active sessions, process counts, and how close you are to configured limits
Tablespace utilization: Used vs. allocated space across tablespaces
Wait events: Which categories of waits are consuming time inside the database
Resource limits: Current values against v$resource_limit thresholds
Availability: oracledb_up for at-a-glance health

Key alerts

Alert	Severity
OracledbReachingSessionLimit	Critical
OracledbReachingProcessLimit	Critical
OracledbTablespaceReachingCapacity	Critical

Documentation

View the Oracle Database integration documentation.

Path completed

The Oracle Database integration monitors session usage, process limits, tablespace capacity, and wait times. It’s the only option in this journey for Oracle, since Database Observability doesn’t yet support it.

The overview dashboard covers the operational fundamentals: active sessions, process counts, tablespace utilization, and wait-event breakdowns, and a separate logs dashboard collects the Oracle alert log. The built-in alerts focus on the most common operational risks: running out of sessions, running out of processes, and tablespaces filling up.

Setup is a little heavier than other integrations because it requires the Oracle Instant Client. From Alloy 1.9.0 and later, the exporter needs Instant Client installed on the Alloy host with the ORACLE_HOME environment variable set. A dedicated monitoring user with specific SELECT grants is also required, which is standard practice for any Oracle monitoring tool.

If Oracle Database is what you’re running, the documentation link below takes you to the full setup guide.

Oracle Database integration