Hi Team, is there a provision to modify the base path of signoz UI and host it behind nginx at subpath? For instance: instead of https://mydomain.com/ i want https://mydomain/signoz/ since my app is already running at basepath /

@Prashant Shahi @Palash Gupta

@Rohan Shetty What's the use case here? I think you should be able to run SigNoz as a subdomain. Soemthing like signoz.mydomain.com AN specific reason you want it as a subpath?

yes 1. we have a restriction in terms of having multiple subdomain / CNAME per environment as we do not allow wildcard entries and hence as an alternative solution we try to configure the micro services / microapp using the path based routing wherever possible. 2. In the existing environments we cannot update the domain certificate to add a new CNAME and as a best practice we do not want to create additional resources such as Load Balancer, New SSL Certs, etc. for hosting a new micro service / microapp.

Hi @Rohan Shetty ! We currently working on to support custom baseURL to support that. It should take some time though as we are doing our best to switch tasks on priority basis. You can track it here: https://github.com/SigNoz/signoz/pull/1115

@Prashant Shahi @Palash Gupta: If I set "FRONTEND_BASE=/signoz " environment variable while deploying Signoz helm chart then the signoz front end will be accessible at /signoz path instead of "/" ?

@Rohan Shetty Currently, it won’t as the PR work is yet to be continued. However, you should be able to use another nginx server which can do that.

can you please share an example on alternative option?

@Rohan Bhatia it looks like we would need Frontend changes afterall. I tested deploying signoz to

/ui

path using Ingress. Runtime JS bundles returned 404, I am guessing these webpack changes would be able to resolve it. cc @Ankit Nayan @Palash Gupta @Pranshu