The SnapLogic platform consists of various components (such as Snaps, Snaplexes, APIs) and interacts with various 3rd party applications and technologies, making timezone settings an issue which demands some consideration from the user. This matrix describes how time stamps are handled across the various components of the SnapLogic platform.
| SnapLogic Component | Supported Timezone | User Configurable? | Notes |
|---|---|---|---|
| UI Dashboard | UTC | No | This setting depends on the browser, which obtains time zone information from the host Operating System (OS). This setting is not part of the SnapLogic product. |
| Snaps/Pipelines | Default UTC | Yes | Configurability depends on whether a Snap supports date/time expressions. See documentation for the specific Snap for more information. For details about supported timezone configuration for specific 3rd party applications, see Database Date Types. |
| Cloudplex | UTC | No | |
| Groundplex | User defined | Yes | Since a Groundplex is on-premise, this setting depends on the host OS timezone setting. |
| eXtremeplex | UTC | No | |
| Hadooplex | UTC | No | |
| Public API | UTC | No | You can only view timestamp information via the Activity API. |
| Tasks | User defined | Yes | Since scheduled tasks have a scheduled time to execute, a drop down menu allows the user to choose the time zone for the schedule time of task execution. |
| Error Logs | UTC | No | |
| User Notifications | Local | No | This timezone is dependent on host OS time settings. The browser uses the host OS time zone to convert to the user's local time zone. |
Timezone setting example: if you configure the timestamp of a Snaps to a local timezone, only the timestamp of the data in the pipeline is affected. Hence, the timestamp information of the pipeline activity on the Dashboard would still be dependent on the timezone settings of the host OS.