Every ticket raised in Foreman, its status changes, who handled it, how long it took, and how many were open at any point in time.
Part of the Foreman Intelligence Data Dictionary. Model: customer_access. Generated from the live Looker model on 2026-09-04.
Contents
Explores in this group
Ticket Data ticket_history
Looker description: Historical ticket information
Every event in the life of a Foreman ticket, one row per event: creation, status changes, diagnoses, and closure, with who did it and which miner it was about. A Ticket Facts view rolls those events up to one row per ticket (created, closed, current status, resolution time), and miner telemetry and details are joined so tickets can be analyzed alongside the miner they concern.
| Grain | One row per ticket event (Ticket History) or one row per ticket (Ticket Facts) |
| Time field | Timestamp Date on events, Created Date and Closed Date on Ticket Facts |
| Best for |
|
Example questions
- How many tickets were closed per week this quarter, and what was the median resolution time?
- Which open tickets are more than 7 days old?
- Which miner types generate the most tickets?
Views in this explore: Client Power Cost, Coin Hash Price, Miner Data, Miner Details (Current), Ticket Facts, Ticket History, Ticket History: Custom Field
Tickets Open Over Time open_tickets_over_time
Looker description: Hourly snapshot of how many tickets were open at each point in time
A small explore that answers one question well: how many tickets were open at each hour. It is precomputed, so it is the fastest way to draw a backlog trend line, and it includes a filter-only field to set the time range without changing the shape of the result.
| Grain | One row per hour |
| Time field | Timestamp Date, controlled by the Timestamp Filter |
| Best for |
|
Example questions
- How has our open ticket count changed over the last 90 days?
- What was the peak backlog last month, and when?
Views in this explore: Open Tickets Over Time
Fields by view
Each explore is built from one or more views. A view is a set of related fields, and the tables below list every visible field in each view this article owns. Dimensions are attributes you can group and filter by. Measures are aggregates that add up, average, or count across the rows you select.
Ticket History
One row per event in the life of a ticket: creation, status changes, comments, diagnoses, miners or devices added or removed, and closure. Each event records who did it, when, and the state of the miner at the time.
Used by: Ticket Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| Action | Text | What happened: add, change, change-state, change-location, comment, delete, add-miner, remove-miner, add-device, remove-device, or add-asset. |
| Client ID | Number | Numeric ID of the client the ticket belongs to. |
| Client Name | Text | Name of that client. |
| Created By | Text | User who created the ticket. |
| Data | Text | Free-text payload of the event, such as the comment text or the values that changed. |
| Device | Text | The device the ticket concerns, usually the miner type plus its MAC address. |
| Diagnosis | Text | Diagnosis recorded on the ticket, if any, for example 202 Error or No Diagnosis. |
| Is Status Closed (Yes / No) | Yes / No | Yes if this event set the ticket's status to closed. |
| Item Type | Text | The item or problem the ticket was raised for, as typed by the user. Free text, often a serial number and a fault description. |
| Mac ID | Text | MAC address of the miner the ticket concerns. |
| Miner ID | Number | Foreman ID of the miner the ticket concerns. |
| Miner State | Text | State of the miner at the time of the event: deployed, in-repair, in-storage, or retired. |
| Status | Text | Ticket status after this event: pending, in-progress, ready-to-review, rma, or closed. |
| Ticket Created Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When the ticket was originally created. |
| Ticket ID | Number | Foreman's numeric ID for the ticket. |
| Timestamp Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When this event happened. |
| User | Text | User who performed the event. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Count | Count | Number of event rows in the selection. |
| Count Distinct Tickets | Count (distinct) | Number of distinct tickets in the selection. |
| Count Events | Count | Number of ticket history events in the selection. Same as Count. |
| Has Closed Status (Yes / No) | Yes / No | Yes if the ticket has ever had a closed status. |
| Latest Miner ID | Number | Miner ID from the ticket's most recent event. |
| Latest Miner State | Text | Miner state from the ticket's most recent event. |
| Latest Status | Text | Status from the ticket's most recent event. |
| Max Closed Timestamp | Date / time | The latest time the ticket was set to closed. |
| Min Timestamp | Date / time | The earliest event time, which is when the ticket was created. |
Ticket Facts
One row per ticket, rolled up from its events: when it was created and closed, its current status, whether it is open or stale, and how long it took to resolve. This is the view to use for ticket counts and resolution time statistics.
Used by: Ticket Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| Closed Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When the ticket was closed, taken from its latest closed status event. |
| Created Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When the ticket was first created, taken from its earliest event. |
| Current Status | Text | The ticket's most recent status: pending, in-progress, ready-to-review, rma, or closed. |
| Days Since Created | Number | Days between the ticket's creation and now. |
| Event Count | Number | Number of history events on the ticket. |
| Is Closed (Yes / No) | Yes / No | Yes if the ticket has been closed. |
| Is Open (Yes / No) | Yes / No | Yes if the ticket is currently open, meaning it has never had a closed status. |
| Is Stale Open Ticket (Yes / No) | Yes / No | Yes if the ticket is open and more than 7 days old. |
| Miner ID | Number | Miner ID from the ticket's latest event. |
| Miner State | Text | Miner state from the ticket's latest event. |
| Resolution | Duration (Minutes, Hours, Days) | Time between ticket creation and closure, in days, hours, or minutes. |
| Resolution Time Tier | Tier | Resolution time in hours grouped into buckets: Below 1, 1 to 3, 4 to 7, 8 to 23, 24 to 71, 72 to 167, or 168 or Above. Undefined for tickets that are still open. |
| Ticket ID | Number | Foreman's numeric ID for the ticket. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Avg Days Since Created | Average | Average age of the tickets in the selection, in days. |
| Avg Resolution Time Days | Average | Average days to resolve the closed tickets in the selection. |
| Avg Resolution Time Hours | Average | Average hours to resolve the closed tickets in the selection. |
| Avg Resolution Time Hours Week Over Week | Period over period | Avg Resolution Time Hours for the same selection one week earlier. |
| Count Closed Tickets | Count (distinct) | Number of distinct closed tickets. |
| Count Open Tickets | Count (distinct) | Number of distinct tickets currently open. |
| Count Stale Open Tickets | Count (distinct) | Number of distinct open tickets older than 7 days. |
| Count Tickets | Count (distinct) | Number of distinct tickets. |
| Max Resolution Time Hours | Maximum | Slowest resolution time in the selection, in hours. |
| Median Resolution Time Hours | Median distinct | Median hours to resolve the closed tickets in the selection. |
| Min Resolution Time Hours | Minimum | Fastest resolution time in the selection, in hours. |
Ticket History: Custom Field
Custom field values attached to ticket events, one row per value. Only present when your Foreman account has ticket custom fields configured.
Used by: Ticket Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| Ticket History Custom Field | Text | A custom field value recorded on the ticket event. |
Open Tickets Over Time
A precomputed hourly count of how many tickets were open at each point in time. Use the Timestamp Filter to set the range.
Used by: Tickets Open Over Time
Dimensions
| Field | Type | What it means |
|---|---|---|
| Open Ticket Count | Number | Number of tickets that were open at this hour. |
| Timestamp Date | Date / time (Time, Hour, Date, Week, Month) | The hour at which the open ticket count was calculated, at hourly, daily, weekly, or monthly grain. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Avg Open Tickets | Average | Average open ticket count across the selected hours. |
| Latest Open Ticket Count | Maximum | The most recent open ticket count in the selection. |
| Max Open Tickets | Maximum | Peak open ticket count in the selection. |
| Min Open Tickets | Minimum | Lowest open ticket count in the selection. |
| Open Tickets | Maximum | Open tickets at the end of the selected period. Use this one for time-series charts. |
Filter-only fields
| Filter | Type | What it means |
|---|---|---|
| Timestamp Filter | Date / time | Filter-only field that sets the time range for the open ticket calculation without adding a column to the result. |
Shared views documented elsewhere
These views are joined into explores in this group but are documented in another article so the definitions live in one place.
- Client Power Cost (used by Ticket Data)
- Coin Hash Price (used by Ticket Data)
- Miner Data (used by Ticket Data)
- Miner Details (Current) (used by Ticket Data)
Comments
0 comments
Please sign in to leave a comment.