Hash rate, power, temperature, pool, and issue data for every miner Foreman monitors, at 5 minute, hourly, and daily grain.
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
Five explores cover miners. They share the same underlying miner data view, so the difference between them is which miners are included, how far back the data goes, and how it is aggregated. The overview article has a short guide to picking between them.
Miner Data (Online) miner_metrics
Looker description: Five minute aggregates of historical miner data (online miners only)
The main time-series explore for miner telemetry. Every row is one miner over one 5 minute window, built only from miners that were online and reporting during that window. It carries hash rate, power, temperature, fan, pool share, firmware, uptime, and earnings figures, and joins the client, power cost, and coin hash price context that was in effect at the same moment.
| Grain | One row per miner per 5 minutes |
| Time field | Timestamp (5m), plus Mining Date for grouping by hour, day, week, or month |
| Best for |
|
Example questions
- What was our total hash rate per hour yesterday, by site map group?
- Which miners had the highest average temperature over the last 24 hours?
- How much did power cost us last week compared with the week before?
Views in this explore: Client Data (Historical), Client Power Cost, Coin Hash Price, Firmware Error Codes, Miner Data, Miner Details (Current), Pickaxe's Client Data (Historical)
Miner Data (Online - Daily) miner_metrics_daily
Looker description: Daily aggregates of historical miner data (online miners only)
The same miner telemetry rolled up to one row per miner per day, again from online miners only. It is much smaller and faster than the 5 minute explore and is the right choice for anything measured in days, weeks, or months. Power cost is broken out three ways (client, group, and site level pricing) and the daily rows carry the same earnings and margin measures as the 5 minute view.
| Grain | One row per miner per day |
| Time field | Date, plus Mining Date for grouping by week, month, quarter, or year |
| Best for |
|
Example questions
- What was our net income per month this year?
- Which miner types had the best hashing uptime last quarter?
- How many reboots did each rack see per day in August?
Views in this explore: Miner Data (Historical - Daily)
Miner Details miner_info
Looker description: Current Foreman miner records joined with the current miner data (most recent data for each miner with a fifteen minute cutoff)
A snapshot explore, not a time series. Every miner record in Foreman appears once, joined to the most recent telemetry Foreman received for it, with a 15 minute cutoff that decides whether the miner counts as current. Use it for fleet inventory questions: how many miners exist, what state they are in, what they are expected to produce, and what they reported most recently.
| Grain | One row per miner |
| Time field | None for the record itself. Timestamp (5m) on the joined Miner Data view is the time of the latest reading |
| Best for |
|
Example questions
- How many miners of each type do we have, and how many are currently reporting?
- What is our expected total hash rate compared with what miners are reporting right now?
- Which miners were created in the last 30 days?
Views in this explore: Client Power Cost, Coin Hash Price, Miner Data, Miner Details (Current)
Miner Data (All) miner_metrics_all
Looker description: Five minute aggregates of historical miner data joined with 15 minute snapshots of all miner records in Foreman
Like Miner Data (Online), but built from 15 minute snapshots of every miner record in Foreman, including miners that were offline or not reporting. Windows with no telemetry still produce a row, so this is the explore that can count offline miners and calculate true availability. The miner details joined here are historical too, so a miner's name, type, or state is shown as it was at that time rather than as it is now.
| Grain | One row per miner per 5 minutes, with or without telemetry |
| Time field | Timestamp (5m) on Miner Data, Timestamp (15m) on Miner Details (Historical) |
| Best for |
|
Example questions
- How many miners were offline at each hour last week?
- What share of our expected hash rate was actually delivered per day?
- When did a given miner last report before going dark?
Views in this explore: Client Power Cost, Coin Hash Price, Firmware Error Codes, Miner Data, Miner Details (Historical)
Miner Issues miner_issue_history
Looker description: Fifteen minute snapshots of historical miner issues
Foreman evaluates a fixed set of health checks for every miner (low hash rate, high temperature, missing hash boards, fans, pool problems, not updating, and so on). This explore stores a 15 minute snapshot of those checks for each miner, with a Yes / No flag and a since timestamp for each issue, plus a companion view that measures how long each issue took to resolve. Miner telemetry and details are joined for context.
| Grain | One row per miner per 15 minutes |
| Time field | Timestamp (15m) |
| Best for |
|
Example questions
- How many miners had high temperature issues each day last month?
- What is our average time to resolve a zero hash rate issue?
- Which racks have the most miners not submitting shares right now?
Views in this explore: Client Power Cost, Coin Hash Price, Miner Data, Miner Details (Current), Miner Issues (Historical), Miner Issues Resolution Times (Historical)
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.
Miner Data
The core telemetry view. Each row summarizes what one miner reported over a 5 minute window: hash rate, power, temperatures, fans, pool shares, firmware, uptime, and the earnings and power cost attributed to that window. Fields are grouped the same way as in the Looker field picker.
Appears in Looker as Miner Data (Historical) or Miner Data (Current) depending on the explore. The fields are the same.
Used by: Miner Data (Online), Miner Details, Miner Data (All), Miner Issues, Ticket Data, Site Map Data, Strike Price Data, Dispatched Miners
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Is Current Data (Yes / No) | Yes / No | Yes if this row is the most recent reading Foreman has for the miner and it is less than 15 minutes old. Filter on Yes to get one live row per miner. |
| Is Most Recent Data (Yes / No) | Yes / No | Yes if this row is the latest reading Foreman has for the miner, however old it is. A miner that went offline days ago still has one row flagged Yes. |
| Miner ID | Number | Foreman's internal numeric ID for the miner. Stable for the life of the record and the safest field to join or filter on. |
| Mining Date | Date / time (Time, 5 minute, Hour, Date, Week, Month) | The window's time, offered at several timeframes (5 minute, hour, date, week, month) for grouping a chart. Same instant as Timestamp (5m). |
| Timestamp (5m) | 5 minute timestamp | Start of the 5 minute window this row summarizes. |
| Client | ||
| Client ID | Number | Numeric ID of the Foreman client (account) that owns the miner. |
| Client Name | Text | Name of the Foreman client that owns the miner. |
| Pickaxe Client ID | Number | Client ID of the account whose Pickaxe collected the data. It differs from Client ID only in hosting setups where one party runs the Pickaxe and another owns the miner. |
| Fans | ||
| Average Fan Speed | Number | Average speed across the miner's fans over the window, in RPM as reported by the miner. |
| Fan Count | Number | Number of fans the miner reported. |
| Fan Error | Number | Number of fans the miner flagged as faulty or reading zero during the window. |
| Maximum Fan Speed | Number | Highest fan speed reported in the window, in RPM. |
| Minimum Fan Speed | Number | Lowest fan speed reported in the window, in RPM. |
| Standard Fan Speed | Number | Standard deviation of fan speed within the window. A high value means fans were changing speed or disagreeing with each other. |
| Financials | ||
| Mining Earnings (BTC) | Number | Estimated revenue for this miner in this window, in BTC, calculated from its average hash rate and the hash price at the time. |
| Mining Earnings (USD) | Number | Estimated revenue for this miner in this window, in US dollars, using the coin price at the time. |
| Power Cost (USD) | Number | Estimated cost of the power this miner used in the window, from its average power and the client's power cost per MWh at the time. |
| Firmware | ||
| Firmware | Text | Firmware the miner is running as detected by Foreman: stock for the manufacturer's firmware, or the name of a third-party firmware such as luxos. |
| Firmware Error Codes (Raw) | Text | Every firmware error code the miner reported in the window, as one text value. The Firmware Error Codes view splits this into one row per code. |
| Firmware Version | Text | Version string of the firmware. |
| Has Firmware Errors (Yes / No) | Yes / No | Yes if the miner reported at least one firmware error code in the window. |
| Hash Rate | ||
| Average Hash Rate (MH) | Number | Average reported hash rate over the window, in megahashes per second (MH/s). |
| Average Hash Rate (PH) | Number | Average reported hash rate over the window, in petahashes per second (PH/s). |
| Average Hash Rate (TH) | Number | Average reported hash rate over the window, in terahashes per second (TH/s). |
| Average Hash Rate (kH) | Number | Average reported hash rate over the window, in kilohashes per second (kH/s). |
| Average Hash Rate Ideal | Number | The hash rate the miner's firmware reports as its ideal or nominal rate for its current settings, averaged over the window, in hashes per second. Compare with Average Hash Rate to see how far the miner is from its own target. |
| First Hash Rate | Number | Hash rate from the first sample in the window, in hashes per second. |
| Last Hash Rate | Number | Hash rate from the last sample in the window, in hashes per second. |
| Standard Hash Rate | Number | Standard deviation of hash rate across the samples in the window, in hashes per second. High values mean unstable hashing. |
| Miner | ||
| Miner Created Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When the miner record was first created in Foreman. |
| Miner Field Values | Text | Values of any custom fields you have defined for miners in Foreman, as text. |
| Miner IP | Text | IP address Foreman used to reach the miner. |
| Miner Last Updated Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When the miner record was last edited in Foreman. This is about the record, not about when the miner last reported. |
| Miner Mac | Text | MAC address of the miner's network interface. |
| Miner Manufacturer | Text | Manufacturer family as Foreman reports it: Antminer (Bitmain), Whatsminer (MicroBT), or AvalonMiner (Canaan). |
| Miner Name | Text | The miner's display name in Foreman. |
| Miner Serial | Text | Serial number reported by the miner. |
| Miner Tags | Text | Tags applied to the miner in Foreman, as a comma-separated list. |
| Miner Type | Text | Model of the miner as Foreman identifies it, for example Antminer S19 XP (141T). |
| Miner Stats | ||
| Hashing Uptime Pct | Number | Percentage of the window during which the miner was reporting and hashing above zero. |
| Reboot Count | Number | Number of times the miner rebooted during the window, detected from resets in its reported uptime. |
| Seconds Observed | Number | Seconds within the window for which Foreman received data from the miner. 300 means it was seen for the entire 5 minutes. |
| Uptime Pct | Number | Percentage of the window during which the miner was reachable and reporting, whether or not it was hashing. |
| Pickaxe | ||
| Average Query Time (ms) | Number | Average time in milliseconds the Pickaxe took to query the miner. Rising values point to network or miner responsiveness problems. |
| Pickaxe ID | Number | Numeric ID of the Pickaxe (Foreman's on-site agent) that collected the data. |
| Pickaxe Name | Text | Name of the Pickaxe that collected the data. |
| Standard Query Time (ms) | Number | Standard deviation of query time within the window, in milliseconds. |
| Pools | ||
| Active Coin Symbol | Text | Symbol of the coin the miner was mining on its active pool, such as BTC. |
| Active Pool | Text | URL of the pool the miner was actually submitting shares to during the window. |
| Active Worker | Text | Worker name the miner used on the active pool. |
| All Pools Accepted Shares | Number | Shares accepted across all configured pools during the window. |
| All Pools Difficulty Accepted Shares | Number | Accepted shares weighted by their difficulty, across all pools. Difficulty-weighted shares track work done more faithfully than raw counts when pools use variable difficulty. |
| All Pools Difficulty Rejected Shares | Number | Rejected shares weighted by their difficulty, across all pools. |
| All Pools Difficulty Stale Shares | Number | Stale shares weighted by their difficulty, across all pools. |
| All Pools Rejected Shares | Number | Shares the pools rejected as invalid or duplicate, across all pools. |
| All Pools Stale Shares | Number | Shares submitted too late to count, across all pools. |
| Pool 1 Accepted Shares | Number | Accepted shares on the pool in slot 1 of the miner's configuration. |
| Pool 1 Difficulty Accepted Shares | Number | Difficulty-weighted accepted shares on pool slot 1. |
| Pool 1 Difficulty Rejected Shares | Number | Difficulty-weighted rejected shares on pool slot 1. |
| Pool 1 Difficulty Stale Shares | Number | Difficulty-weighted stale shares on pool slot 1. |
| Pool 1 Rejected Shares | Number | Rejected shares on pool slot 1. |
| Pool 1 Stale Shares | Number | Stale shares on pool slot 1. |
| Pool 1 URL | Text | Pool URL configured in slot 1. |
| Pool 1 Worker | Text | Worker name configured in slot 1. |
| Pool 2 Accepted Shares | Number | Accepted shares on the pool in slot 2 of the miner's configuration. |
| Pool 2 Difficulty Accepted Shares | Number | Difficulty-weighted accepted shares on pool slot 2. |
| Pool 2 Difficulty Rejected Shares | Number | Difficulty-weighted rejected shares on pool slot 2. |
| Pool 2 Difficulty Stale Shares | Number | Difficulty-weighted stale shares on pool slot 2. |
| Pool 2 Rejected Shares | Number | Rejected shares on pool slot 2. |
| Pool 2 Stale Shares | Number | Stale shares on pool slot 2. |
| Pool 2 URL | Text | Pool URL configured in slot 2. |
| Pool 2 Worker | Text | Worker name configured in slot 2. |
| Pool 3 Accepted Shares | Number | Accepted shares on the pool in slot 3 of the miner's configuration. |
| Pool 3 Difficulty Accepted Shares | Number | Difficulty-weighted accepted shares on pool slot 3. |
| Pool 3 Difficulty Rejected Shares | Number | Difficulty-weighted rejected shares on pool slot 3. |
| Pool 3 Difficulty Stale Shares | Number | Difficulty-weighted stale shares on pool slot 3. |
| Pool 3 Rejected Shares | Number | Rejected shares on pool slot 3. |
| Pool 3 Stale Shares | Number | Stale shares on pool slot 3. |
| Pool 3 URL | Text | Pool URL configured in slot 3. |
| Pool 3 Worker | Text | Worker name configured in slot 3. |
| Submitting Shares | Number | Whether the miner was submitting shares during the window, as 1 (yes) or 0 (no). |
| Power | ||
| Average Power (MW) | Number | Average power draw over the window, in megawatts. |
| Average Power (W) | Number | Average power draw over the window, in watts. |
| Average Power (kW) | Number | Average power draw over the window, in kilowatts. |
| First Power | Number | Power draw from the first sample in the window, in watts. |
| First Power Mode | Text | Power mode the miner was in at the start of the window: normal, low, idle, or sleeping, on firmware that reports modes. Blank when the firmware does not. |
| Last Power | Number | Power draw from the last sample in the window, in watts. |
| Last Power Mode | Text | Power mode the miner was in at the end of the window: normal, low, idle, or sleeping. |
| Maximum Power | Number | Highest power reading in the window, in watts. |
| Minimum Power | Number | Lowest power reading in the window, in watts. |
| Reports PDU Power (Yes / No) | Yes / No | Yes if the power figure came from a PDU (power distribution unit) reading rather than from the miner itself. |
| Reports Power (Yes / No) | Yes / No | Yes if the miner or its PDU reported a measured power figure. When No, use Sticker Power for the rated draw. |
| Standard Power | Number | Standard deviation of power within the window, in watts. |
| Sticker Power | Number | The nameplate (sticker) power draw for this miner model, in watts. Used as the reference when the miner does not report power. |
| Site Map | ||
| Miner Index | Number | Position of the miner within its rack on the site map. |
| Miner Rack | Text | Name of the rack holding the miner on the site map. |
| Miner Rack Group | Number | Numeric group the rack belongs to on the site map. |
| Miner Row | Number | Row within the rack. |
| Sitemap Group ID | Number | ID of the site map group. A site map can be split into groups such as buildings or containers. |
| Sitemap Group Name | Text | Name of the site map group. |
| Temperatures | ||
| Average Temperature | Number | Average of the miner's temperature sensors over the window, in degrees Celsius. |
| Maximum Temperature | Number | Hottest sensor reading in the window, in degrees Celsius. |
| Minimum Temperature | Number | Coolest sensor reading in the window, in degrees Celsius. |
| Standard Temperature | Number | Standard deviation of temperature within the window. |
Measures
| Measure | Type | What it means |
|---|---|---|
| General | ||
| Count of Unique Miners | Count (distinct) | Number of distinct miners in the selected rows. |
| Cummulative Average Temperature | Average | Average of Average Temperature across the selected rows. |
| Total Hash Rate (MH) | Sum | Sum of Average Hash Rate across the selected rows, in megahashes per second (MH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Hash Rate (PH) | Sum | Sum of Average Hash Rate across the selected rows, in petahashes per second (PH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Hash Rate (TH) | Sum | Sum of Average Hash Rate across the selected rows, in terahashes per second (TH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Hash Rate (kH) | Sum | Sum of Average Hash Rate across the selected rows, in kilohashes per second (kH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Power (MW) | Sum | Sum of Average Power across the selected rows, in megawatts. Same caveat as Total Hash Rate: group by time for a time series. |
| Total Power (kW) | Sum | Sum of Average Power across the selected rows, in kilowatts. Same caveat as Total Hash Rate: group by time for a time series. |
| Financials | ||
| Average Margin | Number | Margin across the selected rows, calculated as net income divided by revenue in USD. |
| Revenue (BTC) | Sum | Sum of Mining Earnings (BTC) across the selected rows. |
| Revenue (USD) | Sum | Sum of Mining Earnings (USD) across the selected rows. |
| Total Net Income (USD) | Number | Revenue (USD) minus Total Power Cost (USD). |
| Total Power Cost (USD) | Sum | Sum of Power Cost (USD) across the selected rows. |
| Financials - Period over Period | ||
| Average Margin (Period over Period) | Period over period | Average Margin for the same selection one week earlier, for week-over-week comparison. |
| Net Income (Period over Period) | Period over period | Total Net Income (USD) for the same selection one week earlier. |
| Power Cost (Period over Period) | Period over period | Total Power Cost (USD) for the same selection one week earlier. |
| Rev BTC (Period over Period) | Period over period | Revenue (BTC) for the same selection one week earlier. |
| Rev USD (Period over Period) | Period over period | Revenue (USD) for the same selection one week earlier. |
Miner Details (Current)
The miner record as it stands in Foreman right now: identity, ownership, expected performance, lifecycle state, and the per-miner check suppressions. One row per miner. It is joined into most miner explores so you can group historical data by today's names, types, and states.
Used by: Miner Data (Online), Miner Details, Miner Issues, Ticket Data, Site Map Data, Dispatched Miners
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Miner ID | Number | Foreman's internal numeric ID for the miner. Stable for the life of the record and the safest field to join or filter on. |
| Client | ||
| Client ID | Number | Numeric ID of the Foreman client (account) that owns the miner. |
| Client Name | Text | Name of the Foreman client that owns the miner. |
| Pickaxe ID | Number | Numeric ID of the Pickaxe that monitors this miner. |
| Pickaxe's Client ID | Number | Client ID of the account whose Pickaxe collected the data. It differs from Client ID only in hosting setups where one party runs the Pickaxe and another owns the miner. |
| Foreman Config | ||
| Ignore Bad Shares | Number | 1 if Foreman is set to suppress the not-submitting-shares check for this miner, 0 otherwise. |
| Ignore Duplicate Mac | Number | 1 if the duplicate MAC address check is suppressed for this miner. |
| Ignore HW Errors | Number | 1 if the hardware errors check is suppressed for this miner. |
| Ignore Miner Type Changes | Number | 1 if Foreman should not raise an issue when this miner's detected model changes. |
| Ignore Missing Boards | Number | 1 if the missing hash boards check is suppressed for this miner. |
| Ignore Missing Fan | Number | 1 if the missing fan check is suppressed for this miner. |
| Ignore Reboots | Number | 1 if the reboot check is suppressed for this miner. |
| Miner Info | ||
| Created Date | Date / time (Time, Date, Week, Month) | When the miner record was created in Foreman. |
| Deleted Date | Date / time (Time, Date, Week, Month) | When the miner record was deleted in Foreman. Blank for miners that still exist. |
| Expected Hash Rate | Number | The hash rate Foreman expects from this miner, in hashes per second, from its model or a value you set on the record. |
| Expected Hash Rate (MH) | Number | Expected hash rate in megahashes per second (MH/s). |
| Expected Hash Rate (PH) | Number | Expected hash rate in petahashes per second (PH/s). |
| Expected Hash Rate (TH) | Number | Expected hash rate in terahashes per second (TH/s). |
| Expected Hash Rate (kH) | Number | Expected hash rate in kilohashes per second (kH/s). |
| Miner IP | Text | Current IP address of the miner. |
| Miner Mac | Text | MAC address of the miner. |
| Miner Name | Text | The miner's display name in Foreman. |
| Miner Serial | Text | Serial number reported by the miner. |
| PSU Serial | Text | Serial number of the power supply unit, when the miner reports it. |
| Previous Miner IP | Text | The IP address the miner was last seen at before its current one. Useful for tracking DHCP changes. |
| Username | Text | Username Foreman uses to log in to the miner, where one is configured. |
| Miner Status | ||
| Deleted (Yes / No) | Yes / No | Yes if the record has been deleted in Foreman. Deleted miners are kept so their history stays intact. |
| Disabled (Yes / No) | Yes / No | Yes if the miner has been disabled in Foreman, so it is not monitored or alerted on. |
| Has Reported In (Yes / No) | Yes / No | Yes if Foreman has ever received data from this miner. |
| State | Text | Lifecycle state of the miner: deployed, in-repair, in-storage, or retired. |
| Power | ||
| Average Power (MW) | Number | Expected power draw for this miner, in megawatts, from its model or a value set on the record. |
| Average Power (kW) | Number | Expected power draw for this miner, in kilowatts. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Count of Unique Miners | Count (distinct) | Number of distinct miners in the selected rows. |
| Expected Total Hash Rate (MH) | Sum | Sum of Expected Hash Rate across distinct miners, in megahashes per second (MH/s). |
| Expected Total Hash Rate (PH) | Sum | Sum of Expected Hash Rate across distinct miners, in petahashes per second (PH/s). |
| Expected Total Hash Rate (TH) | Sum | Sum of Expected Hash Rate across distinct miners, in terahashes per second (TH/s). |
| Expected Total Hash Rate (kH) | Sum | Sum of Expected Hash Rate across distinct miners, in kilohashes per second (kH/s). |
| Expected Total Power (MW) | Sum | Sum of expected power across distinct miners, in megawatts. |
| Expected Total Power (kW) | Sum | Sum of expected power across distinct miners, in kilowatts. |
Miner Details (Historical)
15 minute snapshots of the miner record, so a miner's name, type, state, and expected performance are shown as they were at that time rather than as they are now. Only the Miner Data (All) explore uses it.
Used by: Miner Data (All)
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Miner ID | Number | Foreman's internal numeric ID for the miner. Stable for the life of the record and the safest field to join or filter on. |
| Timestamp (15m) | 15 minute timestamp | Time of the snapshot. |
| Client | ||
| Client ID | Number | Numeric ID of the Foreman client (account) that owns the miner. |
| Client Name | Text | Name of the Foreman client that owns the miner. |
| Pickaxe Client ID | Number | Client ID of the account whose Pickaxe collected the data. It differs from Client ID only in hosting setups where one party runs the Pickaxe and another owns the miner. |
| Miner Info | ||
| Active Pool | Text | Pool the miner was configured to use at the time of the snapshot. |
| Expected Hash Rate | Number | The hash rate Foreman expects from this miner, in hashes per second, from its model or a value you set on the record. |
| Expected Hash Rate (MH) | Number | Expected hash rate in megahashes per second (MH/s). |
| Expected Hash Rate (PH) | Number | Expected hash rate in petahashes per second (PH/s). |
| Expected Hash Rate (TH) | Number | Expected hash rate in terahashes per second (TH/s). |
| Expected Hash Rate (kH) | Number | Expected hash rate in kilohashes per second (kH/s). |
| Miner Mac | Text | MAC address of the miner at the time. |
| Miner Name | Text | Display name at the time. |
| Miner Type | Text | Model at the time. |
| Miner Status | ||
| Deleted (Yes / No) | Yes / No | Yes if the record had been deleted at the time of the snapshot. |
| Deleted Date | Date / time (Time, Date, Week, Month) | When the record was deleted, if it had been. |
| Disabled (Yes / No) | Yes / No | Yes if the miner was disabled in Foreman at the time. |
| State | Text | Lifecycle state at the time: deployed, in-repair, in-storage, or retired. |
| Pickaxe | ||
| Pickaxe ID | Number | ID of the Pickaxe monitoring the miner at the time. |
| Pickaxe Name | Text | Name of that Pickaxe. |
| Power | ||
| Average Power (MW) | Number | Expected power draw at the time, in megawatts. |
| Average Power (kW) | Number | Expected power draw at the time, in kilowatts. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Count of Unique Miners | Count (distinct) | Number of distinct miners in the selected rows. |
| Expected Total Hash Rate (MH) | Sum | Sum of Expected Hash Rate across distinct miners, in megahashes per second (MH/s). |
| Expected Total Hash Rate (PH) | Sum | Sum of Expected Hash Rate across distinct miners, in petahashes per second (PH/s). |
| Expected Total Hash Rate (TH) | Sum | Sum of Expected Hash Rate across distinct miners, in terahashes per second (TH/s). |
| Expected Total Hash Rate (kH) | Sum | Sum of Expected Hash Rate across distinct miners, in kilohashes per second (kH/s). |
| Expected Total Power (MW) | Sum | Sum of expected power across distinct miners, in megawatts. |
| Expected Total Power (kW) | Sum | Sum of expected power across distinct miners, in kilowatts. |
Miner Data (Historical - Daily)
The daily roll-up of the miner telemetry view: one row per miner per day, from days on which the miner was online. It has the same identity, location, and financial fields as the 5 minute view, minus the per-window detail (fans, temperatures, share counts), and it breaks power cost out by client, group, and site pricing.
Used by: Miner Data (Online - Daily)
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Date | Date | The day this row summarizes. |
| Miner ID | Number | Foreman's internal numeric ID for the miner. Stable for the life of the record and the safest field to join or filter on. |
| Mining Date | Date / time (Date, Week, Month, Quarter, Year) | The day, offered at week, month, quarter, and year timeframes for grouping. |
| Client | ||
| Client ID | Number | Numeric ID of the Foreman client (account) that owns the miner. |
| Client Name | Text | Name of the Foreman client that owns the miner. |
| Pickaxe Client ID | Number | Client ID of the account whose Pickaxe collected the data. It differs from Client ID only in hosting setups where one party runs the Pickaxe and another owns the miner. |
| Financials | ||
| Mining Earnings (BTC) | Number | Estimated revenue for the day, in BTC. |
| Mining Earnings (USD) | Number | Estimated revenue for the day, in US dollars. |
| Power Cost (USD - Client) | Number | Estimated power cost for the day priced at the client's own power rate. Foreman can hold power prices at client, client group, and site level, and the three variants show the day's cost under each. |
| Power Cost (USD - Group) | Number | Estimated power cost for the day priced at the client group's power rate. |
| Power Cost (USD - Site) | Number | Estimated power cost for the day priced at the site's power rate. |
| Firmware | ||
| Firmware | Text | Firmware the miner is running as detected by Foreman: stock for the manufacturer's firmware, or the name of a third-party firmware such as luxos. |
| Firmware Version | Text | Version string of the firmware. |
| Hash Rate | ||
| Average Hash Rate (MH) | Number | Average reported hash rate over the day, in megahashes per second (MH/s). |
| Average Hash Rate (PH) | Number | Average reported hash rate over the day, in petahashes per second (PH/s). |
| Average Hash Rate (TH) | Number | Average reported hash rate over the day, in terahashes per second (TH/s). |
| Average Hash Rate (kH) | Number | Average reported hash rate over the day, in kilohashes per second (kH/s). |
| Average Hash Rate Ideal | Number | The miner's own ideal or nominal hash rate averaged over the day, in hashes per second. |
| Standard Hash Rate | Number | Standard deviation of hash rate across the day, in hashes per second. |
| Miner | ||
| Miner Created Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When the miner record was first created in Foreman. |
| Miner IP | Text | IP address Foreman used to reach the miner. |
| Miner Last Updated Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When the miner record was last edited in Foreman. This is about the record, not about when the miner last reported. |
| Miner Mac | Text | MAC address of the miner's network interface. |
| Miner Manufacturer | Text | Manufacturer family as Foreman reports it: Antminer (Bitmain), Whatsminer (MicroBT), or AvalonMiner (Canaan). |
| Miner Name | Text | The miner's display name in Foreman. |
| Miner Serial | Text | Serial number reported by the miner. |
| Miner Type | Text | Model of the miner as Foreman identifies it, for example Antminer S19 XP (141T). |
| Miner Stats | ||
| Hashing Uptime Pct | Number | Percentage of the day during which the miner was reporting and hashing above zero. |
| Reboot Count | Number | Number of reboots detected during the day. |
| Seconds Observed | Number | Seconds within the day for which Foreman received data from the miner. 86,400 means it was seen all day. |
| Uptime Pct | Number | Percentage of the day during which the miner was reachable and reporting. |
| Pickaxe | ||
| Average Query Time (ms) | Number | Average Pickaxe query time for the miner over the day, in milliseconds. |
| Pickaxe ID | Number | Numeric ID of the Pickaxe (Foreman's on-site agent) that collected the data. |
| Pickaxe Name | Text | Name of the Pickaxe that collected the data. |
| Standard Query Time (ms) | Number | Standard deviation of Pickaxe query time over the day. |
| Pools | ||
| Active Coin Symbol | Text | Symbol of the coin the miner was mining on its active pool, such as BTC. |
| Active Pool | Text | URL of the pool the miner was actually submitting shares to during the window. |
| Active Worker | Text | Worker name the miner used on the active pool. |
| Power | ||
| Average Power (MW) | Number | Average power draw over the day, in megawatts. |
| Average Power (W) | Number | Average power draw over the day, in watts. |
| Average Power (kW) | Number | Average power draw over the day, in kilowatts. |
| Maximum Power | Number | Highest power reading during the day, in watts. |
| Minimum Power | Number | Lowest power reading during the day, in watts. |
| Reports PDU Power (Yes / No) | Yes / No | Yes if the power figure came from a PDU (power distribution unit) reading rather than from the miner itself. |
| Reports Power (Yes / No) | Yes / No | Yes if the miner or its PDU reported a measured power figure. When No, use Sticker Power for the rated draw. |
| Standard Power | Number | Standard deviation of power across the day, in watts. |
| Sticker Power | Number | The nameplate (sticker) power draw for this miner model, in watts. Used as the reference when the miner does not report power. |
| Site Map | ||
| Miner Index | Number | Position of the miner within its rack on the site map. |
| Miner Rack | Text | Name of the rack holding the miner on the site map. |
| Miner Rack Group | Number | Numeric group the rack belongs to on the site map. |
| Miner Row | Number | Row within the rack. |
| Sitemap Group ID | Number | ID of the site map group. A site map can be split into groups such as buildings or containers. |
| Sitemap Group Name | Text | Name of the site map group. |
Measures
| Measure | Type | What it means |
|---|---|---|
| General | ||
| Count of Unique Miners | Count (distinct) | Number of distinct miners in the selected rows. |
| Total Hash Rate (MH) | Sum | Sum of Average Hash Rate across the selected rows, in megahashes per second (MH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Hash Rate (PH) | Sum | Sum of Average Hash Rate across the selected rows, in petahashes per second (PH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Hash Rate (TH) | Sum | Sum of Average Hash Rate across the selected rows, in terahashes per second (TH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Hash Rate (kH) | Sum | Sum of Average Hash Rate across the selected rows, in kilohashes per second (kH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Power (MW) | Sum | Sum of Average Power across the selected rows, in megawatts. Same caveat as Total Hash Rate: group by time for a time series. |
| Total Power (kW) | Sum | Sum of Average Power across the selected rows, in kilowatts. Same caveat as Total Hash Rate: group by time for a time series. |
| Financials | ||
| Average Margin | Number | Margin across the selected rows, calculated as net income divided by revenue in USD. |
| Revenue (BTC) | Sum | Sum of Mining Earnings (BTC) across the selected rows. |
| Revenue (USD) | Sum | Sum of Mining Earnings (USD) across the selected rows. |
| Total Net Income (USD) | Number | Revenue (USD) minus Total Power Cost (USD). |
| Total Power Cost (USD) | Sum | Sum of Power Cost (USD) across the selected rows. |
| Financials - Period over Period | ||
| Average Margin (Period over Period) | Period over period | Average Margin for the same selection one week earlier, for week-over-week comparison. |
| Net Income (Period over Period) | Period over period | Total Net Income (USD) for the same selection one week earlier. |
| Power Cost (Period over Period) | Period over period | Total Power Cost (USD) for the same selection one week earlier. |
| Rev BTC (Period over Period) | Period over period | Revenue (BTC) for the same selection one week earlier. |
| Rev USD (Period over Period) | Period over period | Revenue (USD) for the same selection one week earlier. |
Miner Metrics Hourly (Historical)
An hourly roll-up of miner hash rate and power, joined into the site map explore so each rack position can show what its miner produced during the hour.
Used by: Site Map Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Timestamp (1h) | Hour | Start of the hour this row summarizes. |
| Client | ||
| Client ID | Number | Numeric ID of the Foreman client (account) that owns the miner. |
| Client Name | Text | Name of the Foreman client that owns the miner. |
| Pickaxe Client ID | Number | Client ID of the account whose Pickaxe collected the data. It differs from Client ID only in hosting setups where one party runs the Pickaxe and another owns the miner. |
| Hash Rate | ||
| Average Hash Rate (MH) | Number | Average reported hash rate over the hour, in megahashes per second (MH/s). |
| Average Hash Rate (PH) | Number | Average reported hash rate over the hour, in petahashes per second (PH/s). |
| Average Hash Rate (TH) | Number | Average reported hash rate over the hour, in terahashes per second (TH/s). |
| Average Hash Rate (kH) | Number | Average reported hash rate over the hour, in kilohashes per second (kH/s). |
| Miner | ||
| Miner ID | Number | Foreman's internal numeric ID for the miner. Stable for the life of the record and the safest field to join or filter on. |
| Power | ||
| Average Power (MW) | Number | Average power draw over the hour, in megawatts. |
| Average Power (W) | Number | Average power draw over the hour, in watts. |
| Average Power (kW) | Number | Average power draw over the hour, in kilowatts. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Count of Unique Miners | Count (distinct) | Number of distinct miners in the selected rows. |
| Total Hash Rate (MH) | Sum | Sum of Average Hash Rate across the selected rows, in megahashes per second (MH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Hash Rate (PH) | Sum | Sum of Average Hash Rate across the selected rows, in petahashes per second (PH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Hash Rate (TH) | Sum | Sum of Average Hash Rate across the selected rows, in terahashes per second (TH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Hash Rate (kH) | Sum | Sum of Average Hash Rate across the selected rows, in kilohashes per second (kH/s). For one window this is the fleet hash rate. Over a longer period group by time so each point is one window. |
| Total Power (MW) | Sum | Sum of Average Power across the selected rows, in megawatts. Same caveat as Total Hash Rate: group by time for a time series. |
| Total Power (kW) | Sum | Sum of Average Power across the selected rows, in kilowatts. Same caveat as Total Hash Rate: group by time for a time series. |
Miner Issues (Historical)
Foreman runs a fixed set of health checks on every miner. This view stores a 15 minute snapshot of those checks per miner: a Yes / No flag for each issue, when it started, and for some checks a Warn or Error severity. Fields are grouped by the kind of problem, matching the Looker field picker.
Used by: Miner Issues
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Is Current Data (Yes / No) | Yes / No | Yes if this is the most recent issue snapshot for the miner and it is less than 15 minutes old. Filter on Yes for a live issue list. |
| Miner ID | Number | Foreman's internal numeric ID for the miner. Stable for the life of the record and the safest field to join or filter on. |
| Primary Key | Text | Internal unique key for the row (miner plus timestamp). Not useful for analysis. |
| Timestamp (15m) | 15 minute timestamp | Time of the snapshot. |
| Hardware Issues | ||
| Fans High (Yes / No) | Yes / No | Yes if fan speed was above the threshold Foreman uses for this miner type. |
| Fans High Since | Date / time | When the fans high condition started. |
| Fans High Status | Text | Severity of the fans high issue: Warn or Error. Blank when there is no issue. |
| Fans Low (Yes / No) | Yes / No | Yes if fan speed was below the threshold for this miner type. |
| Fans Low Since | Date / time | When the fans low condition started. |
| Fans Low Status | Text | Severity of the fans low issue: Warn or Error. Blank when there is no issue. |
| Hardware Errors (Yes / No) | Yes / No | Yes if the miner reported hardware errors (for example chip failures) above Foreman's threshold. |
| Hardware Errors Since | Date / time | When the hardware errors condition started. |
| Missing Fan (Yes / No) | Yes / No | Yes if the miner reported fewer fans than its model should have. |
| Missing Fan Since | Date / time | When the missing fan condition started. |
| Missing Hash Boards (Yes / No) | Yes / No | Yes if the miner reported fewer hash boards than its model should have. |
| Missing Hash Boards Since | Date / time | When the missing hash boards condition started. |
| Hash Rate Issues | ||
| Abnormal Hash Rate (Yes / No) | Yes / No | Yes if hash rate was unusually far from the miner's expected rate. |
| Abnormal Hash Rate Since | Date / time | When the abnormal hash rate condition started. |
| High Temperature Status | Text | Severity of the high temperature issue: Warn or Error. Blank when there is no issue. |
| Low Hash Rate (Yes / No) | Yes / No | Yes if hash rate was below the miner's expected rate by more than the allowed tolerance. |
| Low Hash Rate Since | Date / time | When the low hash rate condition started. |
| Low Hash Rate Status | Text | Severity of the low hash rate issue: Warn or Error. Blank when there is no issue. |
| Zero Hash Rate (Yes / No) | Yes / No | Yes if the miner was reachable but hashing at zero. |
| Zero Hash Rate Since | Date / time | When the zero hash rate condition started. |
| Offline Issues | ||
| Duplicate Mac (Yes / No) | Yes / No | Yes if another miner record shares this miner's MAC address, which usually means a duplicate or misconfigured record. |
| Duplicate Mac Since | Date / time | When the duplicate mac condition started. |
| Not Updating (Yes / No) | Yes / No | Yes if Foreman has stopped receiving data from the miner. |
| Not Updating Forever (Yes / No) | Yes / No | Yes if the miner has been silent so long that Foreman treats it as permanently offline, or has never reported. |
| Not Updating One Day (Yes / No) | Yes / No | Yes if the miner has not updated for at least one day. |
| Not Updating Recent (Yes / No) | Yes / No | Yes if the miner stopped updating recently, within the last day. |
| Not Updating Since | Date / time | When the not updating condition started. |
| Not Updating Two Days (Yes / No) | Yes / No | Yes if the miner has not updated for at least two days. |
| Pickaxe Offline (Yes / No) | Yes / No | Yes if the Pickaxe responsible for this miner was itself offline, so the miner's status is unknown rather than bad. |
| Pickaxe Offline Since | Date / time | When the pickaxe offline condition started. |
| Rebooted Recently (<10m) (Yes / No) | Yes / No | Yes if the miner rebooted within the last 10 minutes. |
| Rebooted Recently (<10m) Time | Date / time | When the recent reboot was detected. |
| Pool Issues | ||
| Invalid Pool Config (Yes / No) | Yes / No | Yes if the miner's pool configuration does not match what Foreman expects, for example a wrong URL or worker. |
| Invalid Pool Config Since | Date / time | When the invalid pool config condition started. |
| No Pools Configured (Yes / No) | Yes / No | Yes if the miner has no pools configured. |
| No Pools Configured Since | Date / time | When the no pools configured condition started. |
| Not Submitting Shares (Yes / No) | Yes / No | Yes if the miner was hashing but the pool was not accepting shares from it. |
| Not Submitting Shares Since | Date / time | When the not submitting shares condition started. |
| Temperature Issues | ||
| High Temperature (Yes / No) | Yes / No | Yes if a temperature sensor exceeded Foreman's threshold. |
| High Temperature Since | Date / time | When the high temperature condition started. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Total Abnormal Hash Rate | Sum | Number of snapshots in the selection where Abnormal Hash Rate is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Duplicate MAC | Sum | Number of snapshots in the selection where Duplicate Mac is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Fans High | Sum | Number of snapshots in the selection where Fans High is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Fans Low | Sum | Number of snapshots in the selection where Fans Low is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Hardware Errrors | Sum | Number of snapshots in the selection where Hardware Errors is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total High Temperatures | Sum | Number of snapshots in the selection where High Temperature is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Invalid Pool Config | Sum | Number of snapshots in the selection where Invalid Pool Config is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Low Hash Rate | Sum | Number of snapshots in the selection where Low Hash Rate is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Missing Fan | Sum | Number of snapshots in the selection where Missing Fan is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Missing Hash Boards | Sum | Number of snapshots in the selection where Missing Hash Boards is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total No Pools Configured | Sum | Number of snapshots in the selection where No Pools Configured is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Not Submitting Shares | Sum | Number of snapshots in the selection where Not Submitting Shares is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Not Updating | Sum | Number of snapshots in the selection where Not Updating is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Not Updating (1d) | Sum | Number of snapshots in the selection where Not Updating One Day is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Not Updating (2d) | Sum | Number of snapshots in the selection where Not Updating Two Days is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Not Updating Forever | Sum | Number of snapshots in the selection where Not Updating Forever is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Not Updating Recent | Sum | Number of snapshots in the selection where Not Updating Recent is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Pickaxe Offline | Sum | Number of snapshots in the selection where Pickaxe Offline is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Rebooted Recently | Sum | Number of snapshots in the selection where Rebooted Recently is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
| Total Zero Hash Rate | Sum | Number of snapshots in the selection where Zero Hash Rate is Yes. Within one 15 minute window that is the number of miners with the issue; over a longer period it counts miner-intervals, so group by time for a trend. |
Miner Issues Resolution Times (Historical)
For each issue snapshot, whether the issue has since been resolved and how long it took. Average the time-to-resolution fields to get mean time to resolution by issue type, site, or miner type.
Used by: Miner Issues
Dimensions
| Field | Type | What it means |
|---|---|---|
| Abnormal Hash Rate Resolved (Yes / No) | Yes / No | Yes if the abnormal hash rate issue that was open on this miner has since cleared. |
| Abnormal Hash Rate Time to Resolution | Duration (Minutes, Hours) | How long the abnormal hash rate issue lasted, from when it started until it cleared, in hours or minutes. |
| Duplicate Mac Resolved (Yes / No) | Yes / No | Yes if the duplicate mac issue that was open on this miner has since cleared. |
| Duplicate Mac Time to Resolution | Duration (Minutes, Hours) | How long the duplicate mac issue lasted, from when it started until it cleared, in hours or minutes. |
| Fans High Resolved (Yes / No) | Yes / No | Yes if the fans high issue that was open on this miner has since cleared. |
| Fans High Time to Resolution | Duration (Minutes, Hours) | How long the fans high issue lasted, from when it started until it cleared, in hours or minutes. |
| Fans Low Resolved (Yes / No) | Yes / No | Yes if the fans low issue that was open on this miner has since cleared. |
| Fans Low Time to Resolution | Duration (Minutes, Hours) | How long the fans low issue lasted, from when it started until it cleared, in hours or minutes. |
| Hash Rate Resolved (Yes / No) | Yes / No | Yes if the low hash rate issue that was open on this miner has since cleared. |
| Hash Rate Time to Resolution | Duration (Minutes, Hours) | How long the low hash rate issue lasted, from when it started until it cleared, in hours or minutes. |
| Hw Errors Resolved (Yes / No) | Yes / No | Yes if the hardware errors issue that was open on this miner has since cleared. |
| Hw Errors Time to Resolution | Duration (Minutes, Hours) | How long the hardware errors issue lasted, from when it started until it cleared, in hours or minutes. |
| Invalid Pool Config Resolved (Yes / No) | Yes / No | Yes if the invalid pool config issue that was open on this miner has since cleared. |
| Invalid Pool Config Time to Resolution | Duration (Minutes, Hours) | How long the invalid pool config issue lasted, from when it started until it cleared, in hours or minutes. |
| Miner ID | Number | Foreman's internal numeric ID for the miner. Stable for the life of the record and the safest field to join or filter on. |
| Missing Fan Resolved (Yes / No) | Yes / No | Yes if the missing fan issue that was open on this miner has since cleared. |
| Missing Fan Time to Resolution | Duration (Minutes, Hours) | How long the missing fan issue lasted, from when it started until it cleared, in hours or minutes. |
| Missing Hash Boards Resolved (Yes / No) | Yes / No | Yes if the missing hash boards issue that was open on this miner has since cleared. |
| Missing Hash Boards Time to Resolution | Duration (Minutes, Hours) | How long the missing hash boards issue lasted, from when it started until it cleared, in hours or minutes. |
| No Pools Configured Resolved (Yes / No) | Yes / No | Yes if the no pools configured issue that was open on this miner has since cleared. |
| No Pools Configured Time to Resolution | Duration (Minutes, Hours) | How long the no pools configured issue lasted, from when it started until it cleared, in hours or minutes. |
| Not Submitting Shares Resolved (Yes / No) | Yes / No | Yes if the not submitting shares issue that was open on this miner has since cleared. |
| Not Submitting Shares Time to Resolution | Duration (Minutes, Hours) | How long the not submitting shares issue lasted, from when it started until it cleared, in hours or minutes. |
| Not Updating Resolved (Yes / No) | Yes / No | Yes if the not updating issue that was open on this miner has since cleared. |
| Not Updating Time to Resolution | Duration (Minutes, Hours) | How long the not updating issue lasted, from when it started until it cleared, in hours or minutes. |
| Pickaxe Offline Resolved (Yes / No) | Yes / No | Yes if the pickaxe offline issue that was open on this miner has since cleared. |
| Pickaxe Offline Time to Resolution | Duration (Minutes, Hours) | How long the pickaxe offline issue lasted, from when it started until it cleared, in hours or minutes. |
| Rebooted Resolved (Yes / No) | Yes / No | Yes if the rebooted recently issue that was open on this miner has since cleared. |
| Rebooted Time to Resolution | Duration (Minutes, Hours) | How long the rebooted recently issue lasted, from when it started until it cleared, in hours or minutes. |
| Temps Resolved (Yes / No) | Yes / No | Yes if the high temperature issue that was open on this miner has since cleared. |
| Temps Time to Resolution | Duration (Minutes, Hours) | How long the high temperature issue lasted, from when it started until it cleared, in hours or minutes. |
| Timestamp Date | Date / time (15 minute, Hour, Date) | Time of the snapshot, at 15 minute, hourly, or daily grain. |
| Zero Hash Rate Resolved (Yes / No) | Yes / No | Yes if the zero hash rate issue that was open on this miner has since cleared. |
| Zero Hash Rate Time to Resolution | Duration (Minutes, Hours) | How long the zero hash rate issue lasted, from when it started until it cleared, in hours or minutes. |
Firmware Error Codes
The firmware error codes a miner reported in a 5 minute window, split into one row per code. Codes are grouped into categories and carry a human-readable description, so you can count errors by category or find every miner reporting a specific code.
Used by: Miner Data (Online), Miner Data (All), Dispatched Miners
Dimensions
| Field | Type | What it means |
|---|---|---|
| Chip Reset Board # | Number | Hash board number the error refers to, when the code is a chip reset or a board-level error. |
| Chip Reset Chip # | Number | Chip number the error refers to, when the code is a chip-level error. |
| Firmware Error Category | Text | Category of the error: Chip, Fan, Hash Rate, Hashboard, Pool, Power Supply, Temperature, Tuning & Status, or Other. |
| Firmware Error Code | Text | The raw code from the firmware, for example BOARD_NOT_DETECTED or a numeric code such as 206. |
| Firmware Error Description | Text | Human-readable explanation of the code. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Distinct Chips Reset | Count (distinct) | Number of distinct board and chip combinations that reported a reset. |
| Error Code Count | Count | Number of error code rows in the selection. |
| Miners Affected | Count (distinct) | Number of distinct miners that reported at least one code in the selection. |
Client Power Cost
The power price in effect for the client at each 5 minute mark, in dollars per megawatt-hour. Foreman uses it to turn power draw into power cost, and it is joined into most miner explores so cost is always available next to telemetry.
Used by: Miner Data (Online), Miner Details, Miner Data (All), Miner Issues, Ticket Data, Site Map Data, Strike Price Data, Dispatched Miners
Dimensions
| Field | Type | What it means |
|---|---|---|
| Client ID | Number | Numeric ID of the Foreman client (account) that owns the miner. |
| Full Power Cost ($/MWh) | Number | Total power price the client pays per MWh at this time: the base Power Cost plus the Power Cost Adder. |
| Power Cost ($/MWh) | Number | Base power price per MWh, from the client's fixed rate or from the market (LMP) price, depending on the client's pricing setup. |
| Power Cost Adder ($/MWh) | Number | Fixed amount added per MWh on top of the base price, for transmission, fees, or a hosting margin. |
| Timestamp (5m) | 5 minute timestamp | The 5 minute mark the price applies to. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Average of Full Power Cost ($/MWh) | Average | Average Full Power Cost across the selected rows. |
| Average of Power Cost ($/MWh) | Average | Average base Power Cost across the selected rows. |
| Average of Power Cost Adder ($/MWh) | Average | Average Power Cost Adder across the selected rows. |
Client Data (Historical)
The client's (Foreman account's) settings as they were at each point in time: identity, group membership, curtailment configuration, and power pricing setup. Joined so you can see which rules were in force when the miner data was recorded.
Used by: Miner Data (Online), Strike Price Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Client ID | Number | Numeric ID of the client (Foreman account). |
| Timestamp (15m) | 15 minute timestamp | Time of the 15 minute snapshot of the client's settings. |
| Timestamp (5m) | 5 minute timestamp | Time of the 5 minute snapshot, used where this view is joined to 5 minute data. |
| Client Group Info | ||
| Client Group ID | Number | ID of the client group the client belongs to. Client groups let one organization manage several clients (sites) together. |
| Client Group Name | Text | Name of the client group. |
| Client Group Owner Client ID | Number | Client ID of the account that owns the client group. |
| Client Info | ||
| Active (Yes / No) | Yes / No | Yes if the client account was active at the time. |
| Created Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When the client account was created. |
| Deleted (Yes / No) | Yes / No | Yes if the client account had been deleted at the time. |
| Name | Text | Name of the client. |
| Type | Text | Kind of account: colo for a hosting provider with customers, or private for an operator mining its own machines. |
| Curtailment Config | ||
| Auto Strike Price | Number | Strike price Foreman calculates automatically from hash price and power cost when automatic strike pricing is enabled, in $/MWh. |
| Auto Strike Price Tolerance | Number | Margin applied to the automatic strike price before Foreman acts on it. |
| Curtailment Down Interval | Number | Seconds between steps when ramping load down during a curtailment. |
| Curtailment Retry | Number | Number of times Foreman retries a curtailment command that a miner did not act on. |
| Curtailment Retry Duration | Number | Seconds to wait between retries. |
| Curtailment Retry Duration After | Number | Seconds after the initial command before retries begin. |
| Curtailment Up Interval | Number | Seconds between steps when ramping load back up after a curtailment. |
| Strike Curtail After | Number | How long the power price must stay above the strike price before Foreman curtails. |
| Strike Curtail After High | Number | How long the price must stay above the high strike price before the deeper curtailment tier applies. |
| Strike Price | Number | Power price in $/MWh above which Foreman curtails miners. |
| Strike Price High | Number | A second, higher strike price for a deeper curtailment tier. |
| Strike Resume After | Number | How long the price must stay below the strike price before miners are restored. |
| Strike Resume After High | Number | How long the price must stay below the high strike price before the deeper tier is lifted. |
| Target Dispatch Delay | Number | Delay between receiving a dispatch and acting on it. |
| Target Dispatch Delay Units | Text | Unit for Target Dispatch Delay (seconds). |
| Power Pricing | ||
| Power Cost Iso | Text | ISO whose prices are used when the client's power cost follows the market. |
| Power Cost Iso Market | Text | Market used for market-based pricing: day-ahead or real-time. |
| Power Cost Iso Zone | Text | Pricing zone within the ISO. |
| Power Cost Iso Zone ID | Number | Numeric ID of the pricing zone. |
| Power Cost Kwh | Number | Fixed power price per kWh when Power Cost Type is fixed. |
| Power Cost Kwh Currency ID | Number | Numeric ID of the currency the fixed price is in. |
| Power Cost Mwh Adder | Number | Amount added per MWh on top of the base price, for transmission, fees, or hosting margin. |
| Power Cost Type | Text | How the client's power is priced: fixed for a flat rate, or market-based pricing from an ISO. |
Pickaxe's Client Data (Historical)
The same client settings view, but for the client that runs the Pickaxe rather than the client that owns the miner. In a hosting setup this is the host's configuration.
Used by: Miner Data (Online)
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Client ID | Number | Numeric ID of the client (Foreman account). |
| Timestamp (15m) | 15 minute timestamp | Time of the 15 minute snapshot of the client's settings. |
| Client Group Info | ||
| Client Group ID | Number | ID of the client group the client belongs to. Client groups let one organization manage several clients (sites) together. |
| Client Group Name | Text | Name of the client group. |
| Client Group Owner Client ID | Number | Client ID of the account that owns the client group. |
| Client Info | ||
| Active (Yes / No) | Yes / No | Yes if the client account was active at the time. |
| Created Date | Date / time (Time, Date, Week, Month, Quarter, Year) | When the client account was created. |
| Deleted (Yes / No) | Yes / No | Yes if the client account had been deleted at the time. |
| Name | Text | Name of the client. |
| Type | Text | Kind of account: colo for a hosting provider with customers, or private for an operator mining its own machines. |
| Curtailment Config | ||
| Auto Strike Price | Number | Strike price Foreman calculates automatically from hash price and power cost when automatic strike pricing is enabled, in $/MWh. |
| Auto Strike Price Tolerance | Number | Margin applied to the automatic strike price before Foreman acts on it. |
| Curtailment Down Interval | Number | Seconds between steps when ramping load down during a curtailment. |
| Curtailment Retry | Number | Number of times Foreman retries a curtailment command that a miner did not act on. |
| Curtailment Retry Duration | Number | Seconds to wait between retries. |
| Curtailment Retry Duration After | Number | Seconds after the initial command before retries begin. |
| Curtailment Up Interval | Number | Seconds between steps when ramping load back up after a curtailment. |
| Strike Curtail After | Number | How long the power price must stay above the strike price before Foreman curtails. |
| Strike Curtail After High | Number | How long the price must stay above the high strike price before the deeper curtailment tier applies. |
| Strike Price | Number | Power price in $/MWh above which Foreman curtails miners. |
| Strike Price High | Number | A second, higher strike price for a deeper curtailment tier. |
| Strike Resume After | Number | How long the price must stay below the strike price before miners are restored. |
| Strike Resume After High | Number | How long the price must stay below the high strike price before the deeper tier is lifted. |
| Target Dispatch Delay | Number | Delay between receiving a dispatch and acting on it. |
| Target Dispatch Delay Units | Text | Unit for Target Dispatch Delay (seconds). |
| Power Pricing | ||
| Power Cost Iso | Text | ISO whose prices are used when the client's power cost follows the market. |
| Power Cost Iso Market | Text | Market used for market-based pricing: day-ahead or real-time. |
| Power Cost Iso Zone | Text | Pricing zone within the ISO. |
| Power Cost Iso Zone ID | Number | Numeric ID of the pricing zone. |
| Power Cost Kwh | Number | Fixed power price per kWh when Power Cost Type is fixed. |
| Power Cost Kwh Currency ID | Number | Numeric ID of the currency the fixed price is in. |
| Power Cost Mwh Adder | Number | Amount added per MWh on top of the base price, for transmission, fees, or hosting margin. |
| Power Cost Type | Text | How the client's power is priced: fixed for a flat rate, or market-based pricing from an ISO. |
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.
- Coin Hash Price (used by Miner Data (Online), Miner Details, Miner Data (All), Miner Issues)
Comments
0 comments
Please sign in to leave a comment.