+1. I think the best approach would be a mix of 1, 2 and 3, i.e. pulling specific metrics such as memory load / usage which will be useful to spin up nodes through policies. Then we could pull the full map of metrics per component which will avoid to have 100+ sensors.
I like the idea of 4 but I'm not sure if it's possible. Best. On Wed, 26 Aug 2015 at 11:55 Duncan Grant <[email protected]> wrote: > I would like to be able to add policies to a brooklyn-ambari blueprint that > can react to ambari metrics e.g. to add extra nodes when load reaches a set > level. To do this I need sensors that read the metrics provided by Ambari. > > Ambari provides a lot of metrics per deployed component and I'm not sure > what the best brooklyn practice to make these available would be. I think > the following are all possibilities: > 1) On AmbariServer entity dynamically add a sensor for each individual > metric but this would mean adding a couple of hundred sensors. > 2) On AmbariServer entity dynamically add a sensor for each component's > metrics with a value of type map. I'm not sure if this is possible or how > easy it would then be to add a policy based on the value of items in the > map. > 3) Create a few specific sensors that will read specific values. If > someone needs more then they would need to extend java. > 4) Create a generic Enricher that can be added in yaml and can be > configured to dynamically add a sensor for a specific metric. I think this > should be possible but would require some sort of json path value to direct > it to the correct metric. > > Does anyone have any advice on the best approach here? > > Regards > > Duncan > > -- > Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. > Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP > > This e-mail message is confidential and for use by the addressee only. If > the message is received by anyone other than the addressee, please return > the message to the sender by replying to it and then delete the message > from your computer. Internet e-mails are not necessarily secure. Cloudsoft > Corporation Limited does not accept responsibility for changes made to this > message after it was sent. > > Whilst all reasonable care has been taken to avoid the transmission of > viruses, it is the responsibility of the recipient to ensure that the > onward transmission, opening or use of this message and any attachments > will not adversely affect its systems or data. No responsibility is > accepted by Cloudsoft Corporation Limited in this regard and the recipient > should carry out such virus and other checks as it considers appropriate. > -- Thomas Bouron • Software Engineer @ Cloudsoft Corporation • http://www.cloudsoftcorp.com/ Github: https://github.com/tbouron Twitter: https://twitter.com/eltibouron -- Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. Cloudsoft Corporation Limited does not accept responsibility for changes made to this message after it was sent. Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by Cloudsoft Corporation Limited in this regard and the recipient should carry out such virus and other checks as it considers appropriate.
