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
* pickup change in godror to add extra admin roles
* update doc, version
* uptake new admin role api
* update version nums
* use AdminRole type instead of just string
Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>
---------
Signed-off-by: Mark Nelson <mark.x.nelson@oracle.com>
Copy file name to clipboardExpand all lines: README.md
+27-4
Original file line number
Diff line number
Diff line change
@@ -27,8 +27,31 @@ Contributions are welcome - please see [contributing](CONTRIBUTING.md).
27
27
28
28
## Release Notes
29
29
30
+
### Version 1.5.4, February 27, 2025
31
+
32
+
Our current priorities are support for RAC and mutliple databases (inculding #84 and #89), and intermittent connection issues
33
+
with ADB-S when exporter is run in a container (including #169). We expect to address these in an upcoming release.
34
+
35
+
- Fix malloc error (#177)
36
+
- Add support for additional admin roles, exapnding list of options for `DB_ROILE` to `SYSDBA`, `SYSOPER`, `SYSBACKUP`, `SYSDG`, `SYSKM`, `SYSRAC` and `SYSASM` (#180)
37
+
- Updated some third-party dependencies.
38
+
39
+
Thank you to the following people for their suggestions and contributions:
In this release, we also continued some minor code refactoring.
49
+
30
50
### Version 1.5.3, January 28, 2025
31
51
52
+
*Known issue*: This release has a known issue that results in the error message `malloc(): unsorted double linked list corrupted`.
53
+
We recommend staying on 1.5.2 until a new release with a fix is available. We hope to have a fix by early March.
54
+
32
55
Our current priorities are support for RAC and mutliple databases (inculding #84 and #89), and intermittent connection issues
33
56
with ADB-S when exporter is run in a container (including #169). We expect to address these in an upcoming release.
34
57
@@ -496,7 +519,7 @@ For a simple connection, you will provide the details using these variables:
496
519
-`DB_USERNAME` is the database username, e.g., `pdbadmin`
497
520
-`DB_PASSWORD` is the password for that user, e.g., `Welcome12345`
498
521
-`DB_CONNECT_STRING` is the connection string, e.g., `free23ai:1521/freepdb`
499
-
-`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.
522
+
-`DB_ROLE` (Optional) can be set to `SYSDBA`, `SYSOPER`, `SYSBACKUP`, `SYSDG`, `SYSKM`, `SYSRAC`or `SYSASM` 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.
500
523
501
524
To run the exporter in a container and expose the port, use a command like this, with the appropriate values for the environment variables:
>**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`
558
581
@@ -842,7 +865,7 @@ An exmaple of [custom metrics for Transacational Event Queues](./custom-metrics-
842
865
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:
843
866
844
867
```Dockerfile
845
-
FROM container-registry.oracle.com/database/observability-exporter:1.5.3
868
+
FROM container-registry.oracle.com/database/observability-exporter:1.5.4
0 commit comments