OracleDB Monitoring

oracle database (oracledb) is foundational for many enterprise applications, and robust monitoring is essential for maintaining performance and reliability kloudmate provides comprehensive visibility into oracledb by delivering real time insights through logs and metrics using the kloudmate agent powered by opentelemetry oracledb monitoring in kloudmate enables centralized monitoring of oracle database instances running on aws ec2, azure virtual machines, or on premise servers oracledb integration using kloudmate agents what this integration provides with oracledb monitoring enabled, kloudmate collects telemetry that provides visibility into • database session and system statistics • tablespace utilization and data file metrics • resource limits and consumption patterns • performance bottlenecks and resource contention • server logs and operational events this visibility helps identify capacity issues, performance degradation, storage constraints, and availability problems prerequisites • oracle database must be installed and running • kloudmate agent installed on the oracledb host (see agent installation for https //docs kloudmate com/linux agent and https //docs kloudmate com/windows agent ) required permissions monitoring database user requires grant select on v $session to \<username>; grant select on v $sysstat to \<username>; grant select on v $resource limit to \<username>; grant select on dba tablespaces to \<username>; grant select on dba data files to \<username>; grant select on dba tablespace usage metrics to \<username>; configuration overview step 1 access agents and opentelemetry collector configuration log in to the kloudmate platform go to settings → agents select the agent running on the postgresql host click actions → collector configuration yaml editor opens for configuration step 2 configure the oracledb receiver receivers oracledb datasource "oracle //otel\ passwd@\<host ip address>/xepdb1" connection string format oracle //username\ password\@host\ port/service name replace • otel → monitoring username • passwd → monitoring user password • \<host ip address> → oracledb host ip • xepdb1 → pdb/service name (adjust for your database) step 3 export data to kloudmate exporters otlphttp endpoint 'https //otel kloudmate com 4318' headers authorization \<api key> this enables forwarding telemetry to kloudmate for analysis and visualization sample configuration extensions health check pprof endpoint 0 0 0 0 1777 zpages endpoint 0 0 0 0 55679 receivers otlp protocols grpc endpoint 0 0 0 0 4317 http endpoint 0 0 0 0 4318 opencensus endpoint 0 0 0 0 55678 oracledb datasource "oracle //otel\ passwd@\<host ip address>/xepdb1" \# collect own metrics prometheus config scrape configs \ job name 'otel collector' scrape interval 10s static configs \ targets \['0 0 0 0 8888'] jaeger protocols grpc endpoint 0 0 0 0 14250 thrift binary endpoint 0 0 0 0 6832 thrift compact endpoint 0 0 0 0 6831 thrift http endpoint 0 0 0 0 14268 zipkin endpoint 0 0 0 0 9411 processors memory limiter check interval 1s limit mib 1000 spike limit mib 800 batch send batch size 1000 timeout 10s exporters debug verbosity detailed otlphttp endpoint 'https //otel kloudmate com 4318' headers authorization \<api key> service pipelines traces receivers \[otlp, opencensus, jaeger, zipkin] processors \[batch] exporters \[debug, otlphttp] metrics receivers \[oracledb] processors \[memory limiter, batch] exporters \[debug, otlphttp] logs receivers \[otlp, oracledb] processors \[memory limiter, batch] exporters \[debug, otlphttp] extensions \[health check, pprof, zpages] post‑integration data validation verify that metrics are flowing into kloudmate using the explore view after the agent restarts log in to kloudmate navigate to explore select opentelemetry → metrics choose a oracledb metric and run the query seeing time series data confirms that oracledb telemetry is flowing successfully set up kloudmate dashboards and alerts access kloudmate and create dashboards to visualize oracledb metrics and logs configure alerting rules for critical thresholds and unusual activity default metrics default metrics oracledb cpu time oracledb dml locks limit oraclb dml locks usage oracledb enqueue deadlocks oracledb enqueue locks limit oracledb enqueue locks usage oracledb enqueue resources limit oracledb enqueue resources usage oracledb exchange deadlocks oracledb executions oracledb hard parses oracledb logical reads oracledb parse calls oracledb pga memory oracledb physical reads oracledb processes limit oracledb processes usage oracledb sessions limit oracledb sessions usage oracledb tablespace size limit oracledb tablespace size usage oracledb transactions limit oracledb transactions usage oracledb user commits oracledb user rollbacks optional metrics oracledb consistent gets oracledb db block gets for the complete metrics list, refer to the https //github com/open telemetry/opentelemetry collector contrib/blob/main/receiver/oracledbreceiver/documentation md