Alerting

How to include entire source file in an alert?

jwinderDDS
Path Finder

I have an application that generates logs that are not always in a consistent format. Also each time a process in this application executes it creates a whole new log file for that one execution.

Thanks to @woodcock, I can get every event in a source file that triggered an alert. I then merge all of these event into a single field with:

error* OR fail* OR exception OR warn* | dedup source | map search="search source=$source$" | reverse | eval LOG=_raw | fields host, source, LOG | mvcombine LOG | table host, source, LOG

The problem I am having now is, if I initially get results from more than one source, they seem to get merged together in the LOG field. How can I either mvcombine only the events for their respective sources, or show the entire log file?

Thank you!

Jeremy

Tags (2)
0 Karma
1 Solution

woodcock
Esteemed Legend

I think you are looking for this:

error* OR fail* OR exception OR warn* | dedup source | map search="search source=$source$" | reverse | stats list(_raw) AS LOGS BY host, source

View solution in original post

0 Karma

woodcock
Esteemed Legend

I think you are looking for this:

error* OR fail* OR exception OR warn* | dedup source | map search="search source=$source$" | reverse | stats list(_raw) AS LOGS BY host, source
0 Karma

jwinderDDS
Path Finder

That is exactly what I've been trying to produce, with one exception. It truncates one of our longer log files because we are hitting the 1000 byte field size limit. However, this may be "good enough" for our purposes.

Thank you again!

Jeremy

0 Karma

woodcock
Esteemed Legend

Please "Accept" the answer.

0 Karma
Get Updates on the Splunk Community!

Aligning Observability Costs with Business Value: Practical Strategies

 Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...