Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1NxZTUI. Tal Weiss shows how you can easily write your own JVM agent to capture accurate performance data for virtually any type of application from Java microservices to reactive actor systems in Scala, and connect them to any modern DevOps graphing and alerting tool. Filmed at qconsf.com. Tal Weiss is the CEO of Takipi - God Mode in Production Code. Tal has been designing scalable, real-time Java and C++ applications for the past 15 years. He still enjoys analyzing a good core dump and instrumenting Java code.

1. DIY Production Monitoring

2. InfoQ.com: News & Community Site
• 750,000 unique visitors/month
• Published in 4 languages (English, Chinese, Japanese and Brazilian
Portuguese)
• Post content from our QCon conferences
• News 15-20 / week
• Articles 3-4 / week
• Presentations (videos) 12-15 / week
• Interviews 2-3 / week
• Books 1 / month
Watch the video with slide
synchronization on InfoQ.com!
http://www.infoq.com/presentations
/jvm-performance-monitoring-tools

3. Purpose of QCon
- to empower software development by facilitating the spread of
knowledge and innovation
Strategy
- practitioner-driven conference designed for YOU: influencers of
change and innovation in your teams
- speakers and topics driving the evolution and innovation
- connecting and catalyzing the influencers and innovators
Highlights
- attended by more than 12,000 delegates since 2007
- held in 9 cities worldwide
Presented at QCon San Francisco
www.qconsf.com

4. About Me
Co-founder – Takipi, JVM Production Debugging.
Director, AutoCAD Web & Mobile.
Software Architect at IAI Aerospace.
Coding for the past 16 years - C++, Delphi, .NET, Java.
Focus on real-time, scalable systems.
Blogs at blog.takipi.com

5. Java Agents
• An advanced technique for instrumenting code dynamically.
• The foundation of modern profiling / debugging tools.
• Two types of agents: Java and Native.
• Pros: extremely powerful technique to collect state from a live app.
• Cons: requires knowledge of creating verifiable bytecode.

6. Agent Types
• Java agents are written in Java. Have access to the Instrumentation BCI API.
• Native agents – written in C++.
• Have access to JVMTI – the JVM’s low-level set of APIs and capabilities.
– JIT compilation, Garbage Collection, Monitor acquisition, Exception callbacks, ..
• More complex to write.
• Platform dependent.

7. Java Profiling Agents
github.com/takipi/profiling-agent

8. Thread Names
• Thread name is a mutable property.
• Can be set to hold transaction specific state.
• Some frameworks (e.g. EJB) don’t like that.
• Can be super helpful when debugging in tandem with jstack.

9. Thread Names (2)
For example:
Thread.currentThread().setName(
Context + TID + Params + current Time, ...);
Before:
“pool-1-thread-1″ #17 prio=5 os_prio=31 tid=0x00007f9d620c9800
nid=0x6d03 in Object.wait() [0x000000013ebcc000
After:
”Queue Processing Thread, MessageID: AB5CAD, type: AnalyzeGraph,
queue: ACTIVE_PROD, Transaction_ID: 5678956, Start Time:
10/8/2014 18:34″ #17 prio=5 os_prio=31 tid=0x00007f9d620c9800
nid=0x6d03 in Object.wait() [0x000000013ebcc000]

11. Modern Stacks - Java 8

12. Modern Stacks - Scala

14. Watch the video with slide synchronization on
InfoQ.com!
http://www.infoq.com/presentations/jvm-
performance-monitoring-tools