On 3/5/2012 3:16 PM, Heiko W.Rupp wrote:
Am 05.03.2012 um 17:58 schrieb Jay Shaughnessy:
> The more I think about it the more I like the idea of a 10 minute Service default.
This gives us a blanket performance enhancement out of box, without, I
> ed intervals less than 5 minutes. I think perhaps the best scenario is a small
number of relevant resources with fairly short intervals, and the rest with larger
intervals.
Importance has (almost) nothing to do with platform/server/service. A datasource may be
much more critical than the process itself.
Platforms with 100days+ uptime kill a lot of stuff when they fail. But a badly written
application can fill up the datasource pool
quickly or fill memory quickly (gc stats are services), while the base java process will
just not die.
I agree and that is why the plugin descriptors should set overrides as
needed. If the component code can perform fast avail checks, and the
resource seems like a critical failure point, then I think the default
interval should be relatively small. And certainly the users can
adjust as they see fit. But the idea here is to allow flexibility while
also being conservative out of box, for the sake of overall agent
performance. The server/service category approach is blunt but it does
give us a way to group most resources (services), with a longer interval
OOB.