Hi, all, I have a question for you🙏: I have deployed Signoz in the K8s cluster (including many components, frontend, query-service, clickhouse, etc.) But I found that there is a clause in the open source agreement of Signoz, saying that ee/ is the function of the enterprise version. If this ee/ file exists, the open source agreement ee/ LICENSE here will be used. So I would like to ask, is there an ee file in the 0.56.0 version of query-service? What are the differences between 0.56.0, 0.56.0-oss, and 0.56.0-cloud.3? Is there an ee folder in 0.56.0-cloud.3? I expect to use the open source version without violating the open source agreement.

0.56.0-cloud.3? Is there an ee folder in 0.56.0-cloud.3?

This is not relevant to you

What are the differences between 0.56.0, 0.56.0-oss

The 0.56.0. has ee license. By default, you use the ee community edition. You are not violating anything by using this unless you modify the source yourself.

I expect to use the open source version without violating the open source agreement.

There is ee community edition and there is oss edition. The oss edition (docker images with suffix

-oss

). If you prefer to use only MIT-licensed code, please use

-oss

images.

Hi @Srikanth Chekuri Thank you for your reply. I want to show you something. I am currently using the open source version of Signoz, version 0.56.0. I found that the RBAC permissions do not meet my needs. For example, I need the viewer role to not be able to see the logs menu because there will be sensitive data here, so I need to modify the front-end code. When I modify the front-end code and deploy it in an image, do I violate the open source agreement? If so, what should I do or what version should I use to modify the front-end so that it will not be affected? Another question is, if I deploy the backend query-service and use version 0.56.0, as long as I don't change the query-service code, I will not violate the open source agreement, right? But it is possible that I will change the address of clickhouse, is this okay?

But it is possible that I will change the address of clickhouse, is this okay?

Yes, you can configure any valid ClickHouse URL

if I deploy the backend query-service and use version 0.56.0, as long as I don't change the query-service code, I will not violate the open source agreement, right?

Yes, you do not violate if you do not change query-service code

For example, I need the viewer role to not be able to see the logs menu because there will be sensitive data here, so I need to modify the front-end code. When I modify the front-end code and deploy it in an image, do I violate the open source agreement?

You do not violate anything by modifying frontend code

thanks a lot，The last question is, when I modify the frontend code and release it online, will I be required to open source it? Or is it necessary to indicate some open source agreement in the code?

no

ok ok thanks a lot