This FAQ clarifies how timezones are handled within the UI and API.
Time displayed in the UI:
All configuration items within the UI will be displayed in your local time. This ensures you see familiar time formats while configuring rules and exceptions.
Time displayed in the API:
All timestamps returned by the API will be in Coordinated Universal Time (UTC). This is a consistent format ideal for automation purposes, allowing users to easily convert it to their desired time zone.
Example:
"createdAt": "2023-03-24T11:44:46.9382",
"updatedAt": "2023-10-16T09:13:33.7367",
Why UTC in the API?
Using UTC in the API offers several advantages:
Consistency: It ensures a standardized format for all users, regardless of their location.
Automation: Makes timestamps easier to integrate with automated processes that often rely on UTC.
Flexibility: Allows users to easily convert timestamps to their preferred time zone for better understanding.
Time displayed in Investigate:
Similar to the API, data displayed within the Investigate section will also be presented in UTC. This consistency allows for seamless conversion to any time zone for further analysis.
In summary:
The UI caters to your local time zone for configuration.
The API utilizes UTC for a consistent and flexible format for automation.
If you have any further questions regarding time zones within the UI or API, feel free to reach out to our support team.