-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grafana Oncall Plugin not connected #5100
Comments
I am getting the same error :( curl -X GET 'https://my-user:[email protected]/api/plugins/grafana-oncall-app/resources/plugin/status' "error setting up request headers: failed to parse JSON response: json: cannot unmarshal object into Go value of type []plugin.OrgUser " Grafana Grafana OnCall Version |
I should mention that i have self-hosted grafana with multiple organizations, so enabling the externalServiceAccounts didn't work for me (as I learned from this https://github.com/grafana/grafana-plugin-examples/blob/main/examples/app-with-service-account/README.md). |
@Ennakin Multiple organizations in Grafana is not supported by OnCall. Is |
accessControlOncall flag isn't enabled nor through config file, nor through docker-compose envs. RBAC section in grafana.ini looks like this so should the externalServiceAccounts toggler be enabled? If so I get "PluginAppClientSecret not set in config" error. |
|
Thank you! I checked settings area, externalServiceAccounts is only feature that is on. What PluginAppClientSecret is? |
|
there is only sa-autogen-OnCall account wich was generated a few month ago with the installation of grafana-oncall. and it has 1 token |
Try going to Administration->Plugins and data->Plugins Grafana OnCall make sure there is an IAM tab on that screen and also check in the grafana log file if there is any errors on startup regarding the plugin. That service account should get created when the plugin is loaded. |
IAM tab is in place. I still get 'msg="Request Completed" method=GET path=/api/plugins/grafana-oncall-app/resources/plugin/status status=500 ... msg="Error making sync request" error="error getting settings from context: PluginAppClientSecret not set in config "' in grafana logs |
Is there any chance I can use a post method to create this service account?
|
And if I switched to grafana-enterprise would I need a license to use oncall plugin? |
This service account can't be created by the user it should be created automatically by the plugin.
You need a license to use all the features of grafana-enterprise, oncall does not have a license it just conforms to the Grafana version it is installed on. |
In the enterprise mode with 'enable = externalServiceAccounts, accessControlOncall' setting I still get 'PluginAppClientSecret not set in config' error. |
Hello I have the exact same issue, the most disturbing par is that it was working but as soon restarted grafana the oncall pages where displaying "Plugin not connected". I tried to install and uninstall using the API, the UI and ansible without success. Grafana Version Grafana logs when I hit the retry button :
Edit, update to v1.11.5, same issue |
we rolled back to 11.1.1 of grafana, 1.9.30 of oncall and 1.9.26 of oncall-plugin. this is the only configuration it works more or less fine. |
the second I wrote the prev comment we faced another issue:
every time i'm trying to connect to the plugin |
Got the same problem with
I add the following features as describe in the thread :
I got the IAM tab in the plugin setting. But I got no success
|
grafana 11.3.0 has been disabled in the e2e test currently (#5207 ) so I guess oncall is currently not compatible. Looking at the changes in grafana 11.3.0, grafana/grafana#93849 seem like a possible source of the problem. |
since grafana has gained rbac support for all editions, i assum its safe to work on |
Also affected in the upgrade. In the future, release notes should indicate breaking changes such as major auth re configurations. Grafana set |
disabling feature toggle "accessControlOnCall" helped
|
It helped, but it was not enough. I had to add also GF_AUTH_MANAGED_SERVICE_ACCOUNTS_ENABLED=true env variable. |
Hi I finally managed to get OnCall to work using these commands here: curl -X POST 'https://admin:<admin_password>@<grafana_host>/api/plugins/grafana-oncall-app/settings' -H "Content-Type: application/json" -d '{"enabled":true, "jsonData":{"stackId":5, "orgId":100, "onCallApiUrl":"http://oncall-engine:8080/", "grafanaUrl":"http://<grafana_address>/"}}' curl -X POST 'https://admin:<admin_password>@<grafana_host>/api/plugins/grafana-oncall-app/resources/plugin/install' Check that everything works properly curl -X GET 'https://admin:<admin_password>@<grafana_host>/api/plugins/grafana-oncall-app/resources/plugin/status' | jq However I'd like to avoid having to run commands. Could you please tell me how to configure it programmatically? (Using the Helm chart?) |
This is how my configuration looks:
I also had to manually set |
@maffelbaffel I followed your guide and it works perfectly. Thank you very much. Do you encounter the parsing error in Grafana OnCall Insights dashboard? |
I have the same error here, did you find a fix? |
This is because the queries in this dashboard are flawed.
The dollar sign at |
in settings > variables > alert_groups_total? or did you change on every visual, because change on every visual for me did no fix it (instance, team, integration etc) still have parser problems and change the variable alert_groups make the dashboard return no data |
Oh wait, my memory tricked me here I guess. It was quite some time ago when I fixed that in my setup. I think the error occurs when the Are you using the Helm chart? If yes, have you enabled the exporter? oncall:
exporter:
enabled: true You also need to create a ServiceMonitor manually because the helm chart does not offer the functionality to create one yet. See this for examples. |
What went wrong?
What happened:
The configuration looks ok though
I have a hobby mode of grafana running in containers. The engine version is also 1.9.30, grafana version is 11.3.0-76679. The integrations is still working, alerts are still being sent. There is an error In grafana container logs: " level=error msg="Request Completed" method=POST path=/api/ds/query status=500"
What did you expect to happen:
How do we reproduce it?
Grafana OnCall Version
v.1.9.30
Product Area
Helm/Kubernetes/Docker
Grafana OnCall Platform?
Docker
User's Browser?
Google Chrome
Anything else to add?
No response
The text was updated successfully, but these errors were encountered: