[openstack-dev] [vitrage] Vitrage was migrated to StoryBoard

Hi, During the weekend we have completed the Vitrage migration to StoryBoard. Vitrage bugs and blueprints should be handled in StoryBoard from now on. All Vitrage bugs have been migrated and have the same bug number as in launchpad. Regarding the blueprints, we migrated the ones that we are

Re: [openstack-dev] [Vitrage] naming issues

Hi, Can you please send me your nagios_conf file, and the logs of vitrage-collector and vitrage-graph? I’ll have a look. Thanks, Ifat On Thu, Jun 21, 2018 at 5:08 PM, Rafal Zielinski < rafal.zielin...@linguamatics.com> wrote: > Hello, > > As suggested by eyalb on irc I am posting my problem

[openstack-dev] [Vitrage][PTL][Election] PTL candidacy for the Stein cycle

Hi all, I would like to announce my candidacy to continue as Vitrage PTL for the Stein release. I’ve been the PTL of Vitrage since the day it started. It has been an amazing journey, both for Vitrage and for me personally. During the Rocky cycle, we have significantly enhanced the stability and

[openstack-dev] [vitrage][ptg] Vitrage virtual PTG

Hi, As discussed in our IRC meeting yesterday [1], we will hold the Vitrage virtual PTG on the first week of October. If you would like to participate, you are welcome to add your name, time zone and ideas for discussion in the PTG etherpad[2]. [1]

[openstack-dev] [vitrage][ptl] PTL on vacation

Hi all, I'll be on vacation between 12th and 31st of August. Anna Reznikov ( anna.rezni...@nokia.com) will replace me during this time and will handle the Vitrage release. Thanks, Ifat __ OpenStack Development Mailing List

Re: [openstack-dev] [nova][searchlight][designate][telemetry][mistral][blazar][watcher][masakari][vitrage] Possible deprecation of Nova's legacy notification interface

Hi, Vitrage also uses the Nova legacy notifications. Unfortunately I will not attend the PTG, but I added the relevant information in the etherpad. Thanks, Ifat On Tue, Aug 28, 2018 at 5:31 PM Balázs Gibizer wrote: > Thanks for all the responses. I collected them on the nova ptg > discussion

[openstack-dev] [vitrage] vitrage virtual PTG

Hi, We will hold the vitrage virtual PTG on Wednesday-Thursday this week, October 10-11th. The agenda is listed in the etherpad[1], and you can still add new topics for discussion. We will skip the regular IRC meeting this week. [1] https://etherpad.openstack.org/p/vitrage-stein-ptg Thanks,

Re: [openstack-dev] [requirements][vitrage][infra] SQLAlchemy-Utils version 0.33.6 breaks Vitrage gate

Thanks for your help, Ifat On Thu, Oct 18, 2018 at 4:17 PM Jeremy Stanley wrote: > On 2018-10-18 14:57:23 +0200 (+0200), Andreas Jaeger wrote: > > On 18/10/2018 14.15, Ifat Afek wrote: > > > Hi, > > > > > > In the last three days Vitrage gate is

[openstack-dev] [requirements][vitrage] SQLAlchemy-Utils version 0.33.6 breaks Vitrage gate

Hi, In the last three days Vitrage gate is broken due to the new requirement of SQLAlchemy-Utils==0.33.6. We get the following error [1]: 2018-10-18 09:21:13.946 |

Re: [openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

Hi, On Wed, Oct 31, 2018 at 11:00 AM Won wrote: > Hi, > >> >> This is strange. I would expect your original definition to work as well, >> since the alarm key in Vitrage is defined by a combination of the alert >> name and the instance. We will check it again. >> BTW, we solved a different bug

Re: [openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

Hi, On Fri, Oct 26, 2018 at 10:34 AM Won wrote: > > I solved the problem of not updating the Prometheus alarm. > Alarms with the same Prometheus alarm name are recognized as the same > alarm in vitrage. > > --- alert.rules.yml > groups: > - name: alert.rules > rules: > - alert:

Re: [openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

Hi, We solved the timestamp bug. There are two patches for master [1] and stable/rocky [2]. I'll check the other issues next week. Regards, Ifat [1] https://review.openstack.org/#/c/616468/ [2] https://review.openstack.org/#/c/616469/ On Wed, Oct 31, 2018 at 10:59 AM Won wrote: >

[openstack-dev] [vitrage] No IRC meeting this week

Hi, We will not hold the Vitrage IRC meeting tomorrow, since some of our contributors are in Berlin. Our next meeting will be Next Wednesday, November 21th. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

On Thu, Nov 15, 2018 at 10:28 AM Won wrote: > Looking at the logs, I see two issues: >> 1. On ubuntu server, you get a notification about the vm deletion, while >> on compute1 you don't get it. >> Please make sure that Nova sends notifications to 'vitrage_notifications' >> - it should be

Re: [openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

Hi Won, On Wed, Oct 10, 2018 at 11:58 AM Won wrote: > > my prometheus version : 2.3.2 and alertmanager version : 0.15.2 and I > attached files.(vitrage collector,graph logs and apache log and > prometheus.yml alertmanager.yml alarm rule file etc..) > I think the problem that resolved alarm does

Re: [openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

Hi, Can you please give us some more details about your scenario with Prometheus? Please try and give as many details as possible, so we can try to reproduce the bug. What do you mean by “if the alarm is resolved, the alarm manager makes a silence, or removes the alarm rule from Prometheus”?

Re: [openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

Hi, In the alertmanager.yml file you should have a receiver for Vitrage. Please verify that it includes "send_resolved: true". This is required for Prometheus to notify Vitrage when an alarm is resolved. The full Vitrage receiver definition should be: - name: ** webhook_configs: - url: **

Re: [openstack-dev] Dose anyone have use Vitrage to build a mature project for RCA or any other purpose?

On Wed, Sep 5, 2018 at 4:59 AM zhangwenqing <18800173...@163.com> wrote: > Thanks for your reply! > So how do you analyse the RCA?Do you ever use any statistics methods like > time series or mathine learning methods?Or just use the method that Vitrage > provides? > > > zhangwenqing > > Hi,

Re: [openstack-dev] Dose anyone have use Vitrage to build a mature project for RCA or any other purpose?

On Tue, Sep 4, 2018 at 11:41 AM zhangwenqing <18800173...@163.com> wrote: > I want to use Vitrage for my AIOps project, but i can't get any relative > information, and I think this is not a mature project.Does anyone have > relative experience?Would you please give me some advice? > Hi, Vitrage

[openstack-dev] [vitrage][ptg] Vitrage virtual PTG

Hi, We will hold the Vitrage virtual PTG on October 10-11th. You are welcome to join and suggest topics for discussion in the PTG etherpad[1]. Thanks, Ifat [1] https://etherpad.openstack.org/p/vitrage-stein-ptg __ OpenStack

Re: [openstack-dev] [vitrage] I would like to know how to link vitrage and prometheus.

Hi, You can use the Prometheus datasource in Vitrage starting from Rocky release. In order to use it, follow these steps: 1. Add 'prometheus' to 'types' configuration under /etc/vitrage/vitrage.conf 2. In alertmanager.yml add a receiver as follows: - name: ** webhook_configs: - url: **

Re: [openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

Hi, A deleted instance should be removed from Vitrage in one of two ways: 1. By reacting to a notification from Nova 2. If no notification is received, then after a while the instance vertex in Vitrage is considered "outdated" and is deleted Regarding #1, it is clear from your logs that you