<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    hi,<br>
    <br>
    i don't completely recall why we don't allow wildcarded exclude and
    include meters. it's probably because there's ambiguity of ordering
    of wildcard which can lead to different filter results.<br>
    <br>
    someone can correct me, but i don't think there's a strict
    requirement that stops us from supporting both at once, just that
    it's not there.<br>
    <br>
    as it stands now. you'll need to explicitly list out the meters you
    want (or don't want) sent to each pipeline.<br>
    <br>
    cheers,<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 20/01/2016 8:39 AM, Raghunath D
      wrote:<br>
    </div>
    <blockquote
cite="mid:OF71FD4EDB.95CE0BEB-ON65257F40.004A7F98-65257F40.004B0B71@tcs.com"
      type="cite"><font size="2" face="Default Sans
        Serif,Verdana,Arial,Helvetica,sans-serif">
        <div>Hi ,</div>
        <div> </div>
        <div>We have one use-case for which we are using ceilometer for
          getting notifications.</div>
        <div> </div>
        <div>We have meter's m1.*,m1.xyz.* and publishers(kafka/udp) as
          p1 and p2.</div>
        <div>i.m1.* notifications/meter data should send to p1 and p2<br>
          ii.m1.xyz.* notifications/meter data should send to p1.</div>
        <div><br>
          We can correlate m1.* as network.* and m1.xyz.* as
          network.incoming.*</div>
        <div>The pipeline.yaml is updated as:<br>
----------------------------------------------------------------------------------<br>
          sources:<br>
                -name : m1meter<br>
                 meters: m1.*,m1.xyz.*<br>
                 sinks:<br>
                      -m1sink           </div>
        <div><br>
          sinks:<br>
               -name: m1sink<br>
                publishers:<br>
                         -p1<br>
                         -p2<br>
                      <br>
------------------------------------------------------------------------------------</div>
        <div>With the above configuration p1 also receives other than
          m1.xyz.* notifications<br>
          which are not subscribed by p1.To avoid this
          duplication's,pipeline.yaml is updates as:<br>
-------------------------------------------------------------------------------------<br>
          sources:<br>
                -name : m1meter<br>
                 meters: m1.*,!m1.xyz.*<br>
                 sinks:<br>
                      -m1sink           </div>
        <div>       .........<br>
                -name : m2meter<br>
                 meters:m1.xyz.*<br>
                 sinks:<br>
                      -m2sink</div>
        <div>sinks:<br>
               -name: m1sink<br>
                publishers:<br>
                         -p1<br>
                         -p2<br>
                       <br>
               -name: m2sink<br>
                publishers:<br>
                         -p1<br>
          ----------------------------------------------------------------------------------------             
        </div>
        <div>This configuration is failing under source rule checking
          with reason "both included and<br>
          excluded meters specified.</div>
        <div><br>
          <strong>Info/Help needed:</strong></div>
        <div>  Do we have any way in ceilometer frame work to achieve
          this or could you provide <br>
          us some suggestions how to achieve this in ceilometer.</div>
        <div> <br>
          <font size="2">With Best Regards<br>
            <font size="2">Raghunath</font></font><font size="2">
            Dudyala<br>
            <font size="2">Tata</font></font><font size="2"> Consultancy
            Services Limited<br>
            <font size="2">Mailto</font></font><font size="2">:
            <a class="moz-txt-link-abbreviated" href="mailto:raghunath.d@tcs.com">raghunath.d@tcs.com</a><br>
          </font><font size="2">Website: <a moz-do-not-send="true"
              href="http://www.tcs.com/">http://www.tcs.com</a><br>
          </font><font size="2">____________________________________________<br>
          </font><font size="2">Experience certainty. IT Services<br>
          </font><font size="2">Business Solutions<br>
          </font><font size="2">Consulting<br>
          </font><font size="2">____________________________________________<br>
          </font></div>
      </font>
      <p>=====-----=====-----=====<br>
        Notice: The information contained in this e-mail<br>
        message and/or attachments to it may contain <br>
        confidential or privileged information. If you are <br>
        not the intended recipient, any dissemination, use, <br>
        review, distribution, printing or copying of the <br>
        information contained in this e-mail message <br>
        and/or attachments to it are strictly prohibited. If <br>
        you have received this communication in error, <br>
        please notify us by reply e-mail or telephone and <br>
        immediately and permanently delete the message <br>
        and any attachments. Thank you</p>
      <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>
    <pre class="moz-signature" cols="72">-- 
gord</pre>
  </body>
</html>