as in the photo, files in which events are stored ... View more

Yes, I'm sure. I checked on Deployment-server there are no such folders for monitoring ... View more

Hi, @gcusello ! [monitor://C:\ExchData\MessageTracking\*] disabled = 0 index = MyIndex sourcetype = MySourcetype #FcrcSalt = <SOURCE ... View more

Log Name: Security EventCode: 4624 EventType: 0 ComputerName: MY_ComputerName SourceName: Microsoft Windows security auditing. Type: Information RecordNumber: 93370261535 Keywords: Audit Success TaskCategory: Logon OpCode: Info Message: An account was successfully logged on. Subject: Security ID: S-1-0-0 Account Name: - Account Domain: - Logon ID: 0x0 Logon Information: Logon Type: 3 Restricted Admin Mode: No Virtual Account: No Elevated Token: Yes Impersonation Level: Impersonation New Logon: Security ID: S-1-5-21-877741627-2216037581-1742749770-81699 Account Name: MY_Account Name Account Domain: MY_Account Domain Logon ID: 0x2153A91CB Linked Logon ID: 0x0 Network Account Name: - Network Account Domain: - Logon GUID: {-} Process Information: Process ID: 0x0 Process Name: - Network Information: Workstation Name: - Source Network Address: MY_Source Network Address Source Port: Port Detailed Authentication Information: Logon Process: Kerberos Authentication Package: Kerberos Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon session is created. 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. ... View more

If I use blacklist, how can I filter by multiple events at once? I need to filter by Account_Name, Source_Network_Address and eventcode. How stanza will look? ... View more

App on deployment-server. I think, filtering by props and transform is better, but maybe I'm wrong) ... View more

the problem is that data from hosts where data is coming to a mounted disk does not come to Splunk ... View more

Yes, it is a mistyping, in my inputs.conf i got it right. ... View more

Hi, richgalloway! Thank you for your answer.  I wrote this information in response to the previous question from Giuseppe. ... View more

Hi, Giuseppe! Thank you for your answer. Let me explain the situation. The application is configured to collect logs from four hosts, on two of which the data is collected in the internal storage C:\Program Files\Microsoft\Exchange Server\... and the data comes from these hosts correctly. On the other two hosts the data is collected in a folder that is moved to a separate disk C:\MyFolder\MyFolder1\*. My stanza looks like: [monitor://C:/MyFolder\MyFolder1/*] disabled = 0 index = MyIndex1 sourcetype = MySourcetype1   [monitor://C:/Program Files/Microsoft/Exchange Server/.../*] disabled = 0 index = MyIndex1 sourcetype = MySourcetype1# ... View more