Splunk Search

Missing seconds in Realtime query with 10ms span on python-sdk

timoti
Explorer

Hi, i'm trying to get Splunk realtime results using splunk's python-sdk.

Everything works well, but in the results, there is a missing second : I don't know whether there is a limitation or if I missed a parameter in the query? This is really embarrassing.

Here's my python code :

Capture d’écran 2020-11-25 à 10.49.12.pngCapture d’écran 2020-11-25 à 10.49.12.pngCapture d’écran 2020-11-25 à 10.48.59.pngCapture d’écran 2020-11-25 à 10.48.59.png

And here are the results:

As you can see, the entire second :  '2020-11-25T10:42:26' is missing, and will never appear in the results. Do you have any idea where this might come from?

Capture d’écran 2020-11-25 à 10.45.43.pngCapture d’écran 2020-11-25 à 10.45.43.png

 

I even tried to "manually" create a timechart using ' search index=_internal bin _time span=10ms | chart count by _time'; and this this case, there is a missing millisecond (not second ).

There is a missing second every 5-10 results

I can't figure out why this is not working properly.

Labels (1)
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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

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