CMD Checks need to be setup by play books about rpc-maas HOT 5 CLOSED

@B3RNARD0 @cloudnull since there aren't scripts to be written for this, and this is entirely done by raxmon, should this actually be moved to rcbops/ansible-lxc-rpc?

from rpc-maas.

I believe this is already done: rcbops/ansible-lxc-rpc#306

I'm assuming that there is no data because there are no installs pushing data upstream yet. The change is in 9.0.1, wasn't in 9.0.0.

from rpc-maas.

@andymcc I think what I actually mean is that we are not collecting all the CMD metrics that the agent is capable of collecting? If I look at CPU metrics available in my cloud account, I see:
Idle % Avg
Interrupt - Average
Kernel Process - Average
Max Usage
Min Usage
Stolen - Average
Usage Average
User Mode - Average
Wait State - Average

Similar situation for disk and memory. I would like to collect all of these metrics as I believe they are built into the agent.

from rpc-maas.

@B3RNARD0 can we get this added to the backlog please

@russwclark can you provide detailed information about exactly what is required, as input to the story? If alarms are needed, we need thresholds, alert types etc per metric.

from rpc-maas.

This is actually an invalid issue. After @andymcc and @russwclark spoke, it appears that the problem was that in fact the playbook to set up the CDM checks had not been run.

from rpc-maas.