<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><DIV>Hi ,</DIV>
<DIV> </DIV>
<DIV> Just to reframe my query:</DIV>
<DIV> I have a meter subscription m1.* for publisher p1 and I need a subset of m1.* notifications for ex:m1.xyz.* for publisher p2.</DIV>
<DIV>If we add p2 to already exisiting sink along with p1, p2 will get other notification's along with m1.xyz.* which are not needed for p2.</DIV>
<DIV> </DIV>
<DIV>To avoid this we had the following entry in pipeline;</DIV>
<DIV><BR>sources:<BR> -name : m1meter<BR> meters: m1.*,!m1.xyz.*<BR> sinks:<BR> -m1sink <BR> .........<BR> -name : m2meter<BR> meters:m1.xyz.*<BR> sinks:<BR> -m2sink<BR>sinks:<BR> -name: m1sink<BR> publishers:<BR> -p1<BR> <BR> -name: m2sink<BR> publishers:<BR> -p1<BR> -p2<BR> <BR>From reply mail it seems there is no strict restriction to support this.Could you please let me know how should we handle such cases in ceilometer.</DIV>
<DIV>If we do code modification in pipeline module of ceilometer does it effects any other parts of ceilometer frame work.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Thanks and Regards</DIV>
<DIV>Raghunath.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Copied reply mail content from <A href="http://osdir.com/ml/openstack-dev/2016-01/msg01346.html">http://osdir.com/ml/openstack-dev/2016-01/msg01346.html</A> for reference, due to some reason I am not getting reply mail to my mailbox.</DIV>
<DIV>-------------------------------------Copied Mail Start here---------------------------------------------------------------------------------------------------------</DIV>
<DIV>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,</DIV>
<DIV>gord.</DIV>
<DIV>-----------------------------------------Mail End Here-----------------------------------------------------------------------------------------------------</DIV>
<DIV><BR><FONT size=2>With Best Regards<BR></FONT><FONT size=2>Raghunath Dudyala<BR></FONT><FONT size=2>Tata Consultancy Services Limited<BR></FONT><FONT size=2>Mailto: raghunath.d@tcs.com<BR></FONT><FONT size=2>Website: <A 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></DIV></FONT><BR><BR><FONT color=#990099>-----Raghunath D/HYD/TCS wrote: -----</FONT>
<DIV style="PADDING-LEFT: 5px" class=iNotesHistory>
<DIV style="BORDER-LEFT: black 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">To: openstack-dev@lists.openstack.org<BR>From: Raghunath D/HYD/TCS<BR>Date: 01/20/2016 07:09PM<BR>Cc: "Srikanth Vavilapalli" <srikanth.vavilapalli@ericsson.com><BR>Subject: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml<BR><BR><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>: raghunath.d@tcs.com<BR></FONT><FONT size=2>Website: <A 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></DIV></FONT>
<DIV></DIV></FONT></DIV></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>
<p></p>