https://signoz.io logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
v
Yes, 
ee
folder is part of enterprise version. It is also opensource but has enterprise license which prevents modifications.
s
Okay, thank you!
b
So just to confirm, the docker images which are available dont have the 
ee
directory or any of its contents as part of any of the components right? The Makefile seems to use only the 
pkg
dir for building the query service.
v
By default docker images use 
ee
components. It can be self hosted for free.
b
Just revisiting the 
ee
directory, is it not possible to run SigNoz without compiling with the ee query service?
v
It is possible to run SigNoz without ee. You will need to build SigNoz using the Makefile present in repo. Though I am curious why do you want to run SigNoz without ee? What’s the usecase?
b
Its more around evaluation of SigNoz and its licensing for usage in the org
Because we see that even though we disable ee and modify pkg/query-service , the frontend doesnt work for some of the tabs like 
services
and there are some api which are of course only present in the ee/query-service
v
Only APIs related to SSO are exclusive to 
ee
. SigNoz is designed to work without 
ee
You might still be building using 
ee
, build using pkg/query-service.
👍 1
b
Will dig further and post if there are issues. Thank you 🙏
Hey @Vishal Sharma 🙂 So the thing is, we were able to build without 
ee
. What threw us off is that, when we ran everything via docker-compose, the frontend showed a 404 for 
/api/v1/services
Our assumption was that this route was only supported in the 
ee
version, but on further digging, it seems to be nil (unhandled?) when we dont provide a skip top level config file to the query service Maybe a 500 should be thrown in this case and maybe we should not mandate users to set a skip config file? Happy to file a bug if required.
47 Views
Open in Slack
PreviousNext
Powered by