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: raghunat...@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
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev