Online Game Server Energy Log
This dataset provides detailed logs of energy consumption and operational downtime for online game servers, including location, performance metrics, and green certification status. It enables gaming companies to monitor infrastructure efficiency, identify cost-saving opportunities, and support sustainability compliance initiatives.
Sample rows
preview · 8 of 68 rows · all 15 columns| log_idstring | downtime_reasonstring | average_cpu_utilization_percentfloat | is_green_certifiedboolean | server_idstring | server_namestring | location_countrystring | location_citystring | energy_consumption_kwhfloat | log_start_timedatetime | log_end_timedatetime | downtime_minutesinteger | peak_power_kwfloat | average_memory_utilization_percentfloat | notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AB12cd34 | blank | 58.3 | true | SRV001 | Orion-NA01 | United States | Dallas | 528.4 | 2024-05-01T08:00:00Z | 2024-05-02T08:00:00Z | 0 | 6.8 | 67.7 | Stable operation throughout |
| Xz70_ghQ | Scheduled maintenance | 61 | false | SRV002 | Atlas-EU02 | Germany | Frankfurt | 479.2 | 2024-05-01T09:00:00Z | 2024-05-02T09:00:00Z | 12 | 6.4 | 65.2 | Routine patch applied |
| qWErty12 | blank | 73.3 | true | SRV003 | Lyra-AP01 | Japan | Tokyo | 612.7 | 2024-05-03T07:00:00Z | 2024-05-04T07:00:00Z | 0 | 7.1 | 80.4 | High user activity, no downtime |
| ZXcvbn56 | Hardware failure | 69.5 | false | SRV004 | Draco-SA01 | Brazil | Sao Paulo | 510.6 | 2024-05-02T10:00:00Z | 2024-05-03T10:00:00Z | 27 | 6.1 | 75.2 | Emergency repair required |
| POIuyt67 | blank | 56.1 | false | SRV005 | Vega-EU03 | France | Paris | 495.9 | 2024-05-04T08:00:00Z | 2024-05-05T08:00:00Z | 0 | 6.5 | 69.3 | blank |
| GHjklo89 | Power outage | 59.4 | true | SRV006 | Phoenix-NA02 | United States | Chicago | 576.2 | 2024-05-05T08:00:00Z | 2024-05-06T08:00:00Z | 6 | 6.7 | 71.9 | Short outage, UPS engaged |
| MNopqw12 | blank | 78.2 | true | SRV007 | Sirius-AP02 | Singapore | Singapore | 620.5 | 2024-05-06T07:00:00Z | 2024-05-07T07:00:00Z | 0 | 7.3 | 85.3 | Green certified, high demand |
| LKjhgf34 | Network upgrade | 53.7 | true | SRV008 | Arcturus-EU04 | Netherlands | Amsterdam | 488.1 | 2024-05-07T09:00:00Z | 2024-05-08T09:00:00Z | 17 | 5.9 | 68 | blank |
| QWEasd90 | blank | 60.8 | false | SRV009 | Hydra-NA03 | United States | San Jose | 502.3 | 2024-05-08T08:00:00Z | 2024-05-09T08:00:00Z | 0 | 6.2 | 70.2 | blank |
| ZXcvbn78 | Unplanned restart | 65.1 | false | SRV010 | Rigel-SA02 | Argentina | Buenos Aires | 523.4 | 2024-05-09T10:00:00Z | 2024-05-10T10:00:00Z | 9 | 6 | 76.2 | Restart due to OS crash |
| qweRTY45 | blank | 50.6 | true | SRV011 | Polaris-EU05 | Sweden | Stockholm | 471.7 | 2024-05-10T09:00:00Z | 2024-05-11T09:00:00Z | 0 | 5.8 | 62.1 | Low traffic period |
| MNBvcxz56 | blank | 54.4 | true | SRV012 | Andromeda-NA04 | Canada | Toronto | 537.9 | 2024-05-11T08:00:00Z | 2024-05-12T08:00:00Z | 0 | 6.6 | 70.9 | blank |
| uIopAS23 | Maintenance | 55.2 | false | SRV013 | Altair-EU06 | Italy | Milan | 482.6 | 2024-05-12T09:00:00Z | 2024-05-13T09:00:00Z | 24 | 5.7 | 64.5 | Scheduled downtime |
| GHjkLO67 | blank | 75.6 | true | SRV014 | Betelgeuse-AP03 | South Korea | Seoul | 609.1 | 2024-05-13T07:00:00Z | 2024-05-14T07:00:00Z | 0 | 7 | 82.8 | blank |
| QWErtY78 | blank | 57.8 | false | SRV015 | Castor-EU07 | Spain | Madrid | 477.8 | 2024-05-14T08:00:00Z | 2024-05-15T08:00:00Z | 0 | 5.6 | 68.7 | No incidents |
| ZXcvbn34 | Power outage | 60.2 | false | SRV016 | Mira-SA03 | Chile | Santiago | 509.4 | 2024-05-15T10:00:00Z | 2024-05-16T10:00:00Z | 15 | 6.3 | 72.5 | Brief local outage |
| qweRTY90 | blank | 49.9 | true | SRV017 | Aldebaran-EU08 | Denmark | Copenhagen | 464.2 | 2024-05-16T09:00:00Z | 2024-05-17T09:00:00Z | 0 | 5.5 | 61.5 | blank |
| MNBvcxz90 | Network outage | 62.7 | false | SRV018 | Deneb-NA05 | United States | Seattle | 551.7 | 2024-05-17T08:00:00Z | 2024-05-18T08:00:00Z | 3 | 6.9 | 73.8 | Network quickly restored |
| uIopAS89 | blank | 80.1 | true | SRV019 | Capella-AP04 | Australia | Sydney | 633.8 | 2024-05-18T07:00:00Z | 2024-05-19T07:00:00Z | 0 | 7.5 | 88.2 | High weekend load |
| GHjkLO90 | Hardware failure | 56.9 | false | SRV020 | Canopus-EU09 | Poland | Warsaw | 489.6 | 2024-05-19T09:00:00Z | 2024-05-20T09:00:00Z | 8 | 5.7 | 67.2 | blank |
What the 68 rows show
from the 68-row sample- 46%is_
green_ certified = true - 56.4median average_
cpu_ utilization_ percent - 318.4median energy_
consumption_ kwh - 0median downtime_
minutes - 9.0median peak_
power_ kw - 68.3median average_
memory_ utilization_ percent
Median 56.4, from 45.2 to 84.2.
- string 7
- integer 1
- float 4
- datetime 2
- boolean 1
Columns
15 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 7 columns | |||
log_id | string | Unique identifier for each energy log entryunique | AB12cd34 |
server_id | string | Unique identifier for the game server | SRV001 |
server_name | string | Human-readable name of the game server | Orion-NA01 |
location_country | string | Country where the server is physically located | United States |
location_city | string | City where the server is physically located | Dallas |
downtime_reason | string | Primary reason for downtime (e.g., maintenance, hardware failure, power outage)8 reasons · optional | Scheduled maintenance |
notes | string | Additional notes or comments about the log entryoptional | Routine patch applied |
| Numbers 5 columns | |||
energy_consumption_kwh | float | Amount of energy consumed by the server during the log period, in kilowatt-hours0 or more | 528.4 |
downtime_minutes | integer | Total minutes of operational downtime during the log period0 or more | 0 |
peak_power_kw | float | Peak power usage during the log period, in kilowatts0 or more · optional | 6.8 |
average_cpu_utilization_percent | float | Average CPU utilization during the log period, as a percentage0 to 100 · optional | 58.3 |
average_memory_utilization_percent | float | Average memory utilization during the log period, as a percentage0 to 100 · optional | 67.7 |
| Dates and times 2 columns | |||
log_start_time | datetime | Start timestamp for the energy log period | 2024-05-01T08:00:00Z |
log_end_time | datetime | End timestamp for the energy log period | 2024-05-02T08:00:00Z |
| True or false 1 column | |||
is_green_certified | boolean | Indicates if the server or data center is certified for green energy standardsoptional | true |
Use it for
A gaming dashboard
The is_
green_ certified rate and average_ cpu_ utilization_ percent by downtime_ reason. Excel, Power BI or Tableau. Why do 31 of 68 rows have is_
green_ certified = true? A class exercise
Hand out the rows and one question. Everyone works from the same 68 rows.
- Logs68AB12cd3458.3—Xz70_ghQ61Schedule…qWErty1273.3—
A software demo
Believable logs with server_
id, server_ name and location_ country to fill a screen in front of a buyer.
blueprint · online-game-server-energy-log
Behind this dataset
Same schema. As many rows as you need.
These 68 rows came out of a blueprint — 15 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
- Each server entry must include unique server ID
- Energy usage recorded per hour, with downtime flagged
- Downtime entries must specify duration and reason
- Region must be specified for each server
- Flag high-usage servers for review
1 credit per row. New accounts start with 25 free credits.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- online-game-server-energy-log