First of all: thank you for this awesome tool. It really looks cool and I think it will be very useful.

Problem Statement

Date/time formatting is inconsistent across the Full Dashboard UI and does not always follow the client machine’s locale.

On my system (Norway / European formats / 24-hour clock), some places display timestamps in a European style (e.g. 15.02.2026 18:42), while other parts of the UI display an English/US-style format and 12-hour clock. For example, the server list on the left shows values like:

• feb. 13, 12:23 a.m.

Some time selection/range controls also appear to be AM/PM-only, which doesn’t match locales that use 24-hour time by default.

This mix makes it harder to scan quickly and increases the chance of misreading times/dates for non-US users. This is not a critical issue, but more a nice to have.

Proposed Solution

Make date/time formatting and date/time input consistent and locale-aware throughout the Full Dashboard.

Suggested approach:

• Default all date/time rendering and input controls to the client machine’s culture/locale settings (e.g. CultureInfo.CurrentCulture / CurrentUICulture).
• Ensure time pickers support 24-hour input when the locale uses 24-hour time.
• (Optional) If you’d rather not rely only on OS locale, add a simple preference like:
  • “Use system locale for dates/times” (default on), or
  • an override format option.

Use Case

I use the Full Dashboard to monitor multiple SQL Server instances and frequently switch between servers and time ranges.

Example:

• When reviewing “Online since” in the left server list, I want timestamps to be in the same format as charts and other views (e.g. 13.02.2026 00:23 instead of feb. 13, 12:23 a.m.).
• When selecting a time range, I want to enter/choose times in 24-hour format (e.g. 18:30) and have that reflected consistently everywhere in the dashboard.

Alternatives Considered

Workarounds I’ve considered:

• Manually translating AM/PM and being extra careful with date ordering. (It always takes an extra millisecond or two to remember what AM and PM was again when you don't use it daily)
• Changing Windows regional settings to English (US), but that’s not a realistic workaround since it affects the entire machine and other apps.

A configurable dashboard setting (or fully locale-driven formatting) would be a better solution for some of us.

Additional Context

• Is this related to a specific SQL Server version?
  No — this seems to be a dashboard/UI formatting issue, independent of SQL Server version.

• Would this require schema changes?
  No — this should be formatting/display/input handling only.

• How frequently would you use this feature?
  Every time I use the dashboard (daily).

Scope

• Full Dashboard
• Lite
• SQL collection scripts
• Installer
• Documentation