Hi Witek, Thank you for your response, it was really helpful. I was trying to figure out what are the next steps in the sporadics metrics side and you've made them more clear now. I'll report to my team so we can start the work. :)
Best regards, Erickson Santos. ----- Mensagem original ----- De: "Witek Bedyk" <witold.be...@est.fujitsu.com> Para: "Erickson" <erick...@lsd.ufcg.edu.br>, openstack-dev@lists.openstack.org Enviadas: Sexta-feira, 13 de maio de 2016 12:44:33 Assunto: [Monasca] Sporadic metrics Hi Erickson, thanks for your interest in our project and sorry for replying so late. We are happy that you're willing to contribute to the development of sporadic metrics. The incentive for this development is to introduce the possibility to create alarms in Monasca based on event like metrics. E.g. A metric is generated every time when an error in the given log-file appears. Such metric is different from the standard Monasca metric in the way that it does not appear on the regular, periodic basis. You can read a little more about it here [1], but the blueprint itself is outdated and the implementation changed. The main logic for alarm creation has been moved to "deterministic_alarm" topic [2] and Tomasz works currently on that. Your reviews are very welcome. The changes in "sporadic_metric" topic [3] are meant to give the user information that a given metric is of sporadic (non-periodic) character. It will have no influence on monasca-thresh. Tomasz has put the code that he already had in this topic but he must focus on "deterministic_alarm" now, so please feel free to submit your patch-sets if you want. Apart from the existing changes also changes in monasca-ui and python-monascaclient repos are needed to display the 'sporadic' attribute of the metric for the user. You could compare this change in monasca-ui [4]. If you have questions to the implementation of "sporadic metrics", I think the existing changes in gerrit [3] are the best place for exchange and communication at the moment. Actually I should have updated the blueprint for that. Sorry, my fault. So, have fun with the code :) Cheers Witek [1] https://blueprints.launchpad.net/monasca/+spec/alarmsonlogs [2] https://review.openstack.org/#/q/topic:deterministic_alarm [3] https://review.openstack.org/#/q/topic:sporadic_metric [4] https://review.openstack.org/#/c/314420/3/monitoring/alarmdefs/templates/alarmdefs/_detail.html P.S. Please note, I will be in holidays for the next two weeks. -- FUJITSU Enabling Software Technology GmbH Schwanthalerstr. 75a, 80336 München Telefon: +49 89 360908-547 Telefax: +49 89 360908-8547 COINS: 7941-6547 Sitz der Gesellschaft: München AG München, HRB 143325 Geschäftsführer: Dr. Yuji Takada, Hans-Dieter Gatzka __________________________________________________________________________ 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