Splunk Search

How to display/access parameters after grouping?

KAKA
New Member

For example I have getting splunk logs with 4 fields 

 

TimeEvent
time 1service = "service1"  | operation = "sampleOperation1" | responseTime = "10" | requestId = "sampleRequestId1"
time2service = "service2"  | operation = "sampleOperation2" | responseTime = "60" | requestId = "sampleRequestId2"
time3service = "service2"  | operation = "sampleOperation2" | responseTime = "60" | requestId = "uniqueRequestId3"
time4service = "service4"  | operation = "sampleOperation4" | responseTime = "30" | requestId = "sampleRequestId4"

 

My objective is to find from all the logs if count is greater then 20 for  combination of (service,operation) with reponseTime>40.

Expected Output

service1  operation1  [sampleRequestId2,uniqueRequestId3]

 

The query I have for now is

search here......

| stats count(eval(responseTime>60)) as reponseCount
by service, operation
| eval title= case(
                              match(service,"service2") AND reponseCount>20, "alert1",
)
| search title=*
| table title,service

 

But here I cannot refer to requestId which is being dropped. Please suggest if you any solution.

Labels (1)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Try this:

| eventstats count(eval(responseTime>40)) as responseCount
by service, operation
| where responseCount > 20 AND responseTime > 40
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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...