Splunk Search

How to segregate the count or limit the count to 1?

Aj01
Path Finder

index="go_pro" Appid="APP-5f" prod (":[ Axis" OR "ErrorCode" OR "System Error" OR "Invalid User :")
| rex field=_raw "ErrorDesc\:\s(?<error_caused_by>.*?)\Z"
| rex field=_raw "calldm\(\)\s\:\[\s(?<error_caused_by>.*?)\Z"
| rex field=_raw "app5f\-(?<Environment>.*?)\-\Z"
| convert timeformat="%m-%d-%Y %I:%M:%S" ctime(_time) AS time
| stats count by time error_caused_by Environment host
| reverse

 

i am using this query but in count some transactions are matching so the count is getting to 5 or 6 because that transaction were matching i want every transaction to come on different line if they are matching also.

PLease help me in segregating the count or limit the count to 1

Labels (3)
0 Karma
1 Solution

Aj01
Path Finder

i have used table instead of stats and now we are not seeing that issue as the events are not merging now

View solution in original post

0 Karma

Aj01
Path Finder

i have used table instead of stats and now we are not seeing that issue as the events are not merging now

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

You don't appear to have extract anything that identifies the transaction. You would need to do this and add it to the by clause of your stats command to split the transactions into separate "lines"

0 Karma

Aj01
Path Finder

I am using by clause but because of the same time and transaction they are coming as aggregated for transactions, i want to remove that aggregation

 

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Perhaps if you shared some anonymised events which demonstrate the issue you are facing, we might be better placed to advise. Please use the code block </> button when inserting event data so that formatting (e.g. white spaces) of the event is preserved.

0 Karma
Get Updates on the Splunk Community!

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...