Knowledge Management

Extracting Text/Field from _raw Microsoft Event For Failed Backups

SplunkLunk
Path Finder

Greetings,

I want to run a report/alert when a MSSQL backup job has failed. It looks like the info I want is only displayed in the _raw field. Can anyone tell me how I can use the rex command to get the name of the database that has failed? The _raw event data looks like this:

2017-11-27 12:34:33.71 Backup BACKUP failed to complete the command BACKUP DATABASE WideWorldImportersDW. Check the backup application log for detailed messages.

The name of the database in this case is "WideWorldImportersDW". However, other database names will always be sandwiched between "BACKUP DATABASE" and ". Check" Can someone help me craft the rex expression to give me the text between "BACKUP DATABASE" and ". Check"? Thanks for any assistance.

Tags (1)
0 Karma
1 Solution

woodcock
Esteemed Legend

Do this:

Your Search Here
| rex "BACKUP DATABASE (?<DBName>\S+). Check"
| search NOT DBName="*"

Refine your rex until none of your events are making it past the last search filter line.

View solution in original post

0 Karma

woodcock
Esteemed Legend

Do this:

Your Search Here
| rex "BACKUP DATABASE (?<DBName>\S+). Check"
| search NOT DBName="*"

Refine your rex until none of your events are making it past the last search filter line.

0 Karma

SplunkLunk
Path Finder

So, this is what I've tried and it seems to work:

|rex field=_raw "BACKUP DATABASE (?[^\s]+). Check"

Is there a better way? I'm not sure if this will miss any events. Maybe there is a better way.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...