RootCause is a powerful and flexible tool for instrumenting software applications
in the post-development environment. With RootCause, you can pinpoint performance bottlenecks,
track down memory leaks, and resolve
bugs in complex software applications faster.
When you can't use development tools because their
overhead is too high, try RootCause. RootCause is
highly non-invasive, perfect for resolving problems that are discovered
during integration or after the application has been deployed.
Why RootCause is Different
CONTROL Create your own instrumentation, specific to
your application or to the problem you are trying to solve. The
instrumentation is accomplished with probes that are written in standard
C or Java, making them easy to build.
You can enable, modify, or disable probes
dynamically, in real time, as the application runs. The
instrumentation is inserted as the application executes, so there are no changes to
any application files stored on disk.
POWER RootCause takes you deeper into your application
to capture information other tools cant reach.
Since RootCause does not require access to source or
compiled code, it can instrument third-party applications, including
shared libraries, Java Virtual Machines, application servers, and
dynamic components. RootCause also crosses JNI boundaries to
instrument legacy code. You can capture information on all the
components of your application.
PRECISION The longer your application runs with the RootCause probes,
the closer you get to pinpointing the exact section of code that is causing
What data can you obtain with RootCause?
Read how SAS uses RootCause.
Read about Aprobe, the software instrumentation technology upon
which RootCause is built.