All Apps and Add-ons

How to use multiple connections in inputs.conf file of db connect v2 app

srinivasup
Explorer

*Hi Team,
Im working on Splunk DB Connect V2 app.
Recently we created identities and connect names properly and able to see valid connect for multiple connections and able to query.
used below query :
index=main | timechart count by INSTANCE_NAME
inputs.conf
[mi_inputs:oracle:database]

connectionname=Oracle_A

--
[mi_inputs:oracle:table]
connectioname=Oracle_A
index=main
source=dbx2
sourcetype=oracle:table
query=
[mi_inputs:oracle:database]
connectionname=Oracle_B
[mi_input:oracle:table]
index=main
source=dbx2
sourcetype=oracle:table
query=
I used above configuarations, when i execute the query i am expecting count by each instance.
Expected out put is :
_time Oracle_A Oracle_B
date 34 45
BUt the query is returing only one instance count.
like
_time Oracle_A Oracle_B
date 0 45
date 0 34
Can you please let me know where Im missing*

Tags (1)
0 Karma

jplumsdaine22
Influencer

If you run your db query manually do you get results? ie

| dbxquery connection="Oracle_A" query="query"

It's possible you have an error in your query. Although I am confused - in your question you said that when you run

| index=main | timechart count by INSTANCE_NAME

You get

_time Oracle_A Oracle_B
date     0     45
date     0     34

If there is no data Oracle_A you should only see a column for Oracle B ie:

_time  Oracle_B
date   45
date   34

Can you clarify the output of your splunk query?

0 Karma
Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Dynamic formatting from XML events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...