Takipi
0 likes129 views
This document introduces Eudy Sekgota, a software developer of 4 years, and provides information about the error monitoring tool Takipi. It explains that Takipi uses JVMTI to monitor Java applications without impacting performance, collects and analyzes data to recreate errors and diagnose their root causes. Some benefits of Takipi mentioned are helping teams or individuals quickly solve intermittent issues or problems in legacy code without wasting time replicating errors.
Takipi
- 1. About Me Im Eudy Sekgota, Software Developer for 4 years at BBD Twitter:@SekgotaEudy PS4:eudy501
- 2. I really think every Java developer should know or start using
- 3. See Why and When your Code Breaks in Production
- 4. How does Takipi work uses the JVMTI to talk to the JVM Takipi runs as a Java agent and a native daemon collector process The daemon process sends data to Takipis central Analysis engine The Analysis engine recreates the crime scene by storing actual source code and variables values which cause errors
- 5. Perfomance Capped CPU overhead (< 3%) Dynamic throttling No reliance on logs Network overhead (< 50Mb per hour) No GC overhead No dependency on Takipi
- 6. Security Two factor authentication and data encryption Personally identifiable information filtering On- premises storage(Enterprise)
- 7. Why you might need Takipi Find root causes to intermittent issues If you are one man Team Want to quickly solve problems in legacy code Dont want to waste time trying to replicate issues.
- 8. Thank you. Happy Debugging
- 9. References http://docs.oracle.com/javase/7/docs/platform/jv mti/jvmti.html#whatIs http://blog.takipi.com/double-agent-java-vs-nati ve-agents/ http://blog.takipi.com/how-to-write-your-own-ja va-scala-debugger/ http://blog.takipi.com/using-reflection-to-look-in side-the-jvm-at-run-time/ https://docs.takipi.com/hc/en-us/sections/2040 70608