> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/metrics-reference/time-and-time-zones.md). # Time and time zones Almost every figure in AMIE involves time: a count over the last day, a chart cut into days, a phrase like "13m ago", a date on a row. This page explains the kinds of time the console uses, so that when a page says "rolling 24 hours" or "calendar day" you know exactly what is meant — and why two people looking at the same screen can see different numbers. ## The kinds of time | Term | Meaning | Whose clock | | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- | | **Rolling 24 hours** | The 24 hours ending at the moment the screen loaded. A duration, so the same length for everyone | The AMIE service's clock | | **Rolling window** | A fixed length of time ending at a stated moment — now, the next whole hour, or an event such as a device's last check-in. A duration, so the same for everyone | Whichever clock computes it | | **Rolling age** | How long ago something last happened, counted back from now in whole days — the check-in bands such as **Today** and **1-7 days**, and **Days Open** on Alerts | The AMIE service's clock | | **Calendar day** | Midnight to midnight, in the time zone of the browser you are using | Your browser | | **Yesterday** | The most recent complete calendar day: from midnight yesterday up to, but not including, midnight this morning, in your browser's time zone | Your browser | | **Relative phrase** | Words such as "13m ago" or "2 days ago" beside **Last Seen**, measuring from the moment the screen last refreshed its data | Your browser | | **Displayed date and time** | A timestamp such as **Created**, shown in your browser's time zone and language format. Precision varies by column: some show the year and seconds, others month, day and minutes | Your browser | | **Displayed date** | A date with no time — **Discovered** and **Last Seen** on Access Points | Your browser | | **Service date** | The service's own calendar date, used to decide whether a license is current today | The AMIE service's clock | {% hint style="warning" %} Review: the console uses **your browser's time zone** for calendar days and for every displayed time. **Settings › Settings** shows a **Timezone** selector under **Space Configuration**, but it has no effect yet — nothing reads it — and there is no time-zone setting in your profile. The product specification is that times follow the time zone set in the user's profile, regardless of the browser's location. Until that ships, a user who travels, or who uses a computer set to a different zone, sees days cut at that computer's midnight. \[REVIEW-time-1] {% endhint %} ## What this means in practice **Two people in different time zones see different daily splits.** A call at 23:30 Denver time is "today" in Denver and "tomorrow" in London. Charts cut into calendar days put it in different bars for the two viewers. Rolling figures are unaffected — the last 24 hours is the last 24 hours for everyone. **A rolling figure and a daily figure on the same screen do not line up.** On the Dashboard, the large figure on each call tile is a rolling 24 hours; the trend line beneath it is seven calendar days ending yesterday. Today is in the figure and not on the line; part of yesterday is in both. **Most day-based charts include today.** A range of "the last seven days" runs to midnight **tonight**, so its last day is today-so-far and grows through the day. The Dashboard's trend lines are the exception: they stop at midnight this morning, so today never appears on them. **"Yesterday" is a whole day.** When a page compares yesterday with the day before, it compares two complete calendar days, not two rolling windows. **Relative phrases do not tick.** "13m ago" is worked out each time the row is drawn — after a search, a filter, a group change or a reload — not continuously. Leave a screen open and the phrases stay as they were. **Twice a year, one boundary can be an hour off.** On the Dashboard trend lines, Devices overview **In-Use**, **Daily Usage Statistics** and **Battery Consumption by App**, the range is measured back from midnight in whole 24-hour steps, so in the week a clock change happens its earliest boundary lands an hour before or after that day's midnight. Performance's day ranges count calendar days and are unaffected. ## Which figures use which | Screen | Figure | Kind of time | | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | Dashboard | **checked in last 24h** on the two fleet cards | Rolling 24 hours | | Dashboard | Device Status bands (**Today**, **1-7 days** …) | Rolling age | | Dashboard | **Available Licenses** — whether a license is current | Service date | | Dashboard | The large figure on **Call Performance**, **Call Volume**, **Call Minutes** | Rolling 24 hours | | Dashboard | **Yest.**, the change percentage, and the trend lines | Calendar days, ending yesterday | | Devices overview | Device Status bands | Rolling age | | Devices overview | **In-Use** bars | Calendar days, the last seven, ending tonight | | Devices Inventory | The **Last Seen** filter (**Today**, **1-7 days** …) and the **Last Seen** column | Rolling age; shown as a relative phrase | | Device details | **Last Seen** and **Last Check-in** — the same moment shown under two labels | Displayed date and time | | Device details | **Call History** — **Start**, **End** (month, day and time) | Displayed date and time | | Device details | **Daily Usage Statistics** | Calendar days, the last seven, ending tonight | | Device details | **Top App Consumption** | Rolling window: everything from seven days before that device's own last check-in onward. Not your browser's clock | | Batteries | **Offline >7d** and the check-in distribution behind it | Rolling age | | Batteries | **Battery Consumption by App** with its **Time Range** | **Today**: the current calendar day. **Yesterday**: yesterday. **Last 7 Days** and longer: calendar days ending tonight | | Batteries Inventory | **Last Seen** | Relative phrase | | Battery details | **Status** — **Last seen** | Relative phrase | | Battery details | **Status** — **Online** / **Offline** | Rolling window: the 24 hours before the page loaded, on your browser's clock | | Battery details | **Charge / Discharge · Last 24h** | Rolling 24 hours | | Performance | **Today** | Calendar day so far: from your browser's midnight this morning to the next whole hour, in hourly points | | Performance | **24h** | Rolling window: the last 24 whole hours, ending at the next whole hour on your browser's clock | | Performance | **7d**, **30d**, **90d** | Calendar days, ending tonight | | Alerts | **Created**, **Modified** | Displayed date and time | | Alerts | **Days Open** | Rolling age, counted from the alert's trigger time — recorded separately from **Created** | | Access Points | **Last Seen**, **Discovered** | Displayed date | | Device details | **Top App Consumption** cycle tabs (start and end of each cycle), **Daily Usage Statistics** first- and last-use times and day labels, **Session Activity** ticks and event times, **Log Bundles** — **Created** | Displayed date and time | | Battery details | Chart axis and the "battery last seen" phrase in the chart heading | Axis: your browser's time zone. Phrase: relative phrase | | Settings › Licenses | Order date | Displayed date | | Any chart | The labels along a time axis — weekday names, hours, dates | Displayed date, in your browser's time zone and language | {% hint style="warning" %} TODO: \*\*Days Open\*\* counts from the alert's trigger time, and \*\*Created\*\* shows when the alert was recorded. Confirm how the two relate for a reader — are they ever meaningfully different? {% endhint %} ## Reading a chart cut into days * On charts that end tonight, the **last** bar or point is today-so-far and is not comparable with the completed days before it until the day ends. * On the Dashboard's trend lines, which end this morning, **today does not appear** even though today's activity is in the rolling figure above the line. * Day labels are the browser's: the same bar is labeled **Mon** for one viewer and **Tue** for another if their midnights differ. ## Related * [Dashboard](/amie-advanced/using-the-platform/dashboard.md) — rolling and calendar figures side by side * [Performance](/amie-advanced/using-the-platform/performance.md) — five time ranges of three different kinds --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spectralink.net/amie-advanced/metrics-reference/time-and-time-zones.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.