Parsing Windows Logs

[genesiusj]

Hello,

Has anyone experienced parsing Windows Event Logs using a KVstore for all of the generic verbiage? 

For example - red text (general/static text associated with EventCode number and other values  - this will mostly be the Message/body fields) will be entered into a KVstore; green text (values within the event) will be indexed.
In the below example, there are 2,150 characters, of which, 214 characters are dynamic, and need to be indexed. The red(undant) text contains over 1,930 characters. 
These are just logon (4624) events. With over 11.5 million logon events per day across our environment, this is ~23 GB. If what I am asking can be/has been accomplished, we could reduce this to 2.3 GB.

Thanks and God bless,
Genesius

09/11/2023 12:00:00AM

LogName=Security

EventCode=4624

EventType=0

ComputerName=<computer name>

SourceName=Microsoft Windows security auditing.

Type=Information

RecordNumber=9696969696

Keywords=Audit Success

TaskCategory=Logon

OpCode=Info

Message=An account was successfully logged on.

Subject:

                Security ID:                         NT AUTHORITY\SYSTEM

                Account Name:                 <account name>

                Account Domain:                              <account domain>

                Logon ID:                             0x000

Logon Information:

                Logon Type:                        3

                Restricted Admin Mode:               -

                Virtual Account:                No

                Elevated Token:                 Yes

Impersonation Level:                      Identification

New Logon:

                Security ID:                         <security id>

                Account Name:                 <account name>

                Account Domain:                              <account domain>

                Logon ID:                             0x0000000000

                Linked Logon ID:                               0x0

                Network Account Name:               -

                Network Account Domain:           -

                Logon GUID:                       <login guid>

Process Information:

                Process ID:                          0x000

                Process Name:                   D:\Program Files\Microsoft System Center\Operations Manager\Server\Microsoft.Mom.Sdk.ServiceHost.exe

Network Information:

                Workstation Name:         <workstation name>

                Source Network Address:             -

                Source Port:                        -

Detailed Authentication Information:

                Logon Process:                  <login process>

                Authentication Package: <authentication package>

                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.