Activity Feed
- Got Karma for Re: Regex transforms not applied on Windows event logs. 06-17-2023 05:30 AM
- Posted Re: Regex transforms not applied on Windows event logs on Getting Data In. 06-16-2023 12:44 PM
- Karma Re: Regex transforms not applied on Windows event logs for richgalloway. 06-16-2023 12:42 PM
- Posted Regex transforms not applied on Windows event logs on Getting Data In. 06-14-2023 03:35 PM
- Posted Re: Adding a standalone Splunk Enterprise server as a cluster search peer- Am I interpreting this correctly? on Splunk Enterprise. 10-12-2022 03:03 PM
- Karma Re: Adding a standalone Splunk Enterprise server as a cluster search peer- Am I interpreting this correctly? for richgalloway. 10-12-2022 01:21 PM
- Posted Re: Adding a standalone Splunk Enterprise server as a cluster search peer- Am I interpreting this correctly? on Splunk Enterprise. 10-12-2022 12:53 PM
- Posted Adding a standalone Splunk Enterprise server as a cluster search peer- Am I interpreting this correctly? on Splunk Enterprise. 10-12-2022 12:11 PM
Topics I've Started
06-16-2023
12:44 PM
1 Karma
Thank you, the sed solution worked! I added it to my props.conf under the [WinEventLog:Security] stanza and now that extraneous text is being removed from events.
... View more
06-14-2023
03:35 PM
I wish to remove unneeded text from Windows event logs before they are indexed. Specifically, Windows event 4624 contains a dozen or so lines of text at the end that I don't want. These are sent to my clustered indexers directly from universal forwarders. I have a transform set up on the indexers to extract the fields I'm interested in: [events-win-security-4624] REGEX = EventCode=(4624)\n.*\nComputerName=(.*)?\n.*\n.*\n.*\n.*\n.*?\n.*\n.*\n\nSubject:\n.*\n*.*\n*.*\n*.*\n\nLogon Information:\n*.*\n*.*\n*.*\n*.*\n\n\n*.*\n\nNew Logon:\n\s*Security ID:\s*(.*)?\n\s*Account Name:\s*(.*)?\n\s*Account Domain:\s*(.*)?\n.*\n.*\n.*\n.*\n.*\n\n.*\n.*\n.*\n\nNetwork Information:\n\s*Workstation Name:\s*(.*)?\n\s*Source Network Address:\s*(.*)?\n\s*Source Port:\s*(.*)?\n\nDetailed Authentication Information:\n.*Logon Process:\s*(.*)? DEST_KEY = _raw FORMAT = EventCode=$1 ComputerName=$2 SecurityID=$3 AccountName=$4 AccountDomain=$5 WorkstationName=$6 SourceNetworkAddress=$7 SourcePort=$8 LogonProcess=$9 (Please pardon the lengthy regex; all it's doing is capturing the relevant fields.) And the corresponding bit from props.conf, also on the indexers: [WinEventLog:Security] TRANSFORMS-winsec_event4624 = events-win-security-4624 Based on my understanding, the transform should extract the specified fields from the raw event, put these into the format specified by the FORMAT line, send it on to be indexed, and ignore the rest. However, this is not happening. When I search my index for "EventCode=4624" I see the full event text, along with the extraneous text. It doesn't appear that the transform is doing anything. I've tested my regex against multiple events using regex101.com and everything looks correct. I've since set up a few other regex transforms to drop specific events from a different source (by sending them to nullQueue) and these are all working as expected, so I know that Splunk is able to see the conf files. I've reviewed the specifications for transforms.conf and props.conf but wasn't able to find what I'm doing wrong. Am I going about this the correct way? I'm relatively new to Splunk so I'm sure I'm overlooking something simple. Thank you for your help!
... View more
Labels
10-12-2022
03:03 PM
Update: I was able to add the standalone Splunk Enterprise server as a search peer on the new search head without any issues. Search still functions on both the old and new servers.
... View more
10-12-2022
12:53 PM
Thank you for your reply. This is the section that has me worried: Important: A search head cannot perform a dual function as a search peer. The only exception to this rule is for the monitoring console, which functions as a "search head of search heads." Maybe I'm misinterpreting this, though.
... View more
10-12-2022
12:11 PM
I am planning a migration of Splunk Enterprise to a new instance. The old instance consists of a single standalone server. The new one has a search head, an indexer cluster master, and 3 indexer cluster peers.
My original plan was this:
Add the old standalone server to the new search head as a search peer
Instruct users to search from the new search head instead of the old standalone server
Reconfigure my 300+ universal forwarders to send data to the new indexer cluster instead of the old standalone instance
Retain the old standalone server for 1 year until we no longer need the data, then decommission it
But based on the following documentation, I would also need to deactivate the search role on the old standalone server before performing step 1.
https://docs.splunk.com/Documentation/Splunk/9.0.1/DistSearch/Configuredistributedsearch
Am I interpreting this correctly?
Thanks in advance.
... View more
Labels
- Labels:
-
configuration