Splunk Enterprise

Creating Event / Alert trigger based upon regex count

Pmeiring
Explorer

Hi All, 

I'm trying to create a alert/event when a regex field count is above 30. I however cannot save as event "that includes pipe operator".

The output show exactly the values I want, but I'm not able to create a alert/event. Is there any alternatives or better ways to create events/alerts for these ? 

Regex - Public_IP_Test
(?s)from\s+(?P<Public_IP_Test>\d+\.\d+\.\d+\.\d+)\s+via\s+ssh

Search Query
host="192.168.68.1" Public_IP_Test="*" failure
| stats count as MyTestCount by Public_IP_Test
| where MyTestCount > 30

Output 
141.98.10.209 32
141.98.10.210 32
141.98.10.211 32
141.98.10.212 32
141.98.10.213 32

Example of the logs:
system,error,critical user: login failure for user pi from 141.98.10.210 via ssh
Public_IP_Test = 141.98.10.210 host = 192.168.68.1index = mainlinecount = 1source = udp:514sourcetype = syslogtimestamp = none 

Any help would be greatly appreciated 

P

 

Labels (1)
Tags (2)
0 Karma
1 Solution

isoutamo
SplunkTrust
SplunkTrust

When you are creating alert you must save it as "Alert" not as "Event Type". As that warnings tell "Event type" cannot contain anything else that base search like your 'host="192.168.68.1" Public_IP_Test="*" failure'

r. Ismo

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Please explain the problem some more.  Where do you find the quotation "that includes pipe operator"?  What exactly are you doing and how are you doing it when that appears?

Where are you using the regex?  I see it defined, but not used.

---
If this reply helps you, Karma would be appreciated.
0 Karma

Pmeiring
Explorer

Hi Richgalloway, 

Thanks for the quick response and being willing to assist.

Just to provide a bit more background, The goal is to create an alert/event if a public IP address is  repeated more than 30 times.

Step 1 - Working
Create a new field using  extract regex and name the field - Public_IP_Test
The goal is to identify and capture the IP address after the string "from "

(?s)from\s+(?P<Public_IP_Test>\d+\.\d+\.\d+\.\d+)\s+via\s+ssh

Step 2  - Working
The new field created in step 1 is available. So my query works as follows

host="192.168.68.1" Public_IP_Test="*" failure

my gateway:  host="192.168.68.1"
the new field:  Public_IP_Test="*"
Must include text called failure: failure

At this point everything seems to be in order, when the search query is ran, I see all the logs with my gateway, containing failures and the Public_IP_Test field is  capturing the IP's.  If I click on the SELECTED FIELD - Public_IP_Test I am presented with a TOP 10 hosts with their IP's, as well as their count.

Step 3 - Having Problems 

The last thing I want to add is, I want my query to display the logs only if a Public IP address has been repeated more than 30 times.  In other words I will need to count the newly created field Public_IP_Test

host="192.168.68.1" Public_IP_Test="*" failure
| stats count as MyTestCount by Public_IP_Test
| where MyTestCount > 30

This displays each Public IP and their hit count, but I am unable to save it as a query as I receive this message: You cannot base an event type on a search that includes a pipe operator or a subsearch.

Additional example of the logs
9/30/20
7:02:50.000 AM
system,error,critical user: login failure for user 666666 from 77.234.44.184 via ssh
Public_IP_Test = 77.234.44.184host = 192.168.68.1index = mainlinecount = 1source = udp:514sourcetype = syslogtimestamp = none
9/30/20
7:02:50.000 AM
system,error,critical login failure for user 666666 from 77.234.44.184 via ssh
Public_IP_Test = 77.234.44.184host = 192.168.68.1index = mainlinecount = 1source = udp:514sourcetype = syslogtimestamp = none
9/30/20
6:13:40.000 AM
system,error,critical user: login failure for user dircreate from 49.145.0.58 via ssh
Public_IP_Test = 49.145.0.58host = 192.168.68.1index = mainlinecount = 1source = udp:514sourcetype = syslogtimestamp = none
9/30/20
6:13:40.000 AM
system,error,critical login failure for user dircreate from 49.145.0.58 via ssh
Public_IP_Test = 49.145.0.58host = 192.168.68.1index = mainlinecount = 1source = udp:514sourcetype = syslogtimestamp = none
9/30/20
5:39:45.000 AM
system,error,critical user: login failure for user 888888 from 157.47.108.9 via ssh
Public_IP_Test = 157.47.108.9host = 192.168.68.1index = mainlinecount = 1source = udp:514sourcetype = syslogtimestamp = none
9/30/20
5:39:45.000 AM
system,error,critical login failure for user 888888 from 157.47.108.9 via ssh
Public_IP_Test = 157.47.108.9host = 192.168.68.1index = mainlinecount = 1source = udp:514sourcetype = syslogtimestamp = none
9/30/20
5:25:54.000 AM
system,error,critical user: login failure for user admin from 47.27.232.96 via ssh
Public_IP_Test = 47.27.232.96host = 192.168.68.1index = mainlinecount = 1source = udp:514sourcetype = syslogtimestamp = none
9/30/20

0 Karma

isoutamo
SplunkTrust
SplunkTrust

When you are creating alert you must save it as "Alert" not as "Event Type". As that warnings tell "Event type" cannot contain anything else that base search like your 'host="192.168.68.1" Public_IP_Test="*" failure'

r. Ismo

Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...