Splunk Search

Geostats Truncating Data?

vliu2
Explorer

It would appear that using ...| geostats isn't working as it used to anymore. I originally had a search like the following in order to visualize where users were logging in from:

(index="user_logins" session="*") OR (index="ssh" password="Accepted") | iplocation IP | table user lon lat | geostats globallimit=0 count by user

I originally ran into the problem where Splunk would truncate the data shown and found that globallimit=0 appeared to be a fix. Well, it's been about a month and the problem is back (even with globallimit=0). To be exact, Splunk decides to truncate the amount of data it shows after the job finishes. It looks perfectly fine while performing the search, but then it decides to only display the geo-ip location of two users rather than a hundred or so.

Has anyone ran into this problem or have any suggestions to fix this problem?

0 Karma
1 Solution

vliu2
Explorer

It would appear that deleting ...| table user lon lat solved my problem. It's strange because it worked perfectly fine with it before. Strange.

View solution in original post

0 Karma

vliu2
Explorer

It would appear that deleting ...| table user lon lat solved my problem. It's strange because it worked perfectly fine with it before. Strange.

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