Connection Issue with Primary/Secondary database

[subin-basukala]

I'm submitting a ...

• [x] bug report
• [ ] feature request

What is the current behavior?

On my Data Source Name if I put Primary and Secondary database IP's I get error saying too many colons in address. Here is the full error

caller=collector.go:262 level=error Errorpingingoracle:="address primary-ip:1521,secondary-ip:1521: too many colons in address"

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

My data source name is set as below: DATA_SOURCE_NAME=oracle://oracledb_exporter:password@primary-ip:1521,secondary-ip:1521/IFSTDM

What is the expected behavior?

It should not give error when primary/secondary host is specified on the Data Source Name and listed in the example. https://github.com/iamseth/oracledb_exporter#using-a-multiple-host-data-source-name:~:text=VALUE1%5B%26OPTIONn%3DVALUEn%5D...%5D-,For%20Example%3A,-%23%20export%20Oracle

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

I am connecting to EC2 database from kubernetes pod which has oracledb_exporter running. Version: ghcr.io/iamseth/oracledb_exporter:0.5.1

[eagle-rr]

I'm seeing this issue as well.