All Apps and Add-ons

Splunk DB Connect 2: Why am I getting "Validation error: jdbcUrlFormat is a mandatory parameter for the database connection."?

ashish_ray
New Member

I am trying to integrate Splunk DB Connect 2 (Latest), after putting the following settings in “db_connection_types.conf” local file

[mongo]
displayName = MongoDB
jdbcDriverClass = mongodb.jdbc.MongoDriver
connectionUrlFormat = jdbc:mongo://{0}:{1}/{2}
testQuery = SELECT 1

[unity]
displayName = Unity
jdbcDriverClass = unity.jdbc.UnityDriver
connectionUrlFormat = jdbc:unity://{0}
testQuery = SELECT 1 

I get this message on the connection UI page while validating MongoDB JDBC driver (third party):

jdbcUrlFormat is a mandatory parameter for the database connection.

0 Karma

egcthistle
Explorer

There were some changes to the format of the db_connection_types.conf.

Specfically 'connectionUrlFormat' changed to 'jbdcUrlFormat' and 'defaultport' to 'port'

for your case:
connectionUrlFormat = jdbc:mongo://< host>:< port>;databaseName=< database >

General:
jdbcUrlFormat = jdbc:whateverDB://< host>:< port>;databaseName=< database>

jdbcUrlSSLFormat = jdbc:whateverDB://< host>:< port>;databaseName=< database>whatever SSL conn string you use
port = 5432
serviceClass = com.splunk.dbx2.MSSQLJDBC

You also might need 'serviceClass', it was needed for MS SQL, not sure about Mongo/others.

0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...