Symbolicator sends metrics to localhost when StatsD isn't configured
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Look at the Docker Compose configuration that sets the SYMBOLICATOR_STATSD_ADDR default of 127.0.1:8125 and the symbolicator service definitions in the compose files. Decide how to leave the variable unset (or disable StatsD) when STATSD_ADDR isn't configured, and verify with docker compose up symbolicator that no metric-send errors appear. Done means the errors no longer show up for deployments without StatsD.
Written by the indexing model from the issue text.
Description
We're running Sentry self-hosted 26.10.0 without a StatsD server and noticed metric-send errors from both symbolicator and symbolicator-cleanup.
It looks like Docker Compose defaults SYMBOLICATOR_STATSD_ADDR to 127.0.0.1:8125 when STATSD_ADDR isn't set, so both containers try to send metrics to a port where nothing is listening.
Is this intentional? I'd expect StatsD metrics to be disabled unless a server is configured.
- Dominant language
- Shell
- Stars
- 9.6k
- Forks
- 2k
- Avg merge
- 2d 54m
- Merged PRs (30d)
- 27
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/self-hosted
-
Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/self-hosted#4577 · 2 reactions ·
Maintainers usually reply within 1 day
-
Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/self-hosted#4567 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/self-hosted#4518 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Waiting for: Community
Difficulty 4/5 3-5 days Newbie friendliness 47/100
getsentry/self-hosted#4581 · 1 comment ·
Maintainers usually reply within 1 day
-
Waiting for: Product Owner
Difficulty 4/5 3-5 days Newbie friendliness 53/100
getsentry/self-hosted#4580 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
All issues in getsentry/self-hosted
Similar issues
-
TLS guide repeats certs/ in the certificate directoryPossibly taken @maheshrijal claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
prometheus/docs#3156 ·
Maintainers usually reply within 2 days
-
triaged
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
fullsend-ai/agents#1786 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
osam-cologne/archlinux-proaudio#917 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
IBM/bob-oic-tutorials#24 ·
Maintainers usually reply within 1 day