Re: DEA Monitoring Capabilities


Jim CF Campbell
 

Looks like the Runtime team took some out in v234, added them back in in
v235.

From the Runtime Slack:




On Fri, May 20, 2016 at 11:47 AM, Jim CF Campbell <jcampbell(a)pivotal.io>
wrote:

Yep, I've had a back thread with Runtime OG who now has the DEA metrics
and who I thought had implemented all previous /varz (aka Collector)
metrics into the firehose. No answer from Mr Fraenkel yet.

On Fri, May 20, 2016 at 11:15 AM, Voelz, Marco <marco.voelz(a)sap.com>
wrote:

Including Jim Campbell to make sure this reaches him.



On 20/05/16 13:41, "Chawki, Amin" <amin.chawki(a)sap.com> wrote:



Hi,



by upgrading to CF v234 (including pre-release v232) we lost all our
monitoring capabilities regarding DEA and HM9000 (we were still using
Collector). By migrating to Firehose only a fraction of the metrics was
available. Very important metrics for our productive systems like
‘available_memory_ratio’ were just added in CF v235. In the meantime, we
were pretty much “flying blind”.



We replaced not existing metrics like ‘DEA…mem_used_bytes’ and
‘HM9000…healthy’, which were available via Collector, with metrics from
Bosh. Is this the way to go or are there any plans to add them again?



Best Regards,

Amin






--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963


--
Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.