Oracle Database receiver
The Oracle Database receiver collects metrics from an Oracle Database instance.
The Oracle Database receiver, a component of the Splunk Distribution of the OpenTelemetry Collector, queries and retrieves metrics from Oracle Database instances. The receiver connects to an Oracle Database instance and obtains metrics from it such as the number of physical reads, cumulative CPU time, and others. The supported pipeline type is metrics
. See Process your data with pipelines for more information.
Prerequisites
Create an Oracle Database user and password:
-- Create user and set a password CREATE USER <username> IDENTIFIED BY <password>;
Depending on which metrics you collect, you might need to assign the following permissions to the Oracle Database user you created in the previous step:
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>;
Get started
Follow these steps to configure and activate the receiver:
Deploy the collector
Deploy the Splunk Distribution of the OpenTelemetry Collector to your host or container platform:
Configure the receiver
Add
oracledb
to thereceivers
section of your Splunk Distribution of the OpenTelemetry Collector configuration file.- Sample configuration for collecting data from one Oracle Database server
To activate the Oracle Database receiver, add
oracledb
to thereceivers
section of your configuration file, as shown in the following example:receivers: oracledb: # You must encode special characters. Refer to Oracle Go Driver go_ora documentation for full connection string options datasource: "oracle://<username>:<password>@<host>:<port>/<database>"
Alternatively, add
endpoint
,password
,service
, andusername
to thereceivers
section of your configuration file, as shown in the following example:receivers: oracledb: endpoint: <host> password: <password> service: <service> username: <username>
- Sample configuration for collecting data from multiple Oracle Database servers
To collect data from more than one instance of Oracle Database server, add as many entries of the
oracledb
receiver as needed. For example:receivers: oracledb/aninstance: # You must encode special characters. Refer to Oracle Go Driver go_ora documentation for full connection string options datasource: "oracle://<username>:<password>@<host>:<port>/<database>" oracledb/anotherinstance: # You must encode special characters. Refer to Oracle Go Driver go_ora documentation for full connection string options datasource: "oracle://<username>:<password>@<host>:<port>/<database>"
- Sample configuration for high availability
To configure the Oracle Database receiver for high availability, use:
receivers: oracledb: # You must encode special characters. Refer to Oracle Go Driver go_ora documentation for full connection string options datasource: "oracle://<username>:<password>@<host>:<port>/<service_name>?server=<host>:<port>"
Configure advanced settings.
Add
oracledb
toservice.pipeline.metrics
in the collector configuration file:service: pipelines: metrics: receivers: - oracledb
Restart the collector
The command to restart the Splunk Distribution of the OpenTelemetry Collector varies depending on what platform you deployed it on and what tool you used to deploy it, but here are general examples of the restart command:
sudo systemctl restart splunk-otel-collector
Windows with installer script:
Stop-Service splunk-otel-collector Start-Service splunk-otel-collector
sudo systemctl restart splunk-otel-collector
Settings
The following table shows the configuration options for the Oracle Database receiver:
included
https://raw.githubusercontent.com/splunk/collector-config-tools/main/cfg-metadata/receiver/oracledb.yaml
Metrics
The following metrics, resource attributes, and attributes, are available.
included
https://raw.githubusercontent.com/splunk/collector-config-tools/main/metric-metadata/oracledbreceiver.yaml
Activate or deactivate specific metrics
You can activate or deactivate specific metrics by setting the enabled
field in the metrics
section for each metric. For example:
receivers:
samplereceiver:
metrics:
metric-one:
enabled: true
metric-two:
enabled: false
The following is an example of host metrics receiver configuration with activated metrics:
receivers:
hostmetrics:
scrapers:
process:
metrics:
process.cpu.utilization:
enabled: true
-
If you’re in a MTS-based subscription, all metrics count towards metrics usage.
-
If you’re in a host-based plan, metrics listed as active (Active: Yes) on this document are considered default and are included free of charge.
Learn more at Infrastructure Monitoring subscription usage (Host and metric plans).
Troubleshooting
If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.
Available to Splunk Observability Cloud customers
Submit a case in the Splunk Support Portal.
Contact Splunk Support.
Available to prospective customers and free trial users
Ask a question and get answers through community support at Splunk Answers.
Join the Splunk community #observability Slack channel to communicate with customers, partners, and Splunk employees worldwide.