Open Stack

Hi,

Let us know if you have any question, we will be happy to help.

Br,
Ifat


On Fri, Apr 12, 2019 at 4:14 PM <hoanq13 at viettel.com.vn> wrote:

> Hi,
> Now I try write new datasource  kapacitor to vitrage, storyboard :
> https://storyboard.openstack.org/#!/story/2005428
> I will greatly appreciate with your help.
>
>
> ------------------------------
> *From: *ifatafekn at gmail.com
> *To: *hoanq13 at viettel.com.vn, openstack-discuss at lists.openstack.org
> *Sent: *Monday, April 8, 2019 5:54:30 PM
> *Subject: *Re: [Vitrage] Find solution on integrate vitrage to current
> monitor
>
> Hi,
>
> If I understand correctly, InfluxDB is used for storing metrics, but it
> does not handle the logic of when to raise an alarm, so integrating with it
> will not help you. I'm not familiar with any tool that "converts" InfluxDB
> metrics to alarms that are sent to Vitrage.
>
> I think that the only way to integrate your alarms is to write a new
> datasource for Kapacitor, since this specific monitor is not supported yet
> in Vitrage. You can find details on how to write a new datasource here [1].
>
> [1]
> https://docs.openstack.org/vitrage/latest/contributor/add-new-datasource.html
>
> Best regards,
> Ifat
>
> On Thu, Apr 4, 2019 at 6:00 AM <hoanq13 at viettel.com.vn> wrote:
>
>> Hi,
>>
>> I sent this mail for finding solution when integrate  vitrage to my
>> current monitor system.
>> I my system we use Tick stack monitor: with telegraf is collector metric,
>> influxdb for storing metric, and kapacitor for alarming.
>> It been work for a long while, all our monitor data in influxdb. I'm
>> wondering  have any tool can read influxdb, create alarm so vitrage can get
>> input alarm from it?.
>> Or any ideal you can recommend me on integrate vitrage to my system?
>>
>> p/s: i was think about write datasource driver kapacitor can alarm
>> vitrage, but it take time, and I'm not good at codding.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190414/038bae9d/attachment.html>