This message was deleted.
# support
s
This message was deleted.
v
@Palash Gupta
p
Hi @Kumaran Ilangovan Left Nav is present under container/SideNav
there is no allowed origin config over frontend
possibly @Vishal Sharma can help in that part
k
Hi @Vishal Sharma - I am deploying thru helm - hence, let me know the param to setup for the same. Thanks!
v
@Kumaran Ilangovan Are you unable to send trace events to signoz?
k
Yes Vishal - I can sent traces to Signoz. Now, I need to embed my Signoz UI in an iframe - and send events from parent frame. Currently having issues with origin. Hence, I need a way to allow parent page as a trusted origin - so that I can send js events to signoz UI (to show/hide components and such).
We are trying to run Signoz frontend behind nginx reverse proxy. When we try to access signoz using server path like https://domain.com/signoz only a blank page is displayed. We are able to access using root path and port. But in our case it needs to be under /signoz and not / . How do we update baseref in helm values.yaml for frontend? Deployment type : helm chart (kubernetes) cc: @Ganga Lakshmanasamy
a
@Kumaran Ilangovan the backend already supports all origins. You can try writing nxnix rewrite path rules to push requests from domain.com/signoz/<path> to <signoz_ip>/<path>... this however will help you view the dashboard in iframe. This is still hacky, I am not sure you will be able to send events and process them. Some browsers are peculiar about iframe restrictions.
do share if you get it to work
k
Sure will try.
g
@Amol Umbark The issue we see here is the index.html is loading when we have a different base path than the root path but the other CSS is not loading. It's trying to route to / instead of /apm. Sample : http://ip/apm works but the CSS path we see is http://ip/css/antd.dark.min.css which fails with a 404
k
@Ganga Lakshmanasamy - lets install latest signoz and try
1