Continuous Monitoring With JDK Flight Recorder (JFR)
summary
JDK Flight Recorder (JFR) is built into the runtime, captures ~140 event types and now supports event streaming (available in JDK 14) that dumps repository snapshots roughly once per second. Events are written into thread-local buffers, promoted to global buffers, then stored in a compact self‑describing file; default overhead targets <1%. Demos show a Spring Boot app emitting HTTP events, an external monitor detecting requests >500 ms, then streaming a one‑second lookback to correlate GC, CPU and lock activity.
AI-written summary · about
chapters (17)
- 0:00Introduction to JFR
- 2:50What is JDK Flight Recorder
- 8:27History of JFR
- 11:18JFR Events Explained
- 14:30Creating Custom Events
- 23:32JFR Event Types
- 25:00How JFR Works Internally
- 28:52JFR File Format
- 31:00Filtering JFR Data
- 33:27JFR in Production
- 41:32JFR Performance Overhead
- 44:46Using JFR Commands
- 47:16Demo: Recording JFR Data
- 50:50Future of JFR in JDK 14
- 54:00Demo: Continuous Monitoring
- 1:00:32Future Work and Integration
- 1:01:58Resources and Summary
related talks
46mContinuous Monitoring with JDK Flight Recorder
42mContinuous Monitoring with JDK Flight Recorder
39mProgrammer's Guide to JDK Flight Recorder
56mTaking Off With #JDK #FlightRecorder
42mProfiling and monitoring with the JDK
45mAnalyzing Safe Flights, and Firey Wrecks with JDK Flight Recorder
39mProfiling and Monitoring with the JDK
18mContinuous Monitoring w/ JDK Flight Recorder (JFR)