Proposal Review: SSWG-0007 (Statsd Client)
After the discussion thread, we are proposing this as a final revision of this proposal and enter the proposal review phase which will run until the 29th July 2019.
The feedback model will be very similar to the one known from Swift Evolution. The community is asked to provide feedback in the way outlined below and after the review period finishes, the SSWG will -- based on the community feedback -- decide whether to promote the proposal to the Sandbox maturity level or not.
What goes into a review of a proposal?
The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the evolution of the server-side Swift ecosystem.
When reviewing a proposal, here are some questions to consider:
What is your evaluation of the proposal?
Is the problem being addressed significant enough?
Does this proposal fit well with the feel and direction of Swift on Server?
If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
Thank you for contributing to the Swift Server Work Group!
What happens if the proposal gets accepted?
If this proposal gets accepted, the official repository will be created and the code (minus examples, the proposal text, etc) will be submitted. The repository will then become usable as a SwiftPM package and a version (likely
0.1.0) will be tagged. The development (in form of pull requests) will continue as a regular open-source project.
- Proposal: SSWG-0007
- Authors: Tom Doron
- Sponsor(s): TBD
- Review Manager: TBD
- Status: Implemented
- Implementation: tomerd/swift-statsd-client
- Forum Threads: Pitch, Discussion
metrics backend for swift-metrics that uses the statsd protocol
|Proposed Maturity Level||Sandbox|
|Dependencies||swift-nio > 1.0.0, swift-metrics > 1.0.0|
for a background on metrics in swift applications, see the metrics proposal
the statsd protocol is simpler than most custom metrics solutions (eg prometheus), yet extremely popular since it is language agnostic and easy to implement both client and server side. as such, it can be used to integrate applications with many observability solutions such as:
statsd client will allow server applications written in swift to easily integrate with many popular observability solutions. the client, like the protocol, is designed to be lightweight and delegate most computation to the observability server
metrics types are mapped as following:
the client is primarily designed to be used within the context of the swift metrics api. as such, the application needs to create an instance of the
StatsdClient and bootstrap the
MertricsSystem as part of the application's main:
let statsdClient = try StatsdClient(host: host, port: port) MetricsSystem.bootstrap(statsdClient)
to cleanly release the networking resources occupied by the client, the application should also shutdown the client before it terminates:
as mentioned above, usage of the client is designed to be done primarily via the swift metrics api and the client does not provide additional functionality beyond the metrics api surface area. in other words, users are not expected to interact with the client directly beyond bootstrap and shutdown. emitting metrics information is done via the standard metrics api, as described in https://github.com/apple/swift-metrics#metric-types
the client implements the
statsd protocol as following:
name is constructed from the metric object label and dimensions concatenated with a dot between them
value is computed from the data provided to the metrics API. no in-memory aggregation is done at the client level, and data is mostly pass-through. note that some
statsd metrics types accept positive values only in the UInt64 range, while the metrics API generally accepts Int64. in cases of such mismatch, the client truncates negative values to zero
thew client uses swift-nio to establish a
UDP connection to the statsd server. in later phases, the client will also support
this is a fairly new library, not enough production usage to justify anything beyond sandbox
no alternatives exist to my knowledge