Getting Data In

How to process event exact same for events from multiple event source type?

tonopahtaos
Path Finder

Let us say you have following lines in your props.conf file:

[WinEventLog:Security]

REPORT-common = user-account-change

REPORT-win-2k3 = group-type-change

You have another event source type ABC which generates exact same events as WinEvnetLog:Security so you want to apply the same transforms to it. You can do so by adding following lines to your props.conf file:

[ABC]

REPORT-common = user-account-change

REPORT-win-2k3 = group-type-change

This duplicates these REPORT-* entries. Is it possible to support more than one source types in props.conf for the same transform items? An example is:

[WinEventLog:Security],[ABC]

REPORT-common = user-account-change

REPORT-win-2k3 = group-type-change

Tags (1)
0 Karma
1 Solution

sowings
Splunk Employee
Splunk Employee

The type of re-use you're talking about does occur in the transforms. While it's true that you have to reference each transform (i.e., "user-account-change") for each applicable sourcetype in props.conf, you're reusing the regular expression rule itself which appears in transforms.conf. Specifically with regards to Windows Event Logs, you might consider checking the source of these events in your results. It may be possible to use a single props.conf stanza (like [source::(WMI:WinEventLog|WinEventLog)...] based on source--think input path). An example of this is found in the Splunk for Windows Technology Add-on.

View solution in original post

sowings
Splunk Employee
Splunk Employee

The type of re-use you're talking about does occur in the transforms. While it's true that you have to reference each transform (i.e., "user-account-change") for each applicable sourcetype in props.conf, you're reusing the regular expression rule itself which appears in transforms.conf. Specifically with regards to Windows Event Logs, you might consider checking the source of these events in your results. It may be possible to use a single props.conf stanza (like [source::(WMI:WinEventLog|WinEventLog)...] based on source--think input path). An example of this is found in the Splunk for Windows Technology Add-on.

sowings
Splunk Employee
Splunk Employee

No problem. Note that it seems that the "..." is only available for matches beginning with [source: ], kind of like using ... in inputs.conf.

0 Karma

tonopahtaos
Path Finder

[source::(WMI:WinEventLog|WinEventLog)...] is working for me.

I tried using regex yesterday and were not lucky. The ... is the key to work.

Thanks a lot.

0 Karma

tonopahtaos
Path Finder

The WMI:WinEventLog:Security has exact same events as WinEventLog:Security.

0 Karma

kristian_kolb
Ultra Champion

To the best of my knowledge that is not possible. Also, as far as I know, there are no other applications than the Windows OS that produce the same kind of events as WinEventLog:Security.

Are you sure that you should have different sourcetypes for this data? If the format of the events are the same, then it generally IS the same sourcetype. That is pretty much the idea behind sourcetypes. Then you can have just one props.conf stanza.

/kristian

tonopahtaos
Path Finder

The WMI:WinEventLog:Security has exact same events as WinEventLog:Security.

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...