Open BojanOro opened 1 year ago
Having the same issue. After around 24 hours, it gets stuck. Restarting oncall engine resolves the issue.
On 1.3.77, it's still happening. Any direction to solving it?
Recently we made some changes to the way Grafana OnCall is initialized. Use 1.9.22, there were quite a few changes along the way from 1.9.0-1.9.22 to get things working.
externalServiceAccounts
feature toggle enabled.
This has already been enabled in the docker compose files and helm charts in the oncall repo.curl -X POST 'http://admin:admin@localhost:3000/api/plugins/grafana-oncall-app/settings' -H "Content-Type: application/json" -d '{"enabled":true, "jsonData":{"stackId":5, "orgId":100, "onCallApiUrl":"http://engine:8080/", "grafanaUrl":"http://grafana:3000/"}}'
curl -X POST 'http://admin:admin@localhost:3000/api/plugins/grafana-oncall-app/resources/plugin/install'
Grafana OnCall should now be ready to use. For additional troubleshooting see here
Hi folks,
We're having an issue where OnCall periodically refuses to connect in the UI. When clicking the OnCall plugin, we're prompted with the "initializing plugin" line while a dozen
sync
requests are made in the background. Each request results in a 200 with the following body:Clicking the "Configure" button on this error page tries to re-sync the plugin, and eventually results in the error message
On the backend, in both Grafana and OnCall Engine + Celery I don't see any error messages. The issue is resolved by restarting the OnCall Engine service. When I do this, the
sync
request returns withtoken_ok: true
.Any details on where to look further for information as to why this happens would be appreciated!
Details:
License: Open Source Plugin version: v1.1.32 Grafana Version v9.4.3 Hosted on Kubernetes (AKS), managed with ArgoCD