Closed ORuessel closed 1 month ago
thanks for submitting this, it seems we'd need to configure the http server for health from gotstatsd: https://github.com/atlassian/gostatsd#configuring-http-servers
are you able / willing to contribute this change?
@josemore sorry for the long delay, i forget this request. Yes sure, i am testing. Which configuration for http server you prefer behind a network loadbalancer ?
This issue won't be actioned.
Description
In Kubernetes or other orchestration software with multiple instances of new statsd in a high flexibel environment general statsd docker image support a tcp port to monitor the health of statsd instance.
Acceptance Criteria
central port with tcp for loadbalancer to create a health check on this
Describe Alternatives
A clear and concise description of any alternative solutions or features you've considered Are there examples you could link us to?
Dependencies
Do any other teams or parts of the New Relic product need to be considered? Some common areas: UI, collector, documentation
Additional context
What else should we know about this story that might not fit into the other categories?
Estimates
Please provide initial t-shirt size. S = 1-3 days, M = 3-5 days (1 week), L = 1-2 weeks (1 sprint)
For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5): Suggested T-Shirt size (S, M, L, XL, Unknown):