<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi, <br>
    <br>
    Maybe the event transformer is needed in some use cases to generate
    new events or do transformations like the samples handling.  but for
    this timeout event alarming requirement,  the 'timeout' of alarms
    will be various, it not a good idea of changing event_pipeline.yaml
    to generate new events based on events timeout when we need an
    event-timeout alarm. and also, the access of event pipeline
    definitions to users is inadvisable. I personally think it'd better
    to implement the second option and based on Ryota's proposal.<br>
    <br>
    Best Regards<br>
    Liusheng<br>
    <br>
    <div class="moz-cite-prefix">在 2015/8/5 3:36, gord chung 写道:<br>
    </div>
    <blockquote
      cite="mid:BLU436-SMTP69343B50D0633B4CC3F3F7DE760@phx.gbl"
      type="cite">
      <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
      hi Igor,<br>
      <br>
      i would suggest you go with second option as i believe your
      implementation will overlap and reuse some of the functionality
      Ryota would code for his alarm spec [1]. also, since Aodh is
      working on an independent release cycle, it'll give you some more
      time as i don't think we'd be able to get this into Liberty if we
      went the pipeline route.<br>
      <br>
      [1]
      <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://specs.openstack.org/openstack/ceilometer-specs/specs/liberty/event-alarm-evaluator.html">http://specs.openstack.org/openstack/ceilometer-specs/specs/liberty/event-alarm-evaluator.html</a><br>
      <br>
      <div class="moz-cite-prefix">On 04/08/2015 10:00 AM, Igor
        Degtiarov wrote:<br>
      </div>
      <blockquote
cite="mid:CAB68rD9x-hJfO=dAU5YXJSsskUO+gxPx7eTdPHgo2OzfsWbSTA@mail.gmail.com"
        type="cite">
        <div dir="ltr">
          <div>
            <div>
              <div>
                <div>
                  <div>Hi folks,<br>
                    <br>
                  </div>
                  On our meatup we agreed to add timeout event alarms
                  [1](Event-Base Alarming part). <br>
                  In ToDo task "Сhoose the optimal way for timeout
                  alerting implementation"<br>
                </div>
                Now we have two proposition for implementation:<br>
              </div>
               - first is to add timeout param in event pipeline
              (transformer part) [2]    <br>
                 -- weakness of this approach is that we cannot allow
              user change config files, so only administrator will be
              able to set rules for timeout events alarms, and that is
              not what we are expecting from alarms.<br>
            </div>
          </div>
           - second is additional optional parameters in event alarms
          description like sequence of required events and timeout
          threshold. Event alarm evaluator looks thru getting events and
          evaluates alarm if even one event from required sequence isn't
          received in set "timeout".[3]<br>
          <div>
            <div>
              <div>
                <div>
                  <div><br>
                  </div>
                  <div>It seems that second approach is better it
                    doesn't have restrictions for end user.<br>
                  </div>
                  <div>
                    <div>
                      <div>
                        <div>Hope for your help in choosing optimal way
                          for implementation. <br>
                          (In specs review there is silence now)<br>
                        </div>
                        <div><br>
                          [1] <a moz-do-not-send="true"
href="https://wiki.openstack.org/wiki/Meetings/Ceilometer/Liberty_Virtual_Mid-Cycle">https://wiki.openstack.org/wiki/Meetings/Ceilometer/Liberty_Virtual_Mid-Cycle</a><br>
                          [2] <a moz-do-not-send="true"
                            href="https://review.openstack.org/#/c/162167">https://review.openstack.org/#/c/162167</a><br>
                          [3] <a moz-do-not-send="true"
                            href="https://review.openstack.org/#/c/199005">https://review.openstack.org/#/c/199005</a><br>
                          <br clear="all">
                          <div>
                            <div class="gmail_signature">Igor Degtiarov<br>
                              Software Engineer<br>
                              Mirantis Inc.<br>
                              <a moz-do-not-send="true"
                                href="http://www.mirantis.com"
                                target="_blank">www.mirantis.com</a></div>
                          </div>
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
      </blockquote>
      <br>
      <pre class="moz-signature" cols="72">-- 
--
gord</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>