jvm.mem[Perm Gen]

[Alejandro Valcarcel - ODEC]

Hi,

using zorka 1.0.7, zabbix 2.2.4, jboss7.1.3, sunjdk1.6.0_45

using Template_Zorka_JVM.xml:

<?xml version="1.0" encoding="UTF-8"?>

<zabbix_export>

    <version>2.0</version>

    <date>2013-04-14T04:34:29Z</date>

    <groups>

        <group>

            <name>Templates</name>

        </group>

    </groups>

    <templates>

        <template>

            <template>Template_Zorka_JVM</template>

            <name>Template_Zorka_JVM</name>

...

            <items>

...

<item>

                    <name>Perm Gen utilization</name>

                    <type>0</type>

                    <snmp_community/>

                    <multiplier>0</multiplier>

                    <snmp_oid/>

                    <key>jvm.memutil[&quot;Perm Gen&quot;]</key>

...

In zabbix I'm getting that key:

 jvm.memutil["Perm Gen"]

is not supported by zabbix agent so I have disabled the key ;-)

I see on jvm.bsh:

__jvm() {

...

memutil(name) {

    mem_used = zorka.jmx("java", "java.lang:name="+name+",type=MemoryPool", "Usage", "used");

    mem_max = zorka.jmx("java", "java.lang:name="+name+",type=MemoryPool", "PeakUsage", "max");

    if (mem_used == null || mem_max == null) return null;

    if (mem_used.equals(0L) || mem_max.equals(0L)) return 0.0;

    return 100.0 * mem_used.longValue() / mem_max.longValue();

  }

...

Maybe the combination of template and .bsh are not the correct ones?

I was just wondering, how to read the item. 

[Alejandro Valcarcel - ODEC]

discovered my self:

item name "Template_Zorka_JVM: Perm Gen utilization" using key "jvm.memutil["Perm Gen"]" and it's trigger only works for 32bits jvms :-(

 since my jvms are 64bits only "PS Perm Gen" is avaliable ;-)

Changed the item and trigger and OK. 

https://stackoverflow.com/questions/16664763/ps-perm-gen-perm-gen-jvm-properties/16675835#16675835

[Rafal Lewczuk]

Memory pool names vary depending on which garbage collector implementation is used at the moment. Difference between 32 and 64 bit is really difference between default GC implementations used.

Regarding this particular template, memory pools are detected by zabbix discovery feature and this particular item is there because trigger had to be configured for it. It should really be configurable, so I've replaced "Perm Gen" with macro (which defaults to "Perm Gen"). Change will appear in nearest release.

Regards,
rle