Getting Data In

IndexScopedSearch and default ingest timestamp

ellothere
Explorer

Splunk Enterprise. Version: 7.2.3. Build: 06d57c595b80.

New dataset of a 70 MB log file. The timestamp of the log file was based on seconds the device operated, not a traditional month, day, year, etc... When I ingested the file to Splunk, it was assigned the default timestamp of the time of ingest since there was no discernible timestamp. I wanted to round the time to the nearest tenth of a second since further granularity is not needed at this point:
index=main source="03182019.csv"
| eval appTime=round(time)
| stats c by appTime
| sort appTime

When I try doing this search I receive this error:
Error in 'IndexScopedSearch': The search failed. More than 1000000 events found at time 1553486400.
Understandably, this is a lot of events but is there no way to increase the limit so searches like this can be run? Currently, it only returns chunks of the data and there are large amounts of it missing.

0 Karma

secrecys
Explorer

We are experiencing this issue when creating summaries with more than 1M results... 

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...