[openstack-dev] [Monasca] alarms based on events

Hochmuth, Roland M roland.hochmuth at hpe.com
Fri Jan 22 18:31:07 UTC 2016

Hi Prema, I assumed that the component that is translating and sending to the Monasca API would be sending metrics periodically. If that isn't the case, then support for non-periodic metrics would need to be added.

Sorry, I should heave realized this in my previous response.

I don't think it would be difficult to add support for non-periodic metrics/alarms. There are a couple of approaches we could take, so a design discussion would be good to have if you are interested in implementing this. This is feature that we are not working on right now, but it is on our list to implement in the near future.

Regards --Roland

From: Premysl Kouril <premysl.kouril at gmail.com<mailto:premysl.kouril at gmail.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Friday, January 22, 2016 at 7:06 AM
To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [Monasca] alarms based on events

Hi Roland,

I had a chat with people on IRC about it and I understood that in order for my use case to work the Monasca software needs to implement "non-periodic" metrics (because the monitored box sends out the event only on health change and not periodicaly) and I understood that this enhancement is currently being designed.

Is that correct?


On 22 Jan 2016 01:04, "Hochmuth, Roland M" <roland.hochmuth at hpe.com<mailto:roland.hochmuth at hpe.com>> wrote:
Hi Prema, SNMP isn't handled in Monasca and I have little experience in
that area. This would be new development.

It is possible to map binary data, such as health/status of a system or
component. The usual way is to use the value 0 for up/OK and 1 for
down/NOT_OK. A component would need to be developed to handle SNMP traps,
then translate and send them to the Monasca API as binary data. Possibly,
this component could be added to the Agent.

Using the Monasca Alarm API, an alarm could be defined, such as
max(snmp{}) > 0.

The latency for a min/max alarm expression in Monasca is very low.

Regards --Roland

On 1/18/16, 9:07 AM, "Premysl Kouril" <premysl.kouril at gmail.com<mailto:premysl.kouril at gmail.com>> wrote:

>we are just evaluating Monasca for our new cloud infrastructure and I
>would like to ask if there are any possibilities in current Monasca or
>some development plans to address following use case:
>We have a box which we need to monitor and when something goes wrong
>with the box, it sends out and SNMP trap indicating that it is in bad
>condition and when the box is fixed it sends out SNMP trap indicating
>that it is OK and operational again (in other words: the box is
>indicating health state transitions by sending events - in this case
>SNMP traps).
>Is it possible in Monasca to define such alarm which would work on top
>of such events? In other words - Is it possible to have a Monasca
>alarm which would go red on some external event go back green on some
>other external event? By alarm I really mean a stateful entity in
>monasca database not some notification to administrator.
>Best regards.
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>

More information about the OpenStack-dev mailing list