topic Re: date_hour not present in WinEventLogs in Splunk Search

date_hour not present in WinEventLogs

kristian_kolb — Mon, 19 Sep 2011 16:22:01 GMT

Trying to write a search that list events happening outside office hours, across a bunch of sourcetypes - however, the 'date_hour' is not available/reportable/searchable for Windows Event Logs. It just isn't there among the available fields.

e.g.

WORKS FINE: sourcetype=linuxsecure root (date_hour < 8 OR date_hour > 17)

WORKS NOT: sourcetype=wineventlog:security administrator (date_hour < 8 OR date_hour > 17)

The following search confirmed that date_hour is not extracted for WinEventLogs, i.e. the date_hour column is empty on the WinEventLog row.

* | dedup sourcetype | table date_hour, sourcetype

Is there something that could be done about this? It seems like the problem is within the way Splunk treats the WinEvt-logs, rather than something to be done at search time.

The Docs only state that default fields, such as date_*, will be extracted only if the information is present within the event itself. When looking at Windows events, they sure do have timestamps in them. Any help or clarification appreciated.

Running 4.2.1 on RH, forwarders are 4.2.2 on multiple OS's. Other events (various application logs) collected by Win-forwarders contain the date_* default fields....

Thanks in advance,

Kristian

Re: date_hour not present in WinEventLogs

gekoner — Mon, 19 Sep 2011 18:42:13 GMT

Kristian, this is not an answer but I can confirm that you should have a date_hour Field for your WinEventLogs.
I'm guessing you have something interfering with your default field extractions.
Can you upgrade to 4.2.3 on your Indexer?

Re: date_hour not present in WinEventLogs

kristian_kolb — Tue, 20 Sep 2011 13:22:48 GMT

Have not updated the RH splunk indexer yet, but I had a look at a couple of other Windows indexers, and date_hour was not available/extracted on either of them when fetching the logs through forwarders.

One of the indexers was also fetching EventLogs through WMI, and on those the date_* fields were extracted. Anyone who can shed light on this?

Thanks,

Kristian

Re: date_hour not present in WinEventLogs

Ayn — Tue, 20 Sep 2011 14:46:11 GMT

I just tested this on a Universal Forwarder v4.2.3 running on Windows 7 (Swedish language for what it's worth) forwarding to a v4.2.3 indexer on Ubuntu and can confirm that I'm not getting any date_* fields either. Normally this will happen if Splunk can't obtain a valid timestamp from an event, but I'm getting correct timestamps even for old events that were generated before I turned the log monitor on, so Splunk obviously finds and uses the timestamp.

Re: date_hour not present in WinEventLogs

Ayn — Tue, 20 Sep 2011 20:39:53 GMT

I'd say this behaviour is a bug, and you should file a case with support.

That said, there are ways to work around it in the meantime by extracting the date_hour (and other) fields you need from _time instead by using eval and strftime.

sourcetype=wineventlog:security administrator | eval date_hour=strftime(_time, "%H") | where (date_hour<8 OR date_hour>17)

I took the liberty to rewrite the condition using OR instead of AND, as date_hour<8 AND date_hour>17 will never match.

Cheers,

P

Re: date_hour not present in WinEventLogs

kristian_kolb — Tue, 20 Sep 2011 21:07:20 GMT

Thanks for pointing that one out. That's what happens when you copy someone elses code example code 🙂 The character validation was messing with my dangerous HTML characters, so I just copied somebody elses code example for searches WITHIN office hours - hence the reversed position of < and > (first edit) and the 'AND' (second edit)

The problem still persists, and I will file a support case.

Re: date_hour not present in WinEventLogs

ehoward — Wed, 21 Sep 2011 15:30:30 GMT

I hope this is fixed soon. WMI data sources are certainly critical enough that we should not have to resort to hacks like this.

Re: date_hour not present in WinEventLogs

kristian_kolb — Thu, 22 Sep 2011 09:05:30 GMT

The word from the support team is that this is a known limitation of how Splunk treat the WinEventLogs when grabbed through a forwarder (even though the docs do not mention this).

The suggested workaround is the same as Ayn mentioned;

*| eval date_hour = strftime(_time, "%H")

although I suspect one could make a permanent field extraction if date_hour for WinEventLogs is needed in more than just a few places.

Kristian

Re: date_hour not present in WinEventLogs

kristian_kolb — Thu, 22 Sep 2011 09:08:03 GMT

I have not had any real experience with using WMI to fecth WinEventLogs, but the little I have seen indicates that the date_hour field is indeed extracted properly.

Re: date_hour not present in WinEventLogs

jaxjohnny2000 — Wed, 30 Sep 2020 00:50:45 GMT

The date_hour is a Splunk default field which have timestamp information in that as generated by their respective systems. These fields come over unmodified. the _time field is presented to the user the preferences for their local time zone for display purposes

https://docs.splunk.com/Documentation/Splunk/7.2.6/Knowledge/Usedefaultfields

For example,

Assuming the Windows Server is in Pacific Standard time, and the user(me) is in Eastern time.

if the event occurred on the server at 07:37AM PST, then my time will show 10:37AM EST

So the code: *| eval date_hour = strftime(_time, "%H") will production the following output

_time = 10:37 AM
date_hour = 10
actual event time (which I want to display) = 07:37AM

So the code above merely shows the time value using the offset by the user. I want to see 07 in the date_hour field, like I would if syslog sent a record. The code does indeed create a date_hour field, but not the same date_hour which Splunk generates as a default field.

the date_* fields are only missing for Windows Events. They are visible for F5, Netscaler, and Cisco.

We have servers in all four time zones, and Hawaii.

Splunk Support tells me this unfortunately:

Unfortunately, the default date-time fields in Splunk doesn't work for Windows Event Logs as it uses API to ingest data rather the regular data ingestion pipeline.

The link below explains default fields:
https://docs.splunk.com/Documentation/Splunk/7.2.5/Knowledge/Usedefaultfields