feat: add signoz template

[GauthierPLM]

Changes

• Added Signoz template
• Added an icon for Signoz

Issues

• fix SigNoz #4132
• fix Add SigNoz to Coolify services SigNoz/signoz#6368

Further testing and improvement suggestions are welcome! :)
In particular, I am not sure my approach is the best one to expose the OTEL collector.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[GauthierPLM]

Is there any way to ignore the example secret from the XML, since it's not a real secret?

[pkudinov]

@GauthierPLM Outstanding work! I just deployed it to test and it works.

Two questions

1. It seems that sending logs over http using JSON is not supported. The use case is Vercel -> Self hosted Signoz.
   Here is the documentation: https://signoz.io/docs/userguide/send-logs-http/ Is that something you could easily add?

2. The service shows up as unhealthy because below three containers (rightfully?) are down? Is this normal?

[GauthierPLM]

Hi @pkudinov

1. It seems Coolify is not able to automatically set 2 URLs for a service, so you need to define it yourself like this: https://signoz-grpc.example.com:4317,https://signoz-http.example.com:4318

Since the docker compose exposes ports 4317 & 4318, you could also use the signoz service URL to call your machine, as long as the DNS return the machine IP (so no Cloudflare proxy).

2. These three services are run at the compose start and then shutdown. They are all initialization / DB migration services that don't need to run for long.
   I'm also investigating to add healthchecks to the otel-collector container.

[pkudinov]

@GauthierPLM ,

4317&4318 are exposed and all good. I had to map them to subdomains in Cloudflare and all good.

But JSON logs are not working through tracing, they require port 8082 instead which is not being exposed as described in Signoz self-hosted documentation here: https://signoz.io/docs/userguide/send-logs-http/

[GauthierPLM]

@pkudinov in this case, I will keep them no exposed and will let users do the setup would it be needed. This will follow the official behavior and (hopefully) save some confusion.

[flawnn]

Maybe this issue will not occur when actually using the template over the UI, but for me, when using the template via a Docker Compose Service in Coolify, I had permissions issues with the /etc/clickhouse/* files, specifically with the config of Clickhouse.

After manually 777'ing the files in the /data/coolify/services/<service_id>/clickhouse/* directory, everything seems to have worked out. But 777'ing shouldn't be the solution here as well, I guess.

[GauthierPLM]

Maybe this issue will not occur when actually using the template over the UI, but for me, when using the template via a Docker Compose Service in Coolify, I had permissions issues with the /etc/clickhouse/* files, specifically with the config of Clickhouse.

After manually 777'ing the files in the /data/coolify/services/<service_id>/clickhouse/* directory, everything seems to have worked out. But 777'ing shouldn't be the solution here as well, I guess.

@flawnn do you have more details on the error you encountered? I haven't found any issue on my side.

[themodernpk]

+1

[kgotso]

Shouldn't the container named init-clickhouse share the same volume as the actual clickhouse container