Alerting

Splunk ESS: Why does drilldown notable not working?

saveriobocca
Loves-to-Learn Lots

Hi everyone,
I have a specific question for all of you.

In Splunk ESS I created a correlation search and a notable for the monitoring Incident Review section.

I have set up a specific notable with drilldown to which I pass a field of the CS (Corralation Search)  to perform the specific search and display via the Statistics tab.

Corralation Search:

 

index=* (statusCode=4* OR statusCode=5*)  
| rename "requestTime" as Time, "statusCode" as Status, "sourceIp" as SourceIp, "httpMethod" as HttpMethod, "endpointRequestId" as "EndpointReqID"  
| stats values(Status) as Status, values(HttpMethod) as HttpMethod, count by index, SourceIp, EndpointReqID

 

Notable Drilldown

 

index=* (statusCode=4* OR statusCode=5*)  
| search sourceIp="$sourceIp$"
| rename "requestTime" as Time, "statusCode" as Status, "sourceIp" as SourceIp, "httpMethod" as HttpMethod, "endpointRequestId" as "EndpointReqID"  
| stats values(Status) as Status, values(HttpMethod) as HttpMethod, count by index, SourceIp, EndpointReqID

 

When I open the drilldown from the Notable screen, the following query is returned:

 

index=* (statusCode=4* OR statusCode=5*) 
| search sourceIp="$sourceIp$" 
| rename "requestTime" as Time, "statusCode" as Status, "sourceIp" as SourceIp, "httpMethod" as HttpMethod, "endpointRequestId" as "EndpointReqID" 
| stats values(Status) as Status, values(HttpMethod) as HttpMethod, count by index, SourceIp, EndpointReqID

 

Instead of:

 

index=* (statusCode=4* OR statusCode=5*)  
| search sourceIp="129.12.x.x"
| rename "requestTime" as Time, "statusCode" as Status, "sourceIp" as SourceIp, "httpMethod" as HttpMethod, "endpointRequestId" as "EndpointReqID"  
| stats values(Status) as Status, values(HttpMethod) as HttpMethod, count by index, SourceIp, EndpointReqID

 

Why is the $sourceIp$ field not recognized and replaced with the IP address of the CS so that it can perform a specific search?

What is the error?

Thank you all!

Labels (2)
0 Karma

alonsocaio
Contributor

Hey @saveriobocca , just confirming, on your first search (Correlation Search) you have renamed sourceIp to SourceIp. Have you tried using "$SourceIp$" instead of "$sourceIp$" on your drilldown search?

Field names are case-sensitive, so if the token is generated as SourceIp on the correlation search it needs to be the same way on the drilldown.

0 Karma

saveriobocca
Loves-to-Learn Lots

Hi @alonsocaio  thank you for the response.

Yes, after this I tried to write the variable like this "$SourceIp$" but it doesn't work again.

What do you think it could be?
It almost seems that the value is not passed to the variable.

0 Karma
Get Updates on the Splunk Community!

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...

[Live Demo] Watch SOC transformation in action with the reimagined Splunk Enterprise ...

Overwhelmed SOC? Splunk ES Has Your Back Tool sprawl, alert fatigue, and endless context switching are making ...

What’s New & Next in Splunk SOAR

Security teams today are dealing with more alerts, more tools, and more pressure than ever.  Join us on ...