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.
Aug 02, 2023 (4 months ago)
We had a quick question regarding the
eefolder that is present in the github repo.
Is that folder part of the enterprise edition and not present in the OpenSource version?
eefolder is part of enterprise version. It is also opensource but has enterprise license which prevents modifications.
eedirectory or any of its contents as part of any of the components right?
The Makefile seems to use only the
pkgdir for building the query service.
eecomponents. It can be self hosted for free.
Aug 04, 2023 (4 months ago)
eedirectory, is it not possible to run SigNoz without compiling with the ee query service?
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?
servicesand there are some api which are of course only present in the ee/query-service
SigNoz is designed to work without
You might still be building using
ee, build using pkg/query-service.
So the thing is, we were able to build without
What threw us off is that, when we ran everything via docker-compose, the frontend showed a 404 for
Our assumption was that this route was only supported in the
eeversion, 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.
Indexed 1023 threads (61% resolved)
SigNoz Production Feedback and Improvement Suggestions
Users shared their SigNoz experiences and feedback. Issues mentioned include memory consumption, UI/UX improvements, connection difficulties, and automation limitations.
Issues with SigNoz on DigitalOcean k8s After Upgrade
Thomas experienced issues with SigNoz on DigitalOcean k8s after upgrading to v0.19. Prashant identified a PR to address the issue and provided a solution.
Alert Issues After Upgrading SigNoz
James experienced issues with alert rules after upgrading SigNoz. Srikanth suggested using sqlite tool to remove the alerts.
Issue with Restarting Containers After Signoz Update
Div had issues with restarting containers after updating Signoz. Srikanth suggested checking the migration guide, which resolved the issue.
Removing SigNoz's Own Logs from Dashboard
Geoffrey wanted to remove SigNoz's own logs from the dashboard. nitya-signoz provided a solution referencing an existing issue and a filter for ingesting only desired logs.