Issue Deploying Signoz 0.22 on Kubernetes
TLDR Nicolai faced difficulty deploying signoz 0.22 on Kubernetes due to a primary mismatch in the API endpoint. Srikanth confirmed it was a bug and allowed him to use the enterprise edition for his apps.
Jul 11, 2023 (5 months ago)
I am trying to deploy signoz 0.22 on Kubernetes. All components are running but I am having problems using the non-ee version of signoz-query-service.
The problem occurs already at login. As I have seen, the frontend sends a request to
/api/v1/loginPrecheck- but this API endpoint exists only in the "ee" variant of signoz-query-service.
I haven't found any code in the frontend that omits this call in the non-ee variant - moreover, the API endpoint
/api/v1/versionreturns the value "EE: Y" also in the non-ee variant.
Could it be that the non-ee variant of Signoz in version 0.22 is currently not usable?
Jul 12, 2023 (5 months ago)
Jul 13, 2023 (5 months ago)
eedirectory for internal, but productive apps?
Indexed 1023 threads (61% resolved)
Issue with Signoz v0.18.1 in Azure Kubernetes Cluster
KishanReddy encountered an issue with Signoz v0.18.1 in Azure Kubernetes Cluster. vishal-signoz requested API response, and Palash is looking into a potential frontend issue.
Discussing the `ee` folder and SigNoz OpenSource version
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.
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.