Getting Data In

Db connect HTTP 400 Error

Nawab
Communicator

I am getting below error on my dbconnect, every thing was working fine

HTTP Error 400, HEC response body: {"text":"Invalid data format","code":6,"invalid-event-number":15}, trace: HttpResponseProxy{HTTP/1.1 400 Bad Request [Date: Mon, 29 Sep 2025 10:35:01 GMT, Content-Type: application/json; charset=UTF-8, X-Content-Type-Options: nosniff, Content-Length: 65, Vary: Authorization, Connection: Keep-Alive, X-Frame-Options: SAMEORIGIN, Server: Splunkd] ResponseEntityProxy{[Content-Type: application/json; charset=UTF-8,Content-Length: 65,Chunked: false]}}

Labels (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Can you tell more about this?

  • Where you are getting this?
  • What you have actually try/done?
  • What is your environment?
  • What DB you have?
  • What are your versions (splunk, dbx, jdbc drivers/packages, OS, target db etc.)
  • Is this db_input or something else?
  • Or are you initially configure your DB Connection to source DB?
0 Karma

Nawab
Communicator

no we haven't changed anything on our query

0 Karma

PrewinThomas
Motivator

@Nawab 

Have you modified any of your query? Can you specify more details.

The error highlights here can be of multiple reasons 

{"text":"Invalid data format","code":6,"invalid-event-number":15}


Regards,
Prewin
If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...