Getting Data In

How to use regex for just extracting and indexing custom fields of windows eventlogs?

amiritc
New Member

Hi Splunker

I have question about how to use regex for just extract and index custom fields of windows eventlogs. for example, for event id=4624 i need to extract fields like logname source eventid level and their values and to index just this fields in my indexer for reducing volume of windows eventlog. Thanks for your helps splunkers.

0 Karma
1 Solution

493669
Super Champion

You can replace the other portion of the events with blank during index time, so only the necessary information gets logged.
http://docs.splunk.com/Documentation/Splunk/6.2.4/Data/Anonymizedatausingconfigurationfiles#Anonymiz...

have look at this answer-
https://answers.splunk.com/answers/294027/how-to-index-specific-fields-of-a-windows-event-lo.html

View solution in original post

0 Karma

amiritc
New Member

Please help how i can make the proper regex for this log

An account was successfully logged on.

Subject:
Security ID: SYSTEM
Account Name: PC-JALILZADEH$
Account Domain: WORKGROUP
Logon ID: 0x3E7

Logon Information:
Logon Type: 5
Restricted Admin Mode: -
Virtual Account: No
Elevated Token: Yes

Impersonation Level: Impersonation

New Logon:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3E7
Linked Logon ID: 0x0
Network Account Name: -
Network Account Domain: -
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x408
Process Name: C:\Windows\System32\services.exe

Network Information:
Workstation Name: -
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: Advapi

Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The impersonation level field indicates the extent to which a process in the logon session can impersonate.

The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

0 Karma

mstjohn_splunk
Splunk Employee
Splunk Employee

@amiritc

Is this post more information about the query listed above, or is this for a different question? If it's additional information for the above query, can you please add it to your original question post?

0 Karma

493669
Super Champion

You can replace the other portion of the events with blank during index time, so only the necessary information gets logged.
http://docs.splunk.com/Documentation/Splunk/6.2.4/Data/Anonymizedatausingconfigurationfiles#Anonymiz...

have look at this answer-
https://answers.splunk.com/answers/294027/how-to-index-specific-fields-of-a-windows-event-lo.html

View solution in original post

0 Karma

amiritc
New Member

in this case we just remove value of field not value and fields both

0 Karma
Did you miss .conf21 Virtual?

Good news! The event's keynotes and many of its breakout sessions are now available online, and still totally FREE!