Getting Data In

My input is not able to get data with DB connect

justodaniel
Path Finder

We configured an Input in homologation and worked perfectly however when we were to implement in the production environment Input is not able to save the data inside Splunk.
The Query we are using is as follows:
select DATEDIFF (SECOND, '1970-01-01', Data_inicio_cadastro) as Timestamp,
*
from pineonline.dbo.vw_SplunkBaseClients;
We are using the Input type configured to choose the TimeStampo column with the following DateTime Format: yyyy-MM-dd HH: mm: ss

However in production we are receiving the following error message:
2018-06-08 21: 22: 50.466 -0300 INFO csdbx.server.task.listeners.JobMetricsListener - action = collect_job_metrics connection = AGLPNHPSQL09-PineOnline jdbc_url = null db_read_time = 34 record_read_error_count = 5312 status = COMPLETED input_name = PineOnlineBaseClient batch_size = 1000 error_threshold = N / A is_jmx_monitoring = false start_time = 2018-06-08_09: 22:50 end_time = 2018-06-08_09: 22: 50 duration = 390 read_count = 5312 write_count = 0 filtered_count = 0 error_count = 5312

Tags (1)
0 Karma

ansif
Motivator

The above message is an info to collect job metrics.

If your problem is with indexing data,then check the indexname and check if index is created under indexers.

justodaniel
Path Finder

Thank you for you answer but We checked It was missing a setting in date format. was missing the milliseconds house where should be "yyyy-MM-dd HH:mm:ss.SSSSSS" we had configured this format "yyyy-MM-dd HH:mm:ss" When we fixed the schedule, it started to work.
Thank you once again for your help.

0 Karma

ansif
Motivator

Good that it works.You can make your answer as "Accepted Answer".

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!

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 ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...