You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These standard metrics are defined in the file `default-metrics.toml` found in the root directory of this repository.
348
+
349
+
> **Note:** You can change the interval at which metrics are collected at a per-metric level. If you find that any of the default metrics are placing too much load on your database instance, you may will too collect that particular metric less often, which can be done by adding the `scrapeinterval` paraemeter to the metric definition. See the definition of the `top_sql` metric for an example.
350
+
351
+
336
352
## Database permissions required
337
353
338
354
For the built-in default metrics, the database user that the exporter uses to connect to the Oracle Database instance must have the `SELECT_CATALOG_ROLE` privilege and/or `SELECT` permission on the following objects:
@@ -477,6 +493,9 @@ Now, you provide the connection details using these variables:
477
493
-`DB_CONNECT_STRING` is the connection string, e.g., `devdb_tp?TNS_ADMIN=/wallet`
478
494
-`DB_ROLE` (Optional) can be set to `SYSDBA` or `SYSOPER` if you want to connect with one of those roles, however Oracle recommends that you connect with the lowest possible privileges and roles necessary for the exporter to run.
479
495
-`ORACLE_HOME` is the location of the Oracle Instant Client, i.e., `/lib/oracle/21/client64/lib`. If you built your own container image, the path may be different.
496
+
-`TNS_ADMIN` is the location of your (unzipped) wallet. The `DIRECTORY` set in the `sqlnet.ora` file must match the path that it will be mounted on inside the container.
497
+
498
+
> **Note:** Specify the path to your wallet using the `TNS_ADMIN` environment variable rather than adding it to the `DB_CONNECT_STRING`.
480
499
481
500
To run the exporter in a container and expose the port, use a command like this, with the appropriate values for the environment variables, and mounting your `wallet` directory as `/wallet` in the container to provide access to the wallet:
> **Note:** If you are using `podman` you must specify the `:z` suffix on the volume mount so that the container will be able to access the files in the volume. For example: `-v ./wallet:/wallet:z`
492
512
493
513
### Test/demo environment with Docker Compose
494
514
@@ -651,6 +671,7 @@ You may provide the connection details using these variables:
651
671
- `DB_CONNECT_STRING`is the connection string, e.g., `localhost:1521/freepdb1`
652
672
- `DB_ROLE`(Optional) can be set to `SYSDBA` or `SYSOPER` if you want to connect with one of those roles, however Oracle recommends that you connect with the lowest possible privileges and roles necessary for the exporter to run.
653
673
- `ORACLE_HOME`is the location of the Oracle Instant Client, e.g., `/lib/oracle/21/client64/lib`.
674
+
- `TNS_ADMIN`is the location of your (unzipped) wallet. The `DIRECTORY` set in the `sqlnet.ora` file must match the path that it will be mounted on inside the container.
654
675
655
676
The following example puts the logfile in the current location with the filename `alert.log` and loads the default matrics file (`default-metrics,toml`) from the current location.
656
677
@@ -775,7 +796,7 @@ An exmaple of [custom metrics for Transacational Event Queues](./custom-metrics-
775
796
If you run the exporter as a container image and want to include your custom metrics in the image itself, you can use the following example `Dockerfile` to create a new image:
776
797
777
798
```Dockerfile
778
-
FROM container-registry.oracle.com/database/observability-exporter:1.5.0
799
+
FROM container-registry.oracle.com/database/observability-exporter:1.5.1
0 commit comments