Yes, you are right. I have quite a few scenarios where beyond the indicator that something is wrong, that the healthcheck provides me, I need to capture a value that to represent the scale of the problem. So that I can have analysis. I was hoping to have the option to provide that as part of the healthcheck rather than writing two separate things. :)
All good. -----Original Message----- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Tuesday, January 31, 2017 11:59 AM To: users <users@sling.apache.org> Subject: Re: Sling Health Checks Hi, On Tue, Jan 31, 2017 at 4:59 PM, Jason Bailey <jason.bai...@sas.com> wrote: > ...We have an AppDynamics instance that we use to monitor the state of our > instances as much as possible... > ...If the number of submissions each instance is handling falls below > a certain threshold or increases beyond a certain number, it's an > issue of concern, a warning. But certain days and a particular time, it's a > situation where need someone looking at it immediately... Isn't this a case for an MBean that just reports the number of submissions, and a health check that checks that they are within range, maybe based on days and times? I think that would work with our standard health checks modules. -Bertrand
