Hi Vladimir,
that was exactly what i was searching. Thanks for your help!
The next time I will read more carefully the documentation xD.
José Alejandro
> On 26 Feb 2016, at 15:50, Vladimir Vuksan <vli...@veus.hr> wrote:
>
> Hi Jose,
>
> issue is that JMXAgent is not setting the dmax value which by default will be
> set to 0 aka infinity. I haven't looked at JMXAgent in years so I don't
> really remember if that is possible. See if that is possible.
>
> Vladimir
>
>
> 02/26/2016 u 08:06 AM, José Alejandro Camiño Iglesias je napisao/la:
>> Hi,
>>
>> i am working in a project in whose we use Ganglia and JMXAgent to report
>> some metric of the JMX to the
>> gmetad to analyse the cluster status.
>>
>> We noticed that if the java process that is reporting that metrics died, for
>> example by a OutOfMemory due to the charge on that component,
>> the metric is still live in the gmetad and with the last value that was
>> reported by the gmond.
>>
>> I understand that the JMXAgent report the MBean value to the gmond and where
>> the process die gmond is reporting the last value that
>> was published by the JMXAgent to the gmetad.
>>
>> Exist a form to do that the metric isn't reported or the value be a
>> predefined value (void, 0, -1 or similar)?
>>
>> Thanks,
>>
>
signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general
