Every explore in Foreman Intelligence, what it contains, and what each field means.
Model: customer_access. Generated from the live Looker model on 2026-09-04. Fields hidden in Looker are not listed.
Pick a group, then an explore, and this page shows only that explore and the views it is built from. Overview brings back the summary table. Everything shows all 18 explores at once, which is handy for searching the page.
Hash rate, power, temperature, pool, and issue data for every miner Foreman monitors, at 5 minute, hourly, and daily grain.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.Hourly snapshots of your site map racks and positions, joined to the miners sitting in each slot.Dispatch events, strike prices, and the miners affected when Foreman curtails or restores power.Locational marginal prices for power markets around the world, down to 5 minute granularity.Coin prices, hash prices, and network statistics such as difficulty and network hash rate, at 5 minute grain.Per-worker hash rate reported by the mining pools themselves, so you can compare what the pool saw with what the miner reported.Hourly historical weather and 10 day hourly forecasts for any coordinates or US zip code, for correlating site conditions with miner behavior.
Contents
- How to read the dictionary
- All explores at a glance
- Which miner explore should I use?
- Views that appear in many explores
How to read the dictionary
An explore is a starting point for a query in Looker. It defines which tables are joined together and which fields you can pick from. Every dashboard tile and Look in Foreman Intelligence is built on one explore, and when you ask Claude for a chart it picks an explore first too.
An explore is made of one or more views. A view is a set of related fields, usually one table. When you open an explore in Looker the field picker on the left is grouped by view name, and the field tables in this dictionary use the same names, so what you read here matches what you see in Looker.
- Dimensions are attributes you group and filter by: a miner's name, a rack, a timestamp, a Yes / No flag, or a raw reading such as average power for one row.
- Measures aggregate across all the rows you select: a sum, an average, or a count of unique miners. Add a measure and Looker rolls the data up to whatever dimensions you chose.
- Yes / No fields are true or false flags. They are handy as filters: "Is Current Data is Yes" keeps only each miner's latest reading.
- Date fields that show several timeframes (Date, Hour, Week, Month) are one field in Looker with a timeframe picker. Choose the timeframe that matches the grain of your chart.
- Unit variants such as Average Hash Rate (TH) and Average Hash Rate (PH), or Power (W), (kW), and (MW), are the same value at different scales. Pick the one that reads well for your fleet size.
- Current versus Historical in a view name tells you whether the view holds one row per miner as things stand right now, or a time series of how things were.
A few Foreman terms appear throughout. A client is a Foreman account, which for most customers means a site or company. A Pickaxe is the Foreman agent installed on site that talks to the miners and reports back. A dispatch is a curtailment or restore instruction, and a strike price is the power price at which Foreman starts curtailing.
All explores at a glance
Click an explore name to open it.
| Group | Explore | Grain | What it holds |
|---|---|---|---|
| Miners |
Miner Data (All)miner_metrics_all
|
One row per miner per 5 minutes, with or without telemetry | 5 minute telemetry for all miners, including offline ones, with historical miner details. |
| Miners |
Miner Data (Online - Daily)miner_metrics_daily
|
One row per miner per day | Daily roll-up of miner telemetry and earnings, online miners only. |
| Miners |
Miner Data (Online)miner_metrics
|
One row per miner per 5 minutes | 5 minute telemetry for every online miner, with earnings and power cost. |
| Miners |
Miner Detailsminer_info
|
One row per miner | Current record and latest reading for every miner in Foreman. |
| Miners |
Miner Issuesminer_issue_history
|
One row per miner per 15 minutes | 15 minute snapshots of every miner health issue, with time to resolution. |
| Tickets |
Ticket Dataticket_history
|
One row per ticket event (Ticket History) or one row per ticket (Ticket Facts) | Ticket events and per-ticket facts such as status, owner, and resolution time. |
| Tickets |
Tickets Open Over Timeopen_tickets_over_time
|
One row per hour | Hourly count of open tickets, for backlog trend lines. |
| Site Map |
Site Map Datasite_map_history
|
One row per rack position per hour | Hourly snapshots of racks and miner positions, joined to miner telemetry. |
| Curtailment |
Dispatch Datadispatch_history
|
One row per dispatch | Every curtailment dispatch with its timing, target draw, and reason. |
| Curtailment |
Dispatched Minersdispatch_miners
|
One row per miner per 5 minutes during a dispatch | Curtailment dispatches joined to per-miner telemetry during the event. |
| Curtailment |
Strike Price Datastrike_price_history
|
One row per client, miner type, and power mode per 5 minutes | 5 minute history of strike prices alongside LMPs and client curtailment settings. |
| LMPs |
LMPslmps
|
One row per ISO, market, and zone per 5 or 15 minutes | 5 minute locational marginal power prices by ISO, market, and zone. |
| Coins |
Coin Hash Pricecoin_hash_price
|
One row per coin per 5 minutes | 5 minute hash price per coin in USD, BTC, and coin units at several hash rate scales. |
| Coins |
Coin Networkcoin_network_5m
|
One row per coin per 5 minutes | 5 minute coin network hash rate, difficulty, block data, and Bitcoin difficulty forecasts. |
| Coins |
Coin Pricecoin_price
|
One row per coin per 5 minutes | 5 minute USD price per coin. |
| Pools |
Pool Hash Rate (Historical)pool_hash_rate_historical
|
One row per pool worker per 5 minutes | Per-worker hash rate as reported by the pools' own APIs. |
| Weather |
Weather (Forecasted)weather_forecast
|
One row per location per forecast hour | 10 day hourly weather forecast by coordinates or US zip code. |
| Weather |
Weather (Historical)weather_historical
|
One row per location per hour | Hourly historical weather by coordinates or US zip code. |
Which miner explore should I use?
Five explores hold miner data and they share most of their fields, so the choice comes down to grain and coverage.
| If you want | Use | Why |
|---|---|---|
| Intraday trends, the last few days, anything at 5 minute or hourly grain | Miner Data (Online) | Full telemetry every 5 minutes for miners that were online. Joins earnings, power cost, hash price, and firmware errors. |
| Weekly, monthly, or quarterly reporting | Miner Data (Online - Daily) | One row per miner per day. Far fewer rows, so it is fast, and it carries the same revenue, cost, and margin measures. |
| A list or count of miners as they are right now | Miner Details | One row per miner record with its latest reading. Inventory, expected versus actual, and who has stopped reporting. |
| Offline counts, availability, or history that must include silent miners | Miner Data (All) | Built from snapshots of every miner record, so a miner that sent nothing still has a row. Miner details are historical too. |
| Health issues and how long they took to fix | Miner Issues | 15 minute snapshots of every Foreman health check per miner, with time to resolution. |
One more thing to know: the "online only" explores include a miner in a 5 minute window only if it reported during that window. Averages from those explores are averages of working miners. If you need to know how many miners were not working, use Miner Data (All).
Views that appear in many explores
Several views are joined into most of the miner-related explores so that context is always one click away. Each is documented once under Fields by view; the links below jump there.
- Miner Data - the 5 minute telemetry view. Appears as Miner Data (Historical) in time-series explores and Miner Data (Current) in snapshot explores. Same fields either way.
- Miner Details (Current) - the miner record as it is now: name, type, expected hash rate, state, Foreman configuration flags.
- Client Power Cost - the power price per MWh in effect for the client at each 5 minute mark.
- Coin Hash Price - the revenue per unit of hash rate at each 5 minute mark, used to value hash rate in dollars.
- Firmware Error Codes - individual firmware error codes reported by miners, one row per code.
- Client Data (Historical) - the client's configuration over time, including curtailment settings and power pricing setup.
- LMPs - locational marginal power prices, also available as its own explore.
To connect Claude to these explores, see How To: Build Foreman Intelligence Dashboards with Claude.
Miners: 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 (fields are listed below in this order)
Miners: 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 (fields are listed below in this order)
Miners: 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 (fields are listed below in this order)
Miners: 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 (fields are listed below in this order)
Miners: 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 (fields are listed below in this order)
Tickets: 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 (fields are listed below in this order)
Tickets: 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 (fields are listed below in this order)
Site Map: Site Map Data site_map_history
Looker description: Hourly snapshot of site maps data
Hourly snapshots of your Foreman site map: which racks exist, how big they are, and which miner sits in each position. The miner in each slot is joined to both its current and its hourly telemetry, so you can build heat maps and rack-level rollups as they looked at any hour in the past.
| Grain | One row per rack position per hour |
| Time field | Timestamp (1h) |
| Best for |
|
Example questions
- What was the average temperature per rack at 3 pm yesterday?
- Which racks have empty or disabled positions?
- How much power did each row draw per hour last week?
Views in this explore (fields are listed below in this order)
Curtailment: Dispatch Data dispatch_history
Looker description: Historical dispatch information
One row per dispatch, which is a curtailment or restore instruction Foreman executed: when it was created, when it started and ended, the power target it aimed for, how the load was ramped, which miners it applied to, why it happened, and where the instruction came from. This is the audit trail for curtailment.
| Grain | One row per dispatch |
| Time field | Start Date and End Date (5 minute precision), plus Created Date |
| Best for |
|
Example questions
- How many hours were we curtailed last month, and for what reasons?
- What target draw did each dispatch set, and how long did it last?
- Which dispatches came from the grid operator versus a manual request?
Views in this explore (fields are listed below in this order)
Curtailment: Dispatched Miners dispatch_miners
Looker description: Historical dispatch and miner data
Dispatches joined to the miners they affected. Each row pairs a dispatch's 5 minute target draw with the telemetry of a miner during that same window, so you can measure how the fleet actually responded to a curtailment: power before, during, and after, hash rate lost, and revenue impact.
| Grain | One row per miner per 5 minutes during a dispatch |
| Time field | Timestamp (5m) |
| Best for |
|
Example questions
- How far below the target draw did we get during yesterday's dispatch, minute by minute?
- How much hash rate did each site give up per dispatch last month?
- Which miners were still drawing full power 10 minutes into a curtailment?
Views in this explore (fields are listed below in this order)
Curtailment: Strike Price Data strike_price_history
Looker description: Historical strike price information
Foreman curtails when the price of power crosses a strike price. This explore records, every 5 minutes, the strike price in effect per client, miner type, and power mode, and joins the locational marginal price (LMP) at the same time, the client's curtailment configuration, and miner telemetry. It lets you see how close power prices came to your strike prices and what the fleet was doing at the time.
| Grain | One row per client, miner type, and power mode per 5 minutes |
| Time field | Timestamp (5m) |
| Best for |
|
Example questions
- How often did the LMP exceed our strike price last week?
- What strike price applied to each miner type and power mode yesterday?
- How many minutes per day were prices above the high strike price?
Views in this explore (fields are listed below in this order)
LMPs: LMPs lmps
Looker description: Locational Marginal Pricing for many zones in the world with granularity up to 5 minutes
Locational marginal prices (LMPs) for power markets Foreman tracks, keyed by ISO, market, and zone, at 5 minute granularity where the market publishes it. This is the price signal curtailment logic compares against strike prices. It stands alone with no miner data, so it is quick to query.
| Grain | One row per ISO, market, and zone per 5 or 15 minutes |
| Time field | Timestamp Date (5 minute, 15 minute, hourly, or daily) |
| Best for |
|
Example questions
- What was the average real-time price in our zone each hour yesterday?
- How many 5 minute intervals were above $100/MWh last month?
- How does day-ahead compare with real-time for the same day?
Views in this explore (fields are listed below in this order)
Coins: Coin Hash Price coin_hash_price
Looker description: Five minute aggregates of historical coin hash price data
Hash price is the revenue one unit of hash rate earns per day. This explore stores it every 5 minutes for each coin, in USD, BTC, and the coin itself, at several hash rate scales (H/s through PH/s), and splits it into block subsidy and transaction fee components. The same view is joined into most miner explores to value hash rate at the moment it was produced.
| Grain | One row per coin per 5 minutes |
| Time field | Timestamp Date |
| Best for |
|
Example questions
- What was the average USD hash price per PH/s each day this month?
- How much of hash price came from transaction fees last week?
- How does hash price in BTC compare with hash price in USD over time?
Views in this explore (fields are listed below in this order)
Coins: Coin Network coin_network_5m
Looker description: Five minute aggregates of historical coin network data
Network-level statistics for each coin Foreman tracks, sampled every 5 minutes: network hash rate, difficulty, block reward, and block time. For Bitcoin it also carries Foreman's forecast of the next difficulty adjustment and when that adjustment window starts and ends.
| Grain | One row per coin per 5 minutes |
| Time field | Timestamp Date |
| Best for |
|
Example questions
- How has Bitcoin network difficulty changed over the last 6 months?
- What is the forecast for the next difficulty adjustment and when does it land?
- What fraction of the network hash rate did our fleet represent last week?
Views in this explore (fields are listed below in this order)
Coins: Coin Price coin_price
Looker description: Five minute aggregates of historical coin price data
The USD price of each coin Foreman tracks, sampled every 5 minutes. Simple and standalone, useful for converting BTC figures to dollars or overlaying price on any other chart.
| Grain | One row per coin per 5 minutes |
| Time field | Timestamp Date |
| Best for |
|
Example questions
- What was the average BTC price per day last month?
- What was the BTC price at the time of each dispatch?
Views in this explore (fields are listed below in this order)
Pools: Pool Hash Rate (Historical) pool_hash_rate_historical
Looker description: Per-worker five minute hash rate directly from pool APIs
Hash rate as the mining pool measured it, pulled from pool APIs per worker every 5 minutes. Miner-reported hash rate and pool-observed hash rate rarely match exactly, and the difference is what you are paid on, so this explore is the check on what the pool actually credited.
| Grain | One row per pool worker per 5 minutes |
| Time field | Timestamp (5m) |
| Best for |
|
Example questions
- What total hash rate did the pool see from us per hour yesterday?
- Which workers had pool hash rate well below what the miners reported?
- How does pool hash rate compare across our pools?
Views in this explore (fields are listed below in this order)
Weather: Weather (Forecasted) weather_forecast
Looker description: 10 day, hourly forecasted weather data with coordinates or US zip code lookups
The same weather fields as the historical explore, but as a 10 day hourly forecast for any coordinates or US zip code. Use it to plan curtailment, maintenance, or cooling ahead of heat waves, storms, or freezes.
| Grain | One row per location per forecast hour |
| Time field | Timestamp (Hour) |
| Best for |
|
Example questions
- What is the forecast high temperature and heat index at our site each day this week?
- Are thunderstorms likely at the site in the next 48 hours?
- When does the forecast wet bulb temperature drop below 20 degrees?
Views in this explore (fields are listed below in this order)
Weather: Weather (Historical) weather_historical
Looker description: Hourly historical weather data with coordinates or US zip code lookups
Hourly historical weather for any location, looked up by coordinates or US zip code: temperature, humidity, wind, precipitation, and derived measures such as wet bulb, heat index, and wind chill. Use it to correlate site conditions with temperature issues, throttling, or downtime.
| Grain | One row per location per hour |
| Time field | Timestamp (Hour) |
| Best for |
|
Example questions
- What was the hourly outdoor temperature and wet bulb at our site last week?
- How did miner temperature issues line up with outdoor heat index in July?
- How many hours of rain did the site see last month?
Views in this explore (fields are listed below in this order)
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. Dimensions are attributes you can group and filter by. Measures are aggregates that add up, average, or count across the rows you select. Views shared by several explores appear once.
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. |
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 | 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. |
Site Map Racks (Historical)
Hourly snapshots of the racks on your site map: their names, sizes, and which site map group and client they belong to.
Used by: Site Map Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| Rack ID | Number | Numeric ID of the rack. |
| Rack Name | Text | Name of the rack on the site map. |
| Rack Size | Number | Number of positions in the rack. |
| Site Map Client ID | Number | Numeric ID of the client whose site map this is. |
| Site Map Client Name | Text | Name of that client. |
| Site Map Group ID | Number | ID of the site map group the rack belongs to, such as a building or container. |
| Site Map Group Name | Text | Name of that site map group. |
| Timestamp (1h) | Hour | Time of the hourly snapshot. |
Site Map Rack Locations (Historical)
Hourly snapshots of each position in each rack and the miner sitting in it. An empty position has no Miner ID. Join through Miner ID to the miner views for telemetry.
Used by: Site Map Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| Disabled (Yes / No) | Yes / No | Yes if the position has been disabled on the site map, so it is not expected to hold a miner. |
| Index | Number | Position index within the rack. |
| Miner Client ID | Number | Numeric ID of the client that owns the miner in the position. |
| Miner Client Name | Text | Name of the client that owns the miner in the position. |
| Miner ID | Number | Foreman ID of the miner in the position. Blank when the position is empty. |
| Rack ID | Text | ID of the rack the position belongs to. |
| Rack Name | Text | Name of that rack. |
| Row | Number | Row within the rack. |
| Timestamp (1h) | Hour | Time of the hourly snapshot. |
Dispatch History
One row per dispatch, which is a curtailment or restore instruction Foreman executed. It records the timing, the power target and how the load was ramped, which miners were included, why it happened, and where the instruction came from.
Used by: Dispatch Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Created Date | Date / time (Time, Date, Week, Month) | When the dispatch was created in Foreman. |
| End Date | Date / time (Time, 5 minute, Date, Week, Month) | When the dispatch ended or is scheduled to end, to 5 minute precision. |
| Start Date | Date / time (Time, 5 minute, Date, Week, Month) | When the dispatch took effect, to 5 minute precision. |
| Was Cancelled | Number | 1 if the dispatch was cancelled before it completed, 0 otherwise. |
| Client | ||
| Client ID | Number | Numeric ID of the client the dispatch applied to. |
| Client Name | Text | Name of that client. |
| Control Details | ||
| Buffer Draw | Number | Safety margin kept below the target draw so brief spikes do not breach it, in Buffer Units. |
| Buffer Units | Text | Unit for Buffer Draw, for example kW or MW. |
| Load When Dispatched | Number | The site's power draw at the moment the dispatch was issued, in Load When Dispatched Units. |
| Load When Dispatched Units | Text | Unit for Load When Dispatched. |
| Miners Filter | Text | The filter that selected which miners the dispatch applied to, for example by tag, type, or site map group. Blank means all miners. |
| Ramp Down Interval | Number | Seconds between steps when ramping load down. |
| Ramp Up Interval | Number | Seconds between steps when ramping load back up. |
| Target Draw | Number | The power level the dispatch aimed to bring the site to, in Target Units. |
| Target Draw (MW) | Number | Target Draw converted to megawatts. |
| Target Draw (kW) | Number | Target Draw converted to kilowatts. |
| Target Units | Text | Unit for Target Draw. |
| Event Details | ||
| Curtailment Reason | Text | Why the dispatch happened, for example a strike price being crossed, a grid operator request, or a manual action. |
| External Event ID | Text | Identifier from the external system that triggered the dispatch, such as a grid operator or demand response program event. |
| Extra Data | Text | Raw JSON with any additional details the dispatch carried. |
| Source | Text | Where the dispatch originated, for example a Foreman user, the strike price automation, or an external signal. |
| Type | Text | The kind of dispatch, such as a curtailment or a restore. |
Strike Price History
Every 5 minutes, the strike price in effect for each combination of client, miner type, and power mode. A strike price is the power price above which Foreman curtails; setting different prices per miner type and power mode lets efficient miners keep running longer than inefficient ones.
Used by: Strike Price Data
Dimensions
| Field | Type | What it means |
|---|---|---|
| Client ID | Number | Numeric ID of the client. |
| Client Name | Text | Name of the client. |
| Miner Type | Text | Miner model the strike price applies to. |
| Power Mode | Text | Power mode the strike price applies to, for example sleeping for a full shutdown or a low power mode for a partial curtailment. |
| Price | Number | The strike price, in dollars per megawatt-hour. |
| Primary Key | Text | Internal unique key for the row. Not useful for analysis. |
| Strike Type | Text | How the strike price was set. manual-miner-type means a price set by hand per miner type. |
| Timestamp (5m) | 5 minute timestamp | The 5 minute mark the price applies to. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Miner Count of Type | Count (distinct) | Number of distinct miners of the given type. |
| Strike Price Average | Average | Average strike price across the selected rows. |
| Strike Price Sum | Sum | Sum of strike prices across the selected rows. Mostly useful for weighted calculations. |
Dispatches Total (Historical)
The combined target draw of all dispatches active for a client in each 5 minute window. Joined to miner telemetry in the Dispatched Miners explore so actual draw can be compared with the target.
Used by: Dispatched Miners
Dimensions
| Field | Type | What it means |
|---|---|---|
| ID | Text | Internal key for the dispatch window. |
| Target Draw (MW) | Number | Combined target draw for the window, in megawatts. |
| Target Draw (kW) | Number | Combined target draw for the window, in kilowatts. |
| Timestamp (5m) | 5 minute timestamp | The 5 minute window. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Total Target Draw (MW) | Sum | Sum of Target Draw (MW) across distinct dispatch windows. |
| Total Target Draw (kW) | Sum | Sum of Target Draw (kW) across distinct dispatch windows. |
LMPs
Locational marginal prices: the wholesale price of power at a specific place on the grid, published by each ISO for its markets and zones. Foreman stores them at the finest granularity the market publishes (5 minutes for most real-time markets, hourly for day-ahead). This is the price signal that strike price curtailment compares against.
Used by: Strike Price Data, LMPs
Dimensions
| Field | Type | What it means |
|---|---|---|
| Currency | Text | Currency of the price. Blank means US dollars. |
| ISO | Text | The grid operator: ercot, pjm, miso, spp, nyiso, iso-ne, ieso, aeso, aemo, or omie. demo holds test data. |
| Market | Text | Which market the price is from: day-ahead or real-time. |
| Price | Number | Price per megawatt-hour. |
| Primary Key | Text | Internal unique key for the row. Not useful for analysis. |
| Timestamp Date | Date / time (5 minute, 15 minute, Hour, Date) | Time the price applies to, at 5 minute, 15 minute, hourly, or daily grain. |
| Zone | Text | Pricing node or load zone within the ISO. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Average Price | Average | Average price across the selected rows. |
| Total Price | Sum | Sum of prices across the selected rows. Mostly useful for weighted calculations. |
Coin Hash Price
Hash price is how much revenue one unit of hash rate earns per day, and it is the bridge between hash rate and dollars. Foreman records it every 5 minutes for each coin it tracks, in USD, BTC, and the coin itself, at several hash rate scales, and splits it into the part paid by block subsidy and the part paid by transaction fees. The Total fields combine both.
Used by: Miner Data (Online), Miner Details, Miner Data (All), Miner Issues, Ticket Data, Site Map Data, Strike Price Data, Dispatched Miners, Coin Hash Price
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Timestamp Date | Date / time (5 minute, Hour, Date, Week) | The 5 minute mark, at 5 minute, hourly, daily, or weekly grain. |
| Coin Info | ||
| Algo ID | Number | Foreman's numeric ID for the mining algorithm (SHA-256 for BTC). |
| Coin ID | Number | Foreman's numeric ID for the coin. |
| Coin Name | Text | Full name of the coin, for example Bitcoin. |
| Coin Symbol | Text | Ticker symbol, for example BTC. |
| Price Info | ||
| Hash Price BTC (H/s) | Number | Daily revenue in BTC per 1 H/s of hash rate, from block subsidy only. |
| Hash Price BTC (MH/s) | Number | Daily revenue in BTC per 1 MH/s of hash rate, from block subsidy only. |
| Hash Price BTC (PH/s) | Number | Daily revenue in BTC per 1 PH/s of hash rate, from block subsidy only. |
| Hash Price BTC (TH/s) | Number | Daily revenue in BTC per 1 TH/s of hash rate, from block subsidy only. |
| Hash Price BTC (kH/s) | Number | Daily revenue in BTC per 1 kH/s of hash rate, from block subsidy only. |
| Hash Price Coin (H/s) | Number | Daily revenue in units of the coin itself per 1 H/s, from block subsidy only. |
| Hash Price USD (H/s) | Number | Daily revenue in US dollars per 1 H/s of hash rate, from block subsidy only. |
| Hash Price USD (MH/s) | Number | Daily revenue in US dollars per 1 MH/s of hash rate, from block subsidy only. |
| Hash Price USD (PH/s) | Number | Daily revenue in US dollars per 1 PH/s of hash rate, from block subsidy only. |
| Hash Price USD (TH/s) | Number | Daily revenue in US dollars per 1 TH/s of hash rate, from block subsidy only. |
| Hash Price USD (kH/s) | Number | Daily revenue in US dollars per 1 kH/s of hash rate, from block subsidy only. |
| Total Hash Price BTC (PH/s) | Number | Total daily revenue in BTC per 1 PH/s, block subsidy plus transaction fees. |
| Total Hash Price Hash Price BTC (MH/s) | Number | Total daily revenue in BTC per 1 MH/s, block subsidy plus transaction fees. Use the Total figures for revenue estimates. |
| Total Hash Price Hash Price BTC (TH/s) | Number | Total daily revenue in BTC per 1 TH/s, block subsidy plus transaction fees. Use the Total figures for revenue estimates. |
| Total Hash Price Hash Price BTC (kH/s) | Number | Total daily revenue in BTC per 1 kH/s, block subsidy plus transaction fees. Use the Total figures for revenue estimates. |
| Total Hash Price Hash Price USD (MH/s) | Number | Total daily revenue in US dollars per 1 MH/s, block subsidy plus transaction fees. |
| Total Hash Price Hash Price USD (TH/s) | Number | Total daily revenue in US dollars per 1 TH/s, block subsidy plus transaction fees. |
| Total Hash Price Hash Price USD (kH/s) | Number | Total daily revenue in US dollars per 1 kH/s, block subsidy plus transaction fees. |
| Total Hash Price USD (PH/s) | Number | Total daily revenue in US dollars per 1 PH/s, block subsidy plus transaction fees. |
| Transaction Hash Price BTC (H/s) | Number | The transaction fee part of hash price, in BTC per 1 H/s per day. |
| Transaction Hash Price BTC (MH/s) | Number | The transaction fee part of hash price, in BTC per 1 MH/s per day. |
| Transaction Hash Price BTC (PH/s) | Number | The transaction fee part of hash price, in BTC per 1 PH/s per day. |
| Transaction Hash Price BTC (TH/s) | Number | The transaction fee part of hash price, in BTC per 1 TH/s per day. |
| Transaction Hash Price BTC (kH/s) | Number | The transaction fee part of hash price, in BTC per 1 kH/s per day. |
| Transaction Hash Price Coin (H/s) | Number | The transaction fee part of hash price, in units of the coin per 1 H/s per day. |
| Transaction Hash Price USD (H/s) | Number | The transaction fee part of hash price, in US dollars per 1 H/s per day. |
| Transaction Hash Price USD (MH/s) | Number | The transaction fee part of hash price, in US dollars per 1 MH/s per day. |
| Transaction Hash Price USD (PH/s) | Number | The transaction fee part of hash price, in US dollars per 1 PH/s per day. |
| Transaction Hash Price USD (TH/s) | Number | The transaction fee part of hash price, in US dollars per 1 TH/s per day. |
| Transaction Hash Price USD (kH/s) | Number | The transaction fee part of hash price, in US dollars per 1 kH/s per day. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Average Total Hash Price BTC (MH/s) | Average | Average of the total hash price in BTC per MH/s across the selected rows. |
| Average Total Hash Price BTC (PH/s) | Average | Average of the total hash price in BTC per PH/s across the selected rows. |
| Average Total Hash Price BTC (TH/s) | Average | Average of the total hash price in BTC per TH/s across the selected rows. |
| Average Total Hash Price BTC (kH/s) | Average | Average of the total hash price in BTC per kH/s across the selected rows. |
| Average Total Hash Price USD (MH/s) | Average | Average of the total hash price in US dollars per MH/s across the selected rows. |
| Average Total Hash Price USD (PH/s) | Average | Average of the total hash price in US dollars per PH/s across the selected rows. |
| Average Total Hash Price USD (TH/s) | Average | Average of the total hash price in US dollars per TH/s across the selected rows. |
| Average Total Hash Price USD (kH/s) | Average | Average of the total hash price in US dollars per kH/s across the selected rows. |
Coin Price
The US dollar price of each coin Foreman tracks, sampled every 5 minutes.
Used by: Coin Price
Dimensions
| Field | Type | What it means |
|---|---|---|
| Coin Name | Text | Full name of the coin. |
| Coin Price (USD) | Number | Price of one coin in US dollars at the time of the sample. |
| Coin Symbol | Text | Ticker symbol, for example BTC. |
| Timestamp Date | Date / time (5 minute, Hour, Date, Week) | The 5 minute mark, at 5 minute, hourly, daily, or weekly grain. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Average Coin Price (USD) | Average | Average price across the selected rows. |
Coin Network Stats
Network-wide statistics for each coin, sampled every 5 minutes: hash rate, difficulty, block reward, and block time.
Used by: Coin Network
Dimensions
| Field | Type | What it means |
|---|---|---|
| Coin Block Reward | Number | Current block subsidy, in units of the coin. |
| Coin Block Time | Number | Average seconds between blocks at the time of the sample. |
| Coin Name | Text | Full name of the coin. |
| Coin Network Difficultly (T) | Number | Network difficulty, in trillions. |
| Coin Network Hash Rate (EH) | Number | Total network hash rate, in exahashes per second. |
| Coin Symbol | Text | Ticker symbol, for example BTC. |
| Timestamp Date | Date / time (5 minute, Hour, Date, Week) | The 5 minute mark, at 5 minute, hourly, daily, or weekly grain. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Average Coin Network Difficulty (T) | Average | Average network difficulty across the selected rows, in trillions. |
| Average Coin Network Hash Rate (EH/s) | Average | Average network hash rate across the selected rows, in EH/s. |
Bitcoin Forecasted Difficulty
Foreman's estimate of the next Bitcoin difficulty adjustment, refreshed with each 5 minute network sample, with the expected start and end of the next difficulty period.
Used by: Coin Network
Dimensions
| Field | Type | What it means |
|---|---|---|
| Bitcoin Current Network Difficultly (T) | Number | Bitcoin network difficulty at the time of the sample, in trillions. |
| Bitcoin Forecasted Next Network Difficultly (T) | Number | Forecast difficulty after the next adjustment, in trillions. |
| Bitcoin Forecasted Next Network Difficultly End Time | Date / time | When the next difficulty period is expected to end. |
| Bitcoin Forecasted Next Network Difficultly Start Time | Date / time | When the next difficulty period is expected to begin. |
Measures
| Measure | Type | What it means |
|---|---|---|
| Average Bitcoin Current Network Difficulty (T) | Average | Average current difficulty across the selected rows, in trillions. |
| Average Bitcoin Forecasted Network Difficulty (T) | Average | Average forecast difficulty across the selected rows, in trillions. |
| Max Bitcoin Forecasted Next Network Difficultly End Time | Minute timestamp | Latest forecast end time in the selection. |
| Max Bitcoin Forecasted Next Network Difficultly Start Time | Minute timestamp | Latest forecast start time in the selection. |
Pool Hash Rate Historical
Hash rate as the mining pool measured it, pulled from the pool's API for each worker every 5 minutes. Pool-observed hash rate is what you are paid on, so it is the check on what the miners themselves report.
Used by: Pool Hash Rate (Historical)
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Client ID | Number | Numeric ID of the client whose pool account this is. |
| Pool Name | Text | The pool account the data came from, as configured in Foreman's pool integrations. |
| Timestamp (5m) | 5 minute timestamp | Start of the 5 minute window. |
| Worker Name | Text | Worker name as the pool knows it. |
| Hash Rate | ||
| Average Hash Rate (MH) | Number | Hash rate the pool measured for the worker over the window, in megahashes per second (MH/s). |
| Average Hash Rate (PH) | Number | Hash rate the pool measured for the worker over the window, in petahashes per second (PH/s). |
| Average Hash Rate (TH) | Number | Hash rate the pool measured for the worker over the window, in terahashes per second (TH/s). |
| Average Hash Rate (kH) | Number | Hash rate the pool measured for the worker over the window, in kilohashes per second (kH/s). |
Measures
| Measure | Type | What it means |
|---|---|---|
| Total Hash Rate (MH) | Sum | Sum of pool-measured hash rate across the selected rows, in megahashes per second (MH/s). Group by time for a time series. |
| Total Hash Rate (PH) | Sum | Sum of pool-measured hash rate across the selected rows, in petahashes per second (PH/s). Group by time for a time series. |
| Total Hash Rate (TH) | Sum | Sum of pool-measured hash rate across the selected rows, in terahashes per second (TH/s). Group by time for a time series. |
| Total Hash Rate (kH) | Sum | Sum of pool-measured hash rate across the selected rows, in kilohashes per second (kH/s). Group by time for a time series. |
Weather Historical
Hourly historical weather for a location, looked up by coordinates or US zip code. Temperatures are in Fahrenheit, speeds in miles per hour, and amounts in inches unless the matching Unit field says otherwise.
Used by: Weather (Historical)
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Timestamp (Hour) | Hour | The hour the observed conditions apply to. |
| Ice | ||
| Ice Thickness | Number | Observed ice accumulation for the hour. |
| Ice Thickness Unit | Text | Unit for Ice Thickness. |
| Location | ||
| Location | Location | Latitude and longitude of the weather point. Filter on it to pick a site. |
| Zipcode | Text | US zip code, for lookups by zip instead of coordinates. |
| Miscellaneous | ||
| Air Pressure Msl Mb | Number | Air pressure at mean sea level, in millibars. |
| Cloud Cover | Number | Percent of the sky covered by cloud. |
| Is Daytime (Yes / No) | Yes / No | Yes between sunrise and sunset. |
| Relative Humidity | Number | Relative humidity, in percent. |
| Uv Index | Number | UV index for the hour. |
| Weather Description | Text | Short text summary such as Sunny, Cloudy, Light rain, or Thunderstorm. |
| Precipitation | ||
| Precip Prob Percent | Number | Probability of precipitation, in percent. |
| Precip Prob Type | Text | Type of precipitation expected: RAIN, SNOW, or RAIN_AND_SNOW. |
| Precip Qpf Quantity | Number | Amount of precipitation for the hour, in Precip Qpf Unit. |
| Precip Qpf Unit | Text | Unit for Precip Qpf Quantity (inches). |
| Thunderstorm Probability | Number | Probability of a thunderstorm, in percent. |
| Temperature | ||
| Dew Point Degrees | Number | Dew point temperature. |
| Dew Point Unit | Text | Unit for Dew Point Degrees. |
| Feels Like Degrees | Number | Apparent temperature accounting for wind and humidity. |
| Feels Like Unit | Text | Unit for Feels Like Degrees. |
| Heat Index Degrees | Number | Heat index, combining temperature and humidity. |
| Heat Index Unit | Text | Unit for Heat Index Degrees. |
| Temperature Degrees | Number | Air temperature. |
| Temperature Unit | Text | Unit for Temperature Degrees (Fahrenheit). |
| Wet Bulb Degrees | Number | Wet bulb temperature, the key number for evaporative cooling capacity. |
| Wet Bulb Unit | Text | Unit for Wet Bulb Degrees. |
| Wind Chill Degrees | Number | Wind chill temperature. |
| Wind Chill Unit | Text | Unit for Wind Chill Degrees. |
| Visibility | ||
| Visibility Distance | Number | Visibility distance. |
| Visibility Unit | Text | Unit for Visibility Distance (miles). |
| Wind | ||
| Wind Direction Cardinal | Text | Direction the wind comes from, as a compass point such as NW. |
| Wind Direction Degrees | Number | Direction the wind comes from, in degrees. |
| Wind Gust Unit | Text | Unit for Wind Gust Value. |
| Wind Gust Value | Number | Peak wind gust speed. |
| Wind Speed Unit | Text | Unit for Wind Speed Value (miles per hour). |
| Wind Speed Value | Number | Sustained wind speed. |
Weather Forecast
Hourly weather forecast for the next 10 days for a location, looked up by coordinates or US zip code. Temperatures are in Fahrenheit, speeds in miles per hour, and amounts in inches unless the matching Unit field says otherwise.
Used by: Weather (Forecasted)
Dimensions
| Field | Type | What it means |
|---|---|---|
| General | ||
| Timestamp (Hour) | Hour | The hour the forecast conditions apply to. |
| Ice | ||
| Ice Thickness | Number | Expected ice accumulation for the hour. |
| Ice Thickness Unit | Text | Unit for Ice Thickness. |
| Location | ||
| Location | Location | Latitude and longitude of the weather point. Filter on it to pick a site. |
| Zipcode | Text | US zip code, for lookups by zip instead of coordinates. |
| Miscellaneous | ||
| Air Pressure Msl Mb | Number | Air pressure at mean sea level, in millibars. |
| Cloud Cover | Number | Percent of the sky covered by cloud. |
| Is Daytime (Yes / No) | Yes / No | Yes between sunrise and sunset. |
| Relative Humidity | Number | Relative humidity, in percent. |
| Uv Index | Number | UV index for the hour. |
| Weather Description | Text | Short text summary such as Sunny, Cloudy, Light rain, or Thunderstorm. |
| Precipitation | ||
| Precip Prob Percent | Number | Probability of precipitation, in percent. |
| Precip Prob Type | Text | Type of precipitation expected: RAIN, SNOW, or RAIN_AND_SNOW. |
| Precip Qpf Quantity | Number | Forecast amount of precipitation for the hour, in Precip Qpf Unit. |
| Precip Qpf Unit | Text | Unit for Precip Qpf Quantity (inches). |
| Thunderstorm Probability | Number | Probability of a thunderstorm, in percent. |
| Temperature | ||
| Dew Point Degrees | Number | Dew point temperature. |
| Dew Point Unit | Text | Unit for Dew Point Degrees. |
| Feels Like Degrees | Number | Apparent temperature accounting for wind and humidity. |
| Feels Like Unit | Text | Unit for Feels Like Degrees. |
| Heat Index Degrees | Number | Heat index, combining temperature and humidity. |
| Heat Index Unit | Text | Unit for Heat Index Degrees. |
| Temperature Degrees | Number | Air temperature. |
| Temperature Unit | Text | Unit for Temperature Degrees (Fahrenheit). |
| Wet Bulb Degrees | Number | Wet bulb temperature, the key number for evaporative cooling capacity. |
| Wet Bulb Unit | Text | Unit for Wet Bulb Degrees. |
| Wind Chill Degrees | Number | Wind chill temperature. |
| Wind Chill Unit | Text | Unit for Wind Chill Degrees. |
| Visibility | ||
| Visibility Distance | Number | Visibility distance. |
| Visibility Unit | Text | Unit for Visibility Distance (miles). |
| Wind | ||
| Wind Direction Cardinal | Text | Direction the wind comes from, as a compass point such as NW. |
| Wind Direction Degrees | Number | Direction the wind comes from, in degrees. |
| Wind Gust Unit | Text | Unit for Wind Gust Value. |
| Wind Gust Value | Number | Peak wind gust speed. |
| Wind Speed Unit | Text | Unit for Wind Speed Value (miles per hour). |
| Wind Speed Value | Number | Sustained wind speed. |
Comments
0 comments
Please sign in to leave a comment.