• Gaming
  • 16 columns
  • 120 rows
  • 8 formats

Gaming Server Energy Usage Logs

This dataset provides detailed, time-stamped logs of energy consumption and operational metrics across gaming servers, including power usage, performance statistics, sustainability indicators, and server status. It enables operations teams to monitor real-time efficiency, track historical trends, and support sustainability initiatives by analyzing renewable energy usage and carbon emissions. The dataset is ideal for optimizing server infrastructure, reducing costs, and improving uptime in gaming environments.

  • last updated 18 Jan 2026
  • by GoMask
The brief that made it

Real-time monitoring and alerting for abnormal server energy usage

Sample rows

preview · 8 of 120 rows · all 16 columns
log_idstringserver_statusstringcpu_utilization_percentfloatserver_namestringserver_idstringdata_center_idstringdata_center_locationstringtimestampdatetimeenergy_consumed_kwhfloatpower_draw_wattsfloatgpu_utilization_percentfloatmemory_usage_gbfloatrenewable_energy_percentfloatcarbon_emissions_kgco2efloatuptime_secondsintegernotesstring
LOG-0001active77.4Orion-GammaSRV-A02DC-SEA-01Seattle Data Center, WA, USA2024-05-01T08:14:23Z7.121245.58264.294.50.397742321Tournament event
LOG-0002active65.2CentauriSRV-J13DC-PAR-02Paris Cloud Facility, Paris, FR2024-05-01T09:47:12Z2.38621.928.724.610001849223Powered by 100% renewable
LOG-0003active92.6blankSRV-T27DC-MEX-04Mexico City, MX2024-05-01T11:03:09Z13.551457.797.4127.61222.89912212Peak load
LOG-0004active81.5Pioneer-VegaSRV-E19DC-JHB-11Johannesburg, South Africa2024-05-01T12:26:44Z8.971042.393.284.79.531.178123442High traffic
LOG-0005idle9AtlasSRV-X04DC-SEA-01Seattle Data Center, WA, USA2024-05-01T13:03:19Z0.4244.82.73.699.60.011143223blank
LOG-0006idle2.1HeliosSRV-H34DC-SYD-07Sydney, NSW, Australia2024-05-01T13:55:10Z0.089.302.482.70.0377432Scheduled downtime
LOG-0007idle3.5CentauriSRV-J13DC-PAR-02Paris Cloud Facility, Paris, FR2024-05-01T14:22:11Z0.2121.91.11.910001849811blank
LOG-0008active51.7NovaSRV-D08DC-DEL-06Delhi, India2024-05-01T15:30:02Z5.47820.61932.416.25.774828222blank

What the 120 rows show

from the 120-row sample

Active (server status) stands out: mean cpu_utilization_percent is 66.0, against 6.2 for the rest.

  • 32.1median cpu_utilization_percent
  • 25data centers
  • 0.45median energy_consumed_kwh
  • 52.0median power_draw_watts
  • 5.7median gpu_utilization_percent
  • 12.8median memory_usage_gb
Mean cpu_utilization_percent by server_status98 rows
05010066.0active51 rows8.3idle31 rows2.2maintenance16 rows
cpu_utilization_percent98 rows, in bands of 10
02040386466977411050100cpu_utilization_percent →

Median 32.1, from 0.0 to 99.8.

server_name105 rows with a value · 15 left blank
  1. Atlas9
  2. Nova9
  3. Helios8
  4. Apollo7
  5. Gemini7
  6. Centauri4
  7. Pioneer-Vega4
  8. Zephyr4
  9. Astra4
  10. Pegasus4
16 columns by typefrom the column list below
  • string 7
  • integer 1
  • float 7
  • datetime 1

Columns

16 columns in three groups
blueprint · 16 columns
columntypedescriptionexample
Text 7 columns
log_idstringUnique identifier for each energy usage log entryuniqueLOG-0001
server_idstringUnique identifier for the gaming serverSRV-A02
server_namestringHuman-readable name of the gaming serveroptionalOrion-Gamma
data_center_idstringIdentifier for the data center where the server is locatedoptionalDC-SEA-01
data_center_locationstringGeographical location or address of the data centeroptionalMexico City, MX
server_statusstringOperational status of the server at the time of loggingactive · idle · maintenance · offline · optionalactive
notesstringOptional notes or comments about the log entry (e.g., anomalies, maintenance events)optionalTournament event
Numbers 8 columns
energy_consumed_kwhfloatAmount of energy consumed by the server during the logging interval, measured in kilowatt-hours (kWh)0 or more7.12
power_draw_wattsfloatInstantaneous power draw of the server at the time of logging, measured in watts (W)0 or more · optional1245.5
cpu_utilization_percentfloatCPU utilization percentage of the server at the time of logging0 to 100 · optional77.4
gpu_utilization_percentfloatGPU utilization percentage of the server at the time of logging0 to 100 · optional82
memory_usage_gbfloatAmount of memory used by the server at the time of logging, measured in gigabytes (GB)0 or more · optional64.2
renewable_energy_percentfloatPercentage of energy supplied from renewable sources at the data center during the logging interval0 to 100 · optional94.5
carbon_emissions_kgco2efloatEstimated carbon emissions (in kg CO2 equivalent) associated with the energy consumed during the logging interval0 or more · optional0.39
uptime_secondsintegerNumber of seconds the server has been continuously operational at the time of logging0 or more · optional7742321
Dates and times 1 column
timestampdatetimeDate and time when the energy usage was recorded (UTC recommended)2024-05-01T08:14:23Z

Use it for

  • median cpu uti…32.198 rowsmean cpu utilization …66.0active8.3idle2.2mainte…

    A gaming dashboard

    Cpu_utilization_percent by server_status and a breakdown of server_name. Excel, Power BI or Tableau.

  • Why do the 51 active rows have a mean cpu_utilization_percent of 66.0?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable logs with server_id, server_name and data_center_id to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 16 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset120 rows16 columns
Yours1,000 rows16 columnsdata_center_location: UK only

blueprint · gaming-server-energy-usage-logs

Behind this dataset

Same schema. As many rows as you need.

These 120 rows came out of a blueprint — 16 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.

Rules it was built with
  • Each row represents one hourly interval per server.
  • Energy usage (kWh) must be recorded for every interval.
  • Include server location and hardware type to allow segmentation.
  • Flag intervals exceeding threshold for further investigation.
  • Each server must have at least three consecutive intervals logged.
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
gaming-server-energy-usage-logs

What should your data show?

Preview 20 rows free
No signup. No card.