Splunk Search

Why is the Splunk eval command in my search returning a limited number of results (10,000)?

priyankshah
New Member

I am writing a search where I am subtracting values of 2 fields and inserting into a new field using the eval command. The result always contains up to 10,000 records, even though there are more events for the search. Can some one help me understand why is it so and is there any way to change that?

When I try the same search without the eval command, it returns the actual number of events for the search.

Need urgent help with the question. Any help would be highly appreciated. Thanks!

Tags (3)
0 Karma

acharlieh
Influencer

The issue is not the eval command but rather the sort that is imposing a 10,000 result limit. If instead of:

... | sort - Difference | ...

You did:

... | sort 0 - Difference | ...

All results should be returned. (At the cost of more resource usage during the search of course).

jeffland
SplunkTrust
SplunkTrust

Can you post your search? There has to be something else in that search causing this, a subsearch for example.

0 Karma

priyankshah
New Member

Here's my search query -

index=*txn* prefetch.go | rex "eprov_rcae3=[\d]+:(?\d*)" | rex "findNgenOMOffers=[\d]+:(?\d*)"  | eval Difference=OMResponseTime-RCAEResponseTime | sort -Difference | table GSID, RCAEResponseTime, OMResponseTime, Difference
0 Karma

jeffland
SplunkTrust
SplunkTrust

Please mark your search as code, otherwise the markup will screw up special characters.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...