fix(service): prevent signoz broken-pipe errors

[julpar]

Changes

The SigNoz ClickHouse healthcheck used wget --spider. That closes the connection before reading the body, so ClickHouse fails to write the /ping response and logs an Error with a full stack trace. At a 30s interval that is ~5,700 stack traces a day. The container stays healthy throughout (the check still exits 0), so nothing surfaces it. The noise buries real ClickHouse errors.

This switches it to wget -q -O-, which reads the body. Only the clickhouse healthcheck changes; the signoz one keeps --spider, as it targets a Go server that closes cleanly. templates/service-templates.json is deliberately untouched, matching earlier changes to this template.

Issues

• Upstream issue: [install] clickhouse on docker standalone reports broken pipe SigNoz/signoz#5140
• Same fix for SigNoz's Coolify casting: fix(healthcheck): prevent ClickHouse broken-pipe errors in the telemetrystore healthcheck SigNoz/foundry#194

Category

• Fixing or updating existing one click service

AI Assistance

• AI was used (please describe below)

If AI was used:

• Tools used: Claude Code
• How extensively: investigation, measurements, the one-line change, and this description. Results were verified against a running instance.

Testing

Verified on a live Coolify instance running this template, on clickhouse-server:25.5.6-alpine, the image it pins. That is a real deployment, not a local dev instance.

Each command ran 25 times in the container, counting new StaticRequestHandler errors:

wget --spider -q 0.0.0.0:8123/ping    22/25 errors
wget -q -O- 0.0.0.0:8123/ping          0/25 errors

After the change the errors stopped entirely.

One caution: do not fix this by switching the host to localhost. In the ClickHouse image it resolves to ::1 first, so with IPv6 disabled the connection is refused (wget exits 1). That shows no errors only because the request never reaches ClickHouse, and would make the check fail.

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have searched existing issues and pull requests (including closed ones) to ensure this isn't a duplicate.
• I have tested all the changes thoroughly with a local development instance of Coolify and I am confident that they will work as expected when a maintainer tests them.

[peaklabs-dev]

Thanks for your PR!