Seq works with event and time-series data, and has many features for working with date and time data.
Seq internally measures time in 100-nanosecond ticks. For example, Seq will represent a one-minute interval as
Because durations in ticks are very large numbers, Seq provides a shorthand syntax for describing durations. One minute is written as
1m, which is just another way of saying
600000000 (but much easier on the eyes).
Duration literals can be specified as any whole number of days (
d), hours (
h), minutes (
m), seconds (
s) and milliseconds (
ms), and these can be chained together to represent more complex durations such as
Durations can be formatted nicely using
ToTimeString(1h30m) will return the string
Seq represents timestamps and datetimes using the same 100-nanosecond ticks, from a zero value at midnight on January 1st on the year 0001.
Most of the time, datetime values will be encountered through the
@Timestamp property on an event, but values of the same type can be created by calling the
Now() function, or by parsing an ISO-8601 date/time string using
Adding or subtracting the value of two durations will produce the expected values:
1d + 30m will evaluate to
Adding or subtracing a duration from a datetime will also produce what's expected:
Now() - 7d will evaluate to the instance seven days ago.
Many Seq features work server-side, and sometimes unattended, so expressions in queries don't have a single notion of the current time zone, and instead rely on the
OffsetIf() function to compute time zone offsets where required.
-- Prints 10:00 select ToTimeString(OffsetIn('Australia/Brisbane', Now())
OffsetIn() accepts an IANA time zone name.
Because of daylight savings time,
OffsetIn(), also needs a point in time at which to compute the offset. This can be specified using an event's
@Timestamp, by calling the
Now() function, or by parsing an ISO-8601 date time string with
DatePart() is used to break a datetime into its constituent parts. It can answer questions like:
Did the event occur on a Wednesday?
DatePart(@Timestamp, 'weekday', OffsetIn('Australia/Brisbane', @Timestamp)) = 3
DatePart(@Timestamp, 'month', OffsetIn('Australia/Brisbane', @Timestamp)) = 6
DatePart() function needs a time zone offset, computed in these examples using
OffsetIn(), because whether a point in time is a Tuesday or Wednesday depends on in which time zone it's being observed.
The examples above use
OffsetIn() to compute an offset, but if you're working with a fixed offset you can specify it directly using a duration literal like
|The date/time representing 0:00 (midnight AM) at |
|The duration from midnight AM to the specified |
|The year component of |
|The month component of |
|The day component of |
|The hour component of |
|The minute component of |
|The second component of |
|The day of week, as an integer where Sunday = 0, Monday = 1, ...|
Updated about a month ago