<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009yRztcCACOkta Classic EngineAdministrationAnswered2025-09-13T09:01:51.000Z2024-01-22T04:56:12.000Z2024-01-22T22:05:43.000Z

lnllt (lnllt) asked a question.

What timezone should we use for "since" in the System Logs API?

What timezone should we use for "since" in the System Logs API?

 

It's not specified in https://developer.okta.com/docs/reference/api/system-log/.

 

Is it the same as the reports?

 

If so there is contradictory information on https://support.okta.com:

 

This says it's Pacific Time:

https://support.okta.com/help/s/question/0D50Z00008G7UcBSAV/what-is-the-time-zone-in-the-system-log-report-records

 

This says it's UTC:

https://support.okta.com/help/s/article/default-timezone-for-okta-reports


  • a0n5s (a0n5s)

    https://developer.okta.com/docs/reference/api/system-log/

    Parameter

    since

    Description

    Filters the lower time bound of the log events published

    Format

    property for bounded queries or persistence time for polling queriesThe Internet Date/Time Format profile of ISO 8601 (opens new window), for example: 2017-05-03T16:22:18Z

    Default

    7 days prior to until

     

     

    5.6. Internet Date/Time Format

     

    The following profile of ISO 8601 [ISO8601] dates SHOULD be used in

    new protocols on the Internet. This is specified using the syntax

    description notation defined in [ABNF].

     

    date-fullyear = 4DIGIT

    date-month = 2DIGIT ; 01-12

    date-mday = 2DIGIT ; 01-28, 01-29, 01-30, 01-31 based on

    ; month/year

    time-hour = 2DIGIT ; 00-23

    time-minute = 2DIGIT ; 00-59

    time-second = 2DIGIT ; 00-58, 00-59, 00-60 based on leap second

    ; rules

    time-secfrac = "." 1*DIGIT

    time-numoffset = ("+" / "-") time-hour ":" time-minute

    time-offset = "Z" / time-numoffset

     

    partial-time = time-hour ":" time-minute ":" time-second

    [time-secfrac]

    full-date = date-fullyear "-" date-month "-" date-mday

    full-time = partial-time time-offset

     

    date-time = full-date "T" full-time

     

    NOTE: Per [ABNF] and ISO8601, the "T" and "Z" characters in this

    syntax may alternatively be lower case "t" or "z" respectively.

     

    This date/time format may be used in some environments or contexts

    that distinguish between the upper- and lower-case letters 'A'-'Z'

    and 'a'-'z' (e.g. XML). Specifications that use this format in

    such environments MAY further limit the date/time syntax so that

    the letters 'T' and 'Z' used in the date/time syntax must always

    be upper case. Applications that generate this format SHOULD use

    upper case letters.

     

    NOTE: ISO 8601 defines date and time separated by "T".

    Applications using this syntax may choose, for the sake of

    readability, to specify a full-date and full-time separated by

    (say) a space character.

     

    So Z means UTC.

     

    but in the web, it can select.

    https://help.okta.com/en-us/content/topics/reports/syslog-filters.htm

    • Time Zone: Use the drop-down box to select a time zone in which the system log events are displayed.

     

     

    Expand Post
    Selected as Best
  • a0n5s (a0n5s)

    https://developer.okta.com/docs/reference/api/system-log/

    Parameter

    since

    Description

    Filters the lower time bound of the log events published

    Format

    property for bounded queries or persistence time for polling queriesThe Internet Date/Time Format profile of ISO 8601 (opens new window), for example: 2017-05-03T16:22:18Z

    Default

    7 days prior to until

     

     

    5.6. Internet Date/Time Format

     

    The following profile of ISO 8601 [ISO8601] dates SHOULD be used in

    new protocols on the Internet. This is specified using the syntax

    description notation defined in [ABNF].

     

    date-fullyear = 4DIGIT

    date-month = 2DIGIT ; 01-12

    date-mday = 2DIGIT ; 01-28, 01-29, 01-30, 01-31 based on

    ; month/year

    time-hour = 2DIGIT ; 00-23

    time-minute = 2DIGIT ; 00-59

    time-second = 2DIGIT ; 00-58, 00-59, 00-60 based on leap second

    ; rules

    time-secfrac = "." 1*DIGIT

    time-numoffset = ("+" / "-") time-hour ":" time-minute

    time-offset = "Z" / time-numoffset

     

    partial-time = time-hour ":" time-minute ":" time-second

    [time-secfrac]

    full-date = date-fullyear "-" date-month "-" date-mday

    full-time = partial-time time-offset

     

    date-time = full-date "T" full-time

     

    NOTE: Per [ABNF] and ISO8601, the "T" and "Z" characters in this

    syntax may alternatively be lower case "t" or "z" respectively.

     

    This date/time format may be used in some environments or contexts

    that distinguish between the upper- and lower-case letters 'A'-'Z'

    and 'a'-'z' (e.g. XML). Specifications that use this format in

    such environments MAY further limit the date/time syntax so that

    the letters 'T' and 'Z' used in the date/time syntax must always

    be upper case. Applications that generate this format SHOULD use

    upper case letters.

     

    NOTE: ISO 8601 defines date and time separated by "T".

    Applications using this syntax may choose, for the sake of

    readability, to specify a full-date and full-time separated by

    (say) a space character.

     

    So Z means UTC.

     

    but in the web, it can select.

    https://help.okta.com/en-us/content/topics/reports/syslog-filters.htm

    • Time Zone: Use the drop-down box to select a time zone in which the system log events are displayed.

     

     

    Expand Post
    Selected as Best
This question is closed.
Loading
What timezone should we use for "since" in the System Logs API?