I have a working Splunk DB Connect that I am trying to extend.
This is on a heavy forwarder that is pushing the data to Splunk Cloud
I have created new identities and validated collections, however, when trying to use the new (or old) connections I am now receiving the following error com.splunk.dbx.exception.NotFoundException: Can not find object XXXXXX of type connection.
I have found in the logs the following error:
127.0.0.1 - splunk [10/Jan/2020:16:02:11.761 -0800] "GET /servicesNS/admin/-/configs/conf-db_connections/XXXXXX HTTP/1.1" 404 144 - - - 0ms
The main user is actually called splunk
and when splunk
appears in logged urls rather than admin
the 404 is replaced by 200
-- Why is the system using admin username during setup but splunk during execution and how do I stop this?
Hi,
I have basically the same issue.
Splunk 8.0.2 on Windows Server.
For me it is the user ids admin where it works and splunkadm where it does not.
splunkd_access.log:127.0.0.1 - splunkadm [05/Mar/2020:10:09:46.237 +0100] "GET /servicesNS/splunkadm/-/configs/conf-db_connections/mfs_dms_dwdb HTTP/1.1" 200 5712 - - - 0ms
splunkd_access.log:127.0.0.1 - splunkadm [05/Mar/2020:10:09:48.608 +0100] "GET /servicesNS/admin/-/configs/conf-db_connections/mfs_dms_dwdb HTTP/1.1" 404 144 - - - 0ms
So why are user specific paths used here?
The net effect is, none of the queries work.
And one cannot configure the db_connect app by commandline as one needs to go through the gui to set up the status files in modinputs\server\splunk_app_db_connect.
thx
afx
Hi!
I'm also getting this problem. Any ideas on how to solve it?
Regards. Jorge