Open Stack

Thanks, Roland. Makes sense. I agree.


Just tossing the idea: is there a way to validate a temporal causal
relationship among events such that in case e1, followed by e2, followed by
e3 *implies *a condition C to fail/pass - and generates an alarm.


Thanks,
Pradip



On Tue, Feb 16, 2016 at 8:52 PM, Hochmuth, Roland M <roland.hochmuth at hpe.com
> wrote:

> Hi Pradip, The focus of that blueprint is to create metrics from logs in
> the LogStash component and then publish them to the Kafka metrics topic.
> The Monasca Threshold Engine can then be used to alarm on the metrics. For
> example, if the number of errors in a log file exceeds some amount, alarm
> and send a notification.
>
> Regards --Roland
>
> From: Pradip Mukhopadhyay <pradip.interra at gmail.com<mailto:
> pradip.interra at gmail.com>>
> Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:
> openstack-dev at lists.openstack.org>>
> Date: Monday, February 15, 2016 at 9:58 AM
> To: OpenStack List <openstack-dev at lists.openstack.org<mailto:
> openstack-dev at lists.openstack.org>>
> Subject: [openstack-dev] [Monasca] Alarm generation from a sequence of
> events
>
> Hello,
>
>
> We come across the following interesting BP in the last weekly meeting:
> https://blueprints.launchpad.net/monasca/+spec/alarmsonlogs
>
>
> Understood how the non-periodic nature of log events to be taken care of
> (by introducing period = -1 in value-meta).
>
>
> Just wondering can it be possible to use this to satisfy the following
> usecase:
> Given a causal or non-causal sequence of events a, b, c – can we determine
> that a condition ‘p’ has occurred and alarm on that.
>
>
>
> Thanks,
> Pradip
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160216/026e38cc/attachment.html>