OpenStack services in DevStack are managed by systemd, so you can check aodh-listener log by running `sudo journalctl -u devstack@aodh-listener.service | less`

-

Best regards,
Lingxian Kong

Catalyst Cloud

On Sat, Sep 7, 2019 at 2:51 PM Anmar Salih <anmar.salih1@gmail.com> wrote:

Dear Lingxian,

I cloud't find aodh log file.

Also I did 'ps -ef | grep  aodh'  and here is the response.

Best regards.

On Thu, Sep 5, 2019 at 6:56 PM Lingxian Kong <anlin.kong@gmail.com> wrote:

Hi Anmar,

Please see my comments in-line below.

-

Best regards,
Lingxian Kong

Catalyst Cloud

On Wed, Sep 4, 2019 at 2:51 PM Anmar Salih <anmar.salih1@gmail.com> wrote:

Hi Lingxian,

First of all, I would like to apologize because the email is pretty long. I listed all the steps I went through just to make sure that I did everything correctly.

No need to apologize, more information is always helpful to solve the problem.

 

4- Creating the webhook for the function by:  openstack webhook create --function 07edc434-a4b8-424a-8d3a-af253aa31bf8 . Here is a screen capture for the response. I tried to copy and paste the webhook_url " http://192.168.1.155:7070/v1/webhooks/c5608648-bd73-478f-b452-ad1eabf93328/invoke" into my internet browser, so I got 404 not found. I am not sure if this is normal response or I have something wrong here.

Like Gaetan said, the webhook is supposed to be invoked by http POST.

9- Checking aodh alarm history by aodh alarm-history show ea16edb9-2000-471b-88e5-46f54208995e -f yaml . So I got this response

10- Last step is to check the function execution in qinling and here is the response. (empty bracket). I am not sure what is the problem.

Yeah, from the output of alarm history, the alarm is not triggered, as a result, there won't be execution created by the webhook.

Seems like the aodh-listener didn't receive the message or the message was ignored. Could you paste the aodh-listener log but make sure:

1. `debug = True` in /etc/aodh/aodh.conf

2. Trigger the python script again