Hi, On Wed, Nov 27, 2013 at 12:47 AM, Jörg Hoh <[email protected]> wrote: > I have a question to the reasoning behind the timeseries entries available > in Jackrabbit for a number of relevant operational parameters, which are > suitable to monitor. > > Basically I don't see a reason, why you would have time entries instead of > just a single ever-increasing value. Any monitoring system is capable to > handle these and calculate the delta between the current value and the last > one. Even the most simple RRD tool can do that.
We often see cases where a deployment doesn't come with a pre-configured monitoring system, which makes it difficult or impossible to investigate past performance of the system. The TimeSeries mechanism makes it possible to get an overview of the measured variables since the last restart of a repository for up to three years, which in many cases is quite useful and would be impossible to get with a just plain counter. > I don't see a real good usecase to have timeseries entries and would like > to have the raw data (as 64bit longs) as I am much more flexible then. It's still possible for you to sample the value from the array returned by getValuePerSecond(). Alternatively, if you want to poll at finer than per-second granularity, you could submit a patch that exposes the internal counter variable of the TimeSeriesRecorded class. BR, Jukka Zitting
