Hi! Does anyone know if it's possible to change the timezone in which traces, etc are displayed in the Phoenix web app (self hosted)? Right now they are displaying in local timezone and I'd much rather have them be in UTC, which corresponds to other timestamps I have in logging and database entries. Not, I don't want to change this for everyone using that Phoenix instance. Just me! 馃槉
Phoenix's web app displays trace times in your browser's local timezone and does not provide a user-specific setting to display traces in UTC; there is no built-in option to change the display timezone just for your user in a self-hosted instance. All users see times localized to their browser, and timezone customization per user is not supported in the current UI or configuration options according to official documentation and community responses. If you need UTC display, you would need to convert times manually or adjust your browser/system timezone, but this would affect all web browsing, not just Phoenix. For more details, see the discussion in the Phoenix community and documentation, which confirm this limitation and suggest that all timestamps are shown in the browser's local timezone by design, with no per-user override available at this time. Would you like more detail on possible workarounds or future roadmap? Sources: - Slack Community Discussion
馃挕聽Hint: Mention RunLLM in the thread for followups.
Yes, please RunLLM
Phoenix always displays timestamps in the browser's local timezone by default, and there is currently no built-in per-user setting to display times in UTC within the web UI. This behavior is confirmed by both the Phoenix team and community: "everything in the UI gets localized to your browser鈥檚 timezone" and "Phoenix is our open source product... The docs you linked are for the Arize AX product"鈥攖he commercial version, which may have different features. There is no user preference or toggle for UTC display in the open-source Phoenix UI, and all users see times based on their browser settings, not a configurable Phoenix setting or profile option. Workarounds:
- You can temporarily set your browser or system timezone to UTC, which will cause Phoenix (and all other sites) to display times in UTC, but this is a global change and not user-specific within Phoenix.
- For programmatic access, when you export or query data via the Python client or API, timestamps are stored and returned in UTC, so you can process or display them as you wish outside the UI.
- There is no current roadmap item or open feature request for per-user timezone settings in the open-source Phoenix UI. If this is important for your workflow, you may consider submitting a feature request on the Phoenix GitHub issues page.Summary of technical details:
- Timestamps are stored and processed in UTC on the backend, but the frontend (UI) uses JavaScript's toLocaleString() and similar methods to display times in the browser's local timezone (source code example).
- There is a React hook to get the UTC offset from the browser (useUTCOffsetMinutes.ts), but no user-facing control to override this.
- The only way to see UTC in the UI is to set your browser/system timezone to UTC.Let me know if you want code snippets for exporting data in UTC or more details on how timestamps are handled internally.Sources:
- Slack Community Discussion
- source code example
- useUTCOffsetMinutes.ts
馃挕聽Hint: Mention RunLLM in the thread for followups.
That's unfortunate.
Hey Matthew R. your request makes sense. Feel free to file us an issue on public GitHub. We're heads down on a bunch of stuff but we might have someone pick up the issue given Phoenix is open-source.
Will do, thanks Mikyo!
