As a zabbix freeloader I have no support, but I fund something you guys might want to fine tune in the future.
Here is someone else's blog post explaining the problem: https://blog.svedr.in/posts/problem-...ting-mode.html
Basically, zabbix java monitoring will complain if more effort is spent on major garbage collections than on minor collections.
Most of the time this is a sane policy, except if you have a really boring service: If you have less than 1 collection each minute, you'll of course get 1 major collection and 0 minor collections once in a while, even if the last 10 minutes had 0 major collections and 1 minor collection. We have this problem outside our business hours.
The blog post fine tunes the trigger for this situation, but only for the ParNew collection, by requiring a minimum of effort before triggering. I propose adapting the Template App Generic Java JMX for each firefighting mode trigger.
Here is someone else's blog post explaining the problem: https://blog.svedr.in/posts/problem-...ting-mode.html
Basically, zabbix java monitoring will complain if more effort is spent on major garbage collections than on minor collections.
Most of the time this is a sane policy, except if you have a really boring service: If you have less than 1 collection each minute, you'll of course get 1 major collection and 0 minor collections once in a while, even if the last 10 minutes had 0 major collections and 1 minor collection. We have this problem outside our business hours.
The blog post fine tunes the trigger for this situation, but only for the ParNew collection, by requiring a minimum of effort before triggering. I propose adapting the Template App Generic Java JMX for each firefighting mode trigger.
Comment