<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<font face="Calibri">Hi Anton,<br>
<br>
Thanks for investigating this new feature (and new project). In
fact, Lucas's examples are so new I haven't had a chance yet to go
through them in detail, hopefully today. Let me just try and
answer this now and possibly revise the examples when I get a
chance to review.<br>
<br>
With 0.6.0 a client can insert Events via a REST endpoint. All of
the send-events*.sh examples are doing this. They will be
persisted and can optionally specify a 'DataId' (more on that in a
moment). Also, Triggers can now generate an Alert or an Event,
so Events can be generated when a Trigger's conditions are
satisfied. A Trigger specifies one or more Conditions, of which
there are several types: Threshold numeric conditions, Range
numeric conditions, String comparison conditions, etc.
Conditions are evaluated against Data being sent into the alerting
engine (via REST). A Condition specifies a DataId and then
evaluates against all the datums with that same DataId.<br>
<br>
Now, starting in 0.6.0 there is a new condition type,
EventCondition. The datums for this kind of condition are Events
(as opposed to numeric for ThresholdCondition, and strings for
StringCondition, for example). So, if an Event comes via REST
API, or is generated by a Trigger, and it specifies a DataId, it
will then be used for evaluation of any EventCondition with that
DataId. For example:<br>
<br>
Trigger DeploymentFailed<br>
EventCondition {dataId: "deployer", expression: "text contains 'failed'"}<br>
--><br>
Create Alert<br>
<br>
The Condition itself is connected to the Trigger via the
triggerId. Because conditions are owned by a Trigger the
triggerId is actually a path-variable on the post REST endpoint.
Perhaps that is what you were looking for? The same approach is
true when specifying Dampening for a Trigger.<br>
<br>
-Jay<br>
</font><br>
<div class="moz-cite-prefix">On 11/13/2015 9:04 AM, Anton Hughes
wrote:<br>
</div>
<blockquote
cite="mid:CAMOUzMD7CRNCRJQ=vT6bOOE0kenJfd0nGx=QEWPLEeEw-ePVRA@mail.gmail.com"
type="cite">
<div dir="ltr">Hi all
<div><br>
</div>
<div>I have been studying <a moz-do-not-send="true"
href="https://github.com/lucasponce/hawkular-examples/tree/master/events"
target="_blank">https://github.com/lucasponce/hawkular-examples/tree/master/events</a>
- and I have a question.</div>
<div><br>
</div>
<div>In the example documentation, I cannot see how an trigger
and conditions are related. I would expect there to be some
reference between these objects.</div>
<div><br>
</div>
<div>Thanks</div>
<div><br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">Anton Hughes
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
hawkular-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/hawkular-dev">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>