Inspired by the great work done by the Spring team with TC Server and Spring Insight, spring4speedtracer brings similar functionality to any Spring project without the need to run in TC Server. For example, any Java project using Spring can use spring4speedtracer to enable access to every Spring bean method invocation made during an HTTP request and then view those metrics alongside the existing client data available in Speed Tracer.

The most notable difference between spring4speedtracer and TC Server is that spring4speedtracer performs instrumentation via proxies using AspectJ through basic Spring configuration and a filter rather than relying on the container to do it with custom deployers. This makes the metrics available when the application runs in any container such as JBoss, Glassfish, Jetty, or vanilla Tomcat and is especially useful for applications where running in TC Server is either impossible (the application requires features not present in TC Server) or unrealistic (the TC Server environment would differ significantly from the real environment where performance problems exist).

See the QuickStartGuide for an overview of how to enable spring4speedtracer in your project.

You may also wish to view the current list of TracedComponents and FrequentlyAskedQuestions.

NEW! Version 0.0.6 is available! Check out the ReleaseNotes.