#general

Discussing the `ee` folder and SigNoz OpenSource version

TLDR Srinivas and Bharadwaj had queries about the ee folder in SigNoz's GitHub repo. vishal-signoz clarified that it is part of the enterprise version, open-source but with a license preventing modifications. The docker images use ee components by default. vishal-signoz guided Bharadwaj on how to run SigNoz without compiling with the ee query service.

Powered by Struct AI

1

12
4mo
Solved
Join the chat
Aug 02, 2023 (4 months ago)
Srinivas
Photo of md5-65498b9bc5ffb73ba57e2b3fba9a6b7d
Srinivas
05:51 AM
Hello everyone!

We had a quick question regarding the ee folder that is present in the github repo.

Is that folder part of the enterprise edition and not present in the OpenSource version?
vishal-signoz
Photo of md5-f936d3e5743d23344d6c60813189716f
vishal-signoz
07:32 AM
Yes, ee folder is part of enterprise version. It is also opensource but has enterprise license which prevents modifications.
Srinivas
Photo of md5-65498b9bc5ffb73ba57e2b3fba9a6b7d
Srinivas
07:47 AM
Okay, thank you!
Bharadwaj
Photo of md5-3028b9fffae3c97781209723ef45e88e
Bharadwaj
07:57 AM
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.
vishal-signoz
Photo of md5-f936d3e5743d23344d6c60813189716f
vishal-signoz
08:00 AM
By default docker images use ee components. It can be self hosted for free.
Aug 04, 2023 (4 months ago)
Bharadwaj
Photo of md5-3028b9fffae3c97781209723ef45e88e
Bharadwaj
07:37 AM
Just revisiting the ee directory, is it not possible to run SigNoz without compiling with the ee query service?
vishal-signoz
Photo of md5-f936d3e5743d23344d6c60813189716f
vishal-signoz
07:39 AM
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?
Bharadwaj
Photo of md5-3028b9fffae3c97781209723ef45e88e
Bharadwaj
07:41 AM
Its more around evaluation of SigNoz and its licensing for usage in the org
07:43
Bharadwaj
07:43 AM
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
vishal-signoz
Photo of md5-f936d3e5743d23344d6c60813189716f
vishal-signoz
07:45 AM
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

Bharadwaj
Photo of md5-3028b9fffae3c97781209723ef45e88e
Bharadwaj
07:47 AM
Will dig further and post if there are issues. Thank you 🙏
08:52
Bharadwaj
08:52 AM
Hey vishal-signoz 🙂

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.