You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Orgs other than Main org will prompt out "Unauthorized/Forbidden while accessing OnCall engine: /api/internal/v1/plugin/v2/status, status code: 403, check token" or "jsonData.stackId is not set", and there's no token created under Service Account section.
What did you expect to happen:
I know the Grafana OnCall engine only support one instance of the Grafana OnCall plugin at a time.
I wish to not use the API call to initialize the oncall, so that I can configure it through the GUI in the org I want
OR If I have to use an API call to initialize, I hope I can add the orgId option to the command
How do we reproduce it?
Install grafana oncall plugin through DashBoard CRD.
Only Main org will connected successfully, other orgs will prompt out like "jsonData.stackId is not set" or "Unauthorized/Forbidden while accessing OnCall engine: /api/internal/v1/plugin/v2/status, status code: 403, check token"
Let me know if I'm wrong, I beliew the expected procedure is something like: We don't use API call to initialize, we install oncall in the org we want, token created automatically, we provide oncall-engine url, then everything should be done?
The text was updated successfully, but these errors were encountered:
What went wrong?
What happened:
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'
Orgs other than Main org will prompt out "Unauthorized/Forbidden while accessing OnCall engine: /api/internal/v1/plugin/v2/status, status code: 403, check token" or "jsonData.stackId is not set", and there's no token created under Service Account section.
What did you expect to happen:
I know the Grafana OnCall engine only support one instance of the Grafana OnCall plugin at a time.
OR If I have to use an API call to initialize, I hope I can add the orgId option to the command
How do we reproduce it?
Grafana OnCall Version
v1.12.1
Product Area
Helm/Kubernetes/Docker
Grafana OnCall Platform?
Kubernetes
User's Browser?
No response
Anything else to add?
Grafana v11.2.3 (b37c88c4ec)
feature_toggles |
accessControlOnCall | false
enable | externalServiceAccounts
Let me know if I'm wrong, I beliew the expected procedure is something like: We don't use API call to initialize, we install oncall in the org we want, token created automatically, we provide oncall-engine url, then everything should be done?
The text was updated successfully, but these errors were encountered: