Remove the moving-average requirement. about tattle HOT 3 CLOSED

I think there are some graphite functions you can use. The day problem seems unique to your case, I suspect it's a storage schema issue.

Sent from my iPhone. Thanks Steve.

On Dec 15, 2012, at 3:46 PM, John Gietzen [email protected] wrote:

We are using graphite to track an error bucket of sorts.

We need to get alerts anytime this bucket has more than zero items in in.

There are several issues with Graphite-Tattle that prevent us from doing this effectively:

1. We are unable to turn off moving averages (aside from using a single sample).
2. We are unable to tell Graphite-Tattle to look at a shorter window than 1 day. When looking at a 1 day window, the values are averaged.
3. We don't want separate error or warning thresholds here (but we can use 0.5 for warnings as a workaround).

Thoughts?

—
Reply to this email directly or view it on GitHub.

from tattle.

Scratch #2, I was mistaken. However, I have opened #34 to describe the weirdness that we were encountering there.

from tattle.

movingAverage() can now be disabled by setting "sample size" threshold check field to 1

"now" means merged in master since a few minutes

from tattle.