Splunk Search

Newbie struggling with removing "empty" lines for a search/report

vermicknid
New Member

Hi there! Being new and still struggling mightily to master Splunk, I have an immediate need to create a search/report that looks at when new accounts are created in AD, and what those accounts are named. If I run this over 24 hours, I get a host of timestamped "zero" lines, as no accounts were created during that time. However, at some point, there may be creations of accounts, and it those and those alone that I wish to see.

Thanks, and apologies if this is such a stupid and basic question! I'm trying to find a clue in the docs and in the book, but I'm still struggling.

Michael

Tags (1)
0 Karma
1 Solution

lukejadamec
Super Champion

Try this. You can add more fields from the event types as you see fit. There are also separate event codes for machine accounts.

EventCode=4720 OR EventCode=624 | table _time,SAM_Account_Name | dedup SAM_Account_Name

View solution in original post

0 Karma

lukejadamec
Super Champion

Try this. You can add more fields from the event types as you see fit. There are also separate event codes for machine accounts.

EventCode=4720 OR EventCode=624 | table _time,SAM_Account_Name | dedup SAM_Account_Name

0 Karma

linu1988
Champion

Use dedup to get only the unique results OR you could only use a search like this:

Index=blah sourcetype=blah NOT account_name=""|your search..

Thanks

0 Karma

sbrant_splunk
Splunk Employee
Splunk Employee

Can you post your search?

0 Karma
Get Updates on the Splunk Community!

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

 Prepare to elevate your security operations with the powerful upgrade to Splunk Enterprise Security 8.x! This ...

Get Early Access to AI Playbook Authoring: Apply for the Alpha Private Preview ...

Passionate about security automation? Apply now to our AI Playbook Authoring Alpha private preview ...

Reduce and Transform Your Firewall Data with Splunk Data Management

Managing high-volume firewall data has always been a challenge. Noisy events and verbose traffic logs often ...