To view this documentation for the Periscope Classic UI, click here.
When using the Periscope Data built-in daterange filter, there are two time zones considered: the databases's time zone and the site display time zone. The database time zone is usually in UTC as that is the default timezone for databases. The site display time zone is configured per Periscope site upon first connecting, which can be changed by Periscope Data's Support team
The date range filter converts the inputted date range from the site's display timezone to UTC (the database timezone) prior to comparing it against the timestamp column.
To ensure consistency in the selected range and the data being displayed, the timezone in the select clause can be converted to the timezone of the site. For a site in the PST timezone, the timestamp in the select clause would need to be converted to PST:
SELECT [created_at:pst:date] , count(*) FROM users WHERE [created_at=daterange] GROUP BY 1
If the date has been converted to a timezone already, or if the data is stored as a date without timestamp precision, the automatic conversion can be skipped by specifying no time zone:
For a site with a display time zone of PST, if "[created_at=daterange]" is used and 1 day is selected in the daterange filter, the results also include the following day:
As it is still the 19th in PST, the results shouldn't be inclusive of the 20th. The results are also exlcuding some data from the previous day. This is due to the underlying conversion:
The automatic conversion of the daterange selection from PST to UTC is causing the discrepancy. To avoid this, specify no time zone in the query:
Without the conversion the result includes the entire count of logs for the 19th. The underlying SQL is interpreted as: