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
At the moment, it seems to be impossible to serve OnCall from a subpath in OSS deployments. Grafana Cloud serves OnCall from /oncall, but there's no option to specify this in any config file.
Applying a similar approach to grafana/grafana, allowing a serve_from_subpath configuration in the config and exposing this as a value in the Helm chart would be incredibly useful.
For context, the lack of this feature completely breaks hooking up a Grafana instance with an OnCall instance when trying to serve them from the same domain. Grafana wants to route to /integrations from the root of the domain, but we serve OnCall from /oncall, meaning Grafana would need to route to /oncall/integrations (like Grafana Cloud). Therefore, the only way to integrate Grafana and OnCall in this same-domain Enterprise setup is by serving OnCall behind a reverse proxy and integrating it with Grafana via the Webhook integration.
Product Area
Other
Anything else to add?
No response
The text was updated successfully, but these errors were encountered:
The current version of Grafana OnCall, at the time this issue was opened, is v1.4.4. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you 😄!
What would you like to see!
At the moment, it seems to be impossible to serve OnCall from a subpath in OSS deployments. Grafana Cloud serves OnCall from /oncall, but there's no option to specify this in any config file.
Applying a similar approach to grafana/grafana, allowing a serve_from_subpath configuration in the config and exposing this as a value in the Helm chart would be incredibly useful.
For context, the lack of this feature completely breaks hooking up a Grafana instance with an OnCall instance when trying to serve them from the same domain. Grafana wants to route to /integrations from the root of the domain, but we serve OnCall from /oncall, meaning Grafana would need to route to /oncall/integrations (like Grafana Cloud). Therefore, the only way to integrate Grafana and OnCall in this same-domain Enterprise setup is by serving OnCall behind a reverse proxy and integrating it with Grafana via the Webhook integration.
Product Area
Other
Anything else to add?
No response
The text was updated successfully, but these errors were encountered: