Splunk Search

Regex help Required

anandhalagaras1
Contributor

Hi All,

We are planning to ingest the SQL login success and failure logs into Splunk. So  in the logs there are lot of events but we want to ingest only the "Login succeeded for user" and "Login failed for user" information alone. So kindly help to provide the regex for the same.

Sample events looks like below:

2020-08-10 06:00:00.89 Logon Login succeeded for user 'ad\SQL_abcde123'. Connection made using Windows authentication. [CLIENT: <local machine>]
2020-08-10 06:00:01.59 Logon Login succeeded for user 'xyz'. Connection made using SQL Server authentication. [CLIENT: xxx.xxx.xxx.xxx]
2019-08-10 05:00:01.59 Logon Login failed for user ''. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only. [CLIENT: xxx.xxx.xx.xxx]

 

 

Labels (1)
0 Karma

to4kawa
Ultra Champion
0 Karma

anandhalagaras1
Contributor

@to4kawa 

 

Thanks for your swift response. So i need to write in props.conf (or) should i need to include the same in inputs.conf along with index and sourcetype information.

Or Whether do we need to have both props and transforms in place as well?

0 Karma

anandhalagaras1
Contributor

Hi 

Have mentioned in the input.conf and ingested the logs into Splunk. But still i can see other events also getting ingested as well. I just want to see the succeeded and failed events alone. so let me know how to fix it.

 

[monitor://D:\Server Location]
whitelist = (succeeded|failed) for user
sourcetype = xyz
index = abc
crcSalt = <SOURCE>
disabled = 0

 

So kindly help on this request.

0 Karma

anandhalagaras1
Contributor

Can anyone help on my request..

0 Karma

anandhalagaras1
Contributor

Can anyone help 

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 ...