A Prometheus exporter for Oracle.
The following metrics are exposed currently. Support for RAC (databasename and instancename added via lables)
- oracledb_exporter_last_scrape_duration_seconds
- oracledb_exporter_last_scrape_error
- oracledb_exporter_scrapes_total
- oracledb_uptime (days)
- oracledb_session (view v$session system/user active/passive)
- oracledb_sysmetric (view v$sysmetric (Physical Read Total IO Requests Per Sec / Physical Write Total IO Requests Per Sec Physical Read Total Bytes Per Sec / Physical Write Total Bytes Per Sec))
- oracledb_sysstat (view v$sysstat (parse count (total) / execute count / user commits / user rollbacks))
- oracledb_waitclass (view v$waitclass)
- oracledb_tablespace (tablespace total/free)
- oracledb_asmspace (Space in ASM (v$asm_disk/v$asm_diskgroup))
- oracledb_interconnect (view v$sysstat (gc cr blocks served / gc cr blocks flushed / gc cr blocks received))
- oracledb_redo (Redo log switches over last 5 min from v$log_history)
- oracledb_cachehitratio (Cache hit ratios (v$sysmetric)
- oracledb_up (Whether the Oracle server is up)
- oracledb_error (Errors parsed from the alert.log)
- oracledb_error_unix_seconds (Last modified Date of alert.log in Unixtime)
- oracledb_services (Active Oracle Services (v$active_services))
- oracledb_parameter (Configuration Parameters (v$parameter))
- oracledb_query (Self defined Queries in Configuration File)
*TOOK VERY LONG, BE CAREFUL (Put the Metrics below in a separate Scrape-Config):
- oracledb_tablerows (Number of Rows in Tables)
- oracledb_tablebytes (Bytes used by Table)
- oracledb_indexbytes (Bytes used by Indexes of associated Table)
- oracledb_lobbytes (Bytes used by Lobs of associated Table)
- oracledb_recovery (percentage usage in FRA from V$RECOVERY_FILE_DEST)
The Oracle Alertlog file is scanned and the metrics are exposed as a gauge metric with a total occurence of the specific ORA. You can define your own Queries and execute/scrape them
Ensure that the configfile (oracle.conf) is set correctly before starting. You can add multiple instances, e.g. the ASM instance. It is even possible to run one Exporter for all your Databases, but this is not recommended. We use it in our Company because on one host multiple Instances are running.
scrape_configs:
- job_name: 'oracle-short'
metrics_path: /metrics
static_configs:
- targets:
- oracle.host.com:9161
relabel_configs:
- source_labels: ['__address__']
target_label: instance
regex: '(.*):\d+'
replacement: "${1}"
- job_name: 'oracle-tab'
scrape_interval: 6h
scrape_timeout: 120s
metrics_path: /metrics
params:
tablerows: [true]
lobbytes: [true]
static_configs:
- targets:
- oracle.host.com:9161
relabel_configs:
- source_labels: ['__address__']
target_label: instance
regex: '(.*):\d+'
replacement: "${1}"
- job_name: 'oracle-ind'
scrape_interval: 6h
scrape_timeout: 120s
metrics_path: /metrics
params:
tablebytes: [true]
indexbytes: [true]
static_configs:
- targets:
- oracle.host.com:9161
relabel_configs:
- source_labels: ['__address__']
target_label: instance
regex: '(.*):\d+'
replacement: "${1}"
export NLS_LANG=AMERICAN_AMERICA.UTF8
/path/to/binary -configfile=/home/user/oracle.conf -web.listen-address :9161Usage of ./prometheus_oracle_exporter:
-accessfile string
Last access for parsed Oracle Alerts. (default "access.conf")
-configfile string
ConfigurationFile in YAML format. (default "oracle.conf")
-indexbytes
Expose Index size for any Table (CAN TAKE VERY LONG)
-lobbytes
Expose Lobs size for any Table (CAN TAKE VERY LONG)
-logfile string
Logfile for parsed Oracle Alerts. (default "exporter.log")
-tablebytes
Expose Table size (CAN TAKE VERY LONG)
-tablerows
Expose Table rows (CAN TAKE VERY LONG)
-web.listen-address string
Address to listen on for web interface and telemetry. (default ":9161")
-web.telemetry-path string
Path under which to expose metrics. (default "/metrics")In The folder Grafana are examples of my used Dashboards
