Open Stack

Hi ,

 Just to reframe my query:
  I have a meter subscription m1.* for publisher p1 and I need a subset of m1.*  notifications for ex:m1.xyz.* for publisher p2.
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.

To avoid this we had the following entry in pipeline;

sources:
      -name : m1meter
       meters: m1.*,!m1.xyz.*
       sinks:
            -m1sink           
       .........
      -name : m2meter
       meters:m1.xyz.*
       sinks:
            -m2sink
sinks:
     -name: m1sink
      publishers:
               -p1
               
      -name: m2sink
      publishers:
               -p1
               -p2
 
>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.
If we do code modification in pipeline module of ceilometer does it effects any other parts of ceilometer frame work.


Thanks and Regards
Raghunath.


Copied reply mail content from http://osdir.com/ml/openstack-dev/2016-01/msg01346.html for reference, due to some reason I am not getting reply mail to my mailbox.
-------------------------------------Copied Mail Start here---------------------------------------------------------------------------------------------------------
hi,

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.

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.

as it stands now. you'll need to explicitly list out the meters you want (or don't want) sent to each pipeline.

cheers,
gord.
-----------------------------------------Mail End Here-----------------------------------------------------------------------------------------------------

With Best Regards
Raghunath Dudyala
Tata Consultancy Services Limited
Mailto: raghunath.d at tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________



-----Raghunath D/HYD/TCS wrote: ----- 
To: openstack-dev at lists.openstack.org
From: Raghunath D/HYD/TCS
Date: 01/20/2016 07:09PM
Cc: "Srikanth Vavilapalli" <srikanth.vavilapalli at ericsson.com>
Subject: [openstack-dev] [ceilometer] :Regarding wild card configuration in pipeline.yaml


Hi ,
 
We have one use-case for which we are using ceilometer for getting notifications.
 
We have meter's m1.*,m1.xyz.* and publishers(kafka/udp) as p1 and p2.
i.m1.* notifications/meter data should send to p1 and p2
ii.m1.xyz.* notifications/meter data should send to p1.

We can correlate m1.* as network.* and m1.xyz.* as network.incoming.*
The pipeline.yaml is updated as:
----------------------------------------------------------------------------------
sources:
      -name : m1meter
       meters: m1.*,m1.xyz.*
       sinks:
            -m1sink           

sinks:
     -name: m1sink
      publishers:
               -p1
               -p2
            
------------------------------------------------------------------------------------
With the above configuration p1 also receives other than m1.xyz.* notifications
which are not subscribed by p1.To avoid this duplication's,pipeline.yaml is updates as:
-------------------------------------------------------------------------------------
sources:
      -name : m1meter
       meters: m1.*,!m1.xyz.*
       sinks:
            -m1sink           
       .........
      -name : m2meter
       meters:m1.xyz.*
       sinks:
            -m2sink
sinks:
     -name: m1sink
      publishers:
               -p1
               -p2
             
     -name: m2sink
      publishers:
               -p1
----------------------------------------------------------------------------------------              
This configuration is failing under source rule checking with reason "both included and
excluded meters specified.

Info/Help needed:
  Do we have any way in ceilometer frame work to achieve this or could you provide 
us some suggestions how to achieve this in ceilometer.
 
With Best Regards
Raghunath Dudyala
Tata Consultancy Services Limited
Mailto: raghunath.d at tcs.com
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160121/3ee5c173/attachment.html>