Skip to content
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

Allow OSS Configuration to Serve from Subpath #4302

Open
sternma opened this issue Apr 30, 2024 · 3 comments
Open

Allow OSS Configuration to Serve from Subpath #4302

sternma opened this issue Apr 30, 2024 · 3 comments

Comments

@sternma
Copy link

sternma commented Apr 30, 2024

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

@sternma sternma added the feature request New feature or request label Apr 30, 2024
Copy link
Contributor

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 😄!

@mderynck
Copy link
Collaborator

This should be configurable by setting the BASE_URL environment variable

@sternma
Copy link
Author

sternma commented May 8, 2024

Hi @mderynck -

If deploying via Helm, would this be env.BASE_URL or the top-level base_url value? I was not able to accomplish this using the top-level field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants