Observing Minecraft
summary
Sets up a Java Minecraft server on EC2 using a CraftBukkit server, drops in a GitHub plugin called “Minecraft for Prometheus exporter” to expose metrics over HTTP (default port 9225), and collects JVM and host stats with Datadog agent + Java agent instead of full Prometheus+Grafana. Captured metrics include player counts, spawned mobs, chunk loads, JVM thread counts, GC and tick timings; memory tuning (Xmx) matters — low heap causes slow chunk loading rather than host crashes — and visualizes results in Datadog dashboards.
AI-written summary · about
chapters (7)
- 0:00Introduction to talk
- 2:33Why observe Minecraft
- 5:02Live server setup
- 13:16Extracting player metrics
- 17:01Adding monitoring tools
- 26:15Observability results
- 28:08Q&A session
related talks
32mOps for Developers - Monitor Your Java Application with Prometheus
48mState of the Java Metrics Libraries
52mIs your JVM app flying blind? Unmask hidden issues with Observability superpowers!
45mMicroProfile Metrics: Practical Use Cases
45mJava Performance Analysis and Optimization
35mMonitoring Distributed Java Applications at Scale
26mMake Monitoring Easy for your Java Apps
30mPrometheus Monitoring for Java Web Applications w o Modifying Source Code