- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Virtual threads support
- Object allocation profiling
- Memory profiling
- Monitor profiling
- Exception profiling
- Telemetry
- Probes: monitor events of various kinds
- Events in user interface
- Event inspections
- Built-in probes
- Probe classes
- Monitoring method invocation events
- Probe class annotation @MethodPattern
- Callback onEnter()
- Callback onReturn()
- Callback onExit()
- Callbacks onUncaughtException() and onUncaughtExceptionExt()
- Parameter annotation @Param
- Parameter annotation @Params
- Parameter annotation @This
- Parameter annotation @ClassRef
- Parameter annotation @MethodName
- Parameter annotation @MethodTimeMs
- Parameter annotation @MethodTimeNs
- Parameter annotation @MethodParameterTypes
- Parameter annotation @MethodSignature
- Parameter annotation @OnEnterResult
- Parameter annotation @ReturnValue
- Parameter annotation @ThrownException
- Probe application rules
- Data storage
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary
- Filters
- Profiler command line
- Export of profiling results to external formats
- Profiler Java API
- Profiler HTTP API
- Settings
- Troubleshooting and FAQ
Built-in probes
We have prepared a set of probes to help investigating typical problems. The probes are ready to use out of the box. Also you can use them as good examples to start with should you decide creating custom probes.
The following built-in probes are available at the moment:
com.yourkit.probes.builtin.AsyncChannels- socket I/O operations via asynchronous channelscom.yourkit.probes.builtin.AwtEvents- long AWT/Swing events, which cause UI irresponsiveness. Read more...com.yourkit.probes.builtin.Cassandra- Cassandra database requestscom.yourkit.probes.builtin.ClassLoading- class load and unload events. Read more...com.yourkit.probes.builtin.Databases- JDBC/SQL database connections and requestscom.yourkit.probes.builtin.DirectoryStreams- directory streamscom.yourkit.probes.builtin.Files- file I/O operations via streams, random access files, NIO channelscom.yourkit.probes.builtin.HBase- HBase database requestscom.yourkit.probes.builtin.JNDI- JNDI callscom.yourkit.probes.builtin.JPA_DataNucleus- DataNucleus JPA frameworkcom.yourkit.probes.builtin.JPA_EclipseLink- EclipseLink JPA frameworkcom.yourkit.probes.builtin.JPA_Hibernate- Hibernate JPA frameworkcom.yourkit.probes.builtin.JPA_OpenJPA- OpenJPA JPA frameworkcom.yourkit.probes.builtin.JUnitTests- execution of JUnit testscom.yourkit.probes.builtin.MongoDB- MongoDB requestscom.yourkit.probes.builtin.Processes- external processes launched viaRuntime.exec()andProcessBuilder.start()com.yourkit.probes.builtin.Servlets- JSP/Servlet requestscom.yourkit.probes.builtin.Sockets- socket I/O operations via streams and NIO channelscom.yourkit.probes.builtin.TestNg- execution of TestNG testscom.yourkit.probes.builtin.Threads- thread creation, start, name change. Read more...
Registering built-in probes
Built-in probes are enabled by default. You can change their activity mode or disable them. Read more....
Source code location
Source code of the built-in probes can be found in <Profiler Installation Directory>/probes/src