Deprecating swift-statsd-client

Deprecation Notice:

swift-statsd-client has not seen active development for a long time, and will be deprecated and will no longer be maintained. The package will receive critical bug and security fixes for 6-months and then archived. Please migrate to swift-metrics with an appropriate backend such as swift-otel, opentelemetry-swift or swift-prometheus as the replacement.

Reason:

Since this package was introduced we have observed a shift in the ecosystem towards Prometheus and OpenTelemetry based solutions. Adoption and engagement around the swift-statsd-client package has remained relatively low. With all of this in mind, we’ve decided to focus our efforts on maintaining these other heavily used metrics backend.

Migration Guide:

Visit the swift-metrics repository for documentation and setup instructions.

Thank you to all of the contributors of swift-statsd-client.

7 Likes

That's too bad as we recently adopted Swift Metrics for our project and decided to go with the statsd backend for simplicity. We are using a dockerized Graphite instance to visualize metrics. What would be the next obvious choice in terms of learning curve for a team with little experience in the matter. Thanks!

@craigwrong I'm glad to hear Swift Metrics and statsd backend worked for you!

One alternative is OpenTelemetry. Check out this example in Swift System Metrics. It shows how to setup swift-otel backend (which would export metrics in OpenTelemetry format) and how to view these metrics in a Grafana dashboard, running in a container next to your app.

Another one is export metrics in Prometheus format via Swift Prometheus backend.

2 Likes

To add to Vlad’s great suggestions. You can also continue using the statsd client. It won’t go away anytime soon and the repo will just get archived. I expect it to remain usable for quite some time after the deprecation since it has been unchanged for a long time now.

2 Likes