Table of Contents
Beet (from B.T., short for Behavior Tracking) records application metrics as a user (or programmatic agent) interacts with a Spring-based Java application.
No source-level modification is required in the instrumented application; measurement is enabled completely at runtime. Metrics are tied to a specific user and session, and can be collected for servlet requests, Java method calls, and/or SQL statements. Metrics can be stored in various file formats or directly in a relational database. The API is extensible to support other persistence mechanisms and metrics gathering at other layers of an application.
Chapter 2, Justification contains a more detailed discussion of where beet belongs in the broader picture of production monitoring.