Issue with Demo Alerts in Grafana OnCall OSS Hobby Version via Docker-Compose

Grafana Alerting
,
1

Hello,

I am experiencing a problem with Grafana OnCall (OSS Hobby version running with docker-compose), where demo alerts are not appearing in the “Alert Groups” despite successful messages. I have successfully set up the system and can access the Grafana OnCall interface. Integrations have been created, including a basic webhook integration with the following HTTP endpoint: https://grafana-oncall.example.com/integrations/v1/grafana_alerting/xxxxxxxx/. Below this endpoint, it prompts to “send a demo alert.” When I send a demo alert, I receive a success confirmation saying, “Demo alert was generated. Find it on the ‘Alert Groups’ page and make sure it didn’t freak out your colleagues :wink:”. However, no alert shows up in the Alert Groups.

This feature works as expected in the cloud version of Grafana OnCall, but not in my OSS hobby setup. Interestingly, demo alerts functioned correctly in my setup a week ago. Since then, I have made some changes and attempted to revert to my original configuration by deleting and redoing everything, yet the issue persists.

Key Points:

  • Configuration appears correct, and I can access the Oncall interface on my Grafana.
  • Sending a demo alert confirms success, but alerts do not appear in Alert Groups.
  • The same process works without issues on the Grafana OnCall cloud version.
  • Logs do not show any errors when sending demo alerts.
  • This functionality worked once before I made changes to the setup.

I’m stumped as to why demo alerts are not working and would greatly appreciate any assistance or insights from the community. Is there something I might be missing, or are there specific logs or configurations I should double-check?

Thank you in advance for your help!

2 
engine-1               | 2024-03-25 09:27:43 source=engine:app google_trace_id=none logger=root Start calculating latency for /integrations/v1/webhook/xxxxxxxxxxxxxx/
engine-1               | 2024-03-25 09:27:43 source=engine:app google_trace_id=none logger=apps.integrations.mixins.alert_channel_defining_mixin AlertChannelDefiningMixin started
engine-1               | 2024-03-25 09:27:43 source=engine:app google_trace_id=none logger=apps.integrations.mixins.alert_channel_defining_mixin AlertChannelDefiningMixin finished in 0.006258673965930939
engine-1               | 2024-03-25 09:27:43 source=engine:app google_trace_id=none logger=root inbound latency=0.018178 status=200 method=POST path=/integrations/v1/webhook/xxxxxxxxxxxxxx/ user_agent=curl/7.81.0 content-length=73 slow=0 integration_type=webhook integration_token=xxxxxxxxxxxxxx 
engine-1               | 2024-03-25 09:27:43 source=engine:uwsgi status=200 method=POST path=/integrations/v1/webhook/xxxxxxxxxxxxxx/ latency=0.019479 google_trace_id=- protocol=HTTP/1.1 resp_size=292 req_body_size=73

In logs, everything looks fine ? Can you help me to activate some debug logs or something that can help me to understand why the alert is not created after sending demo alert ?

3

Resolved, celery was not responding because of a network problem with docker and traefik.