Phobos.Monitoring.StatsD

Petabridge offers first-party support for StatsD using a high-performance, custom driver developed in-house by the Petabridge team (built on top of Akka.Streams!). This integration is made available to our users who install the Phobos.Monitoring.StatsD NuGet package from your organization's Phobos NuGet feed.

NOTE

In order to use any of the Phobos integrations, you will need to first configure your akka.actor.provider setting to use one of the ActorRefProvider implementations provided by the Phobos.Actor.* NuGet packages. Click here for details.

Configuring via HOCON

Phobos.Monitoring.StatsD can be configured via HOCON, as is the case with all first party drivers supported by Phobos:

phobos.monitoring{
	# Will cause the StatsD driver to be loaded
	provider-type = statsd

	statsd{
		# the IP address or hostname of the StatsD target endpoint.
		endpoint = ""

		# the listening port used by StatsD
		port = 8125

		# determines whether or not we'll use UDP or TCP transports for communicating with StatsD.
		# UDP is the generally accepted default, but Phobos.Monitoring.StatsD supports both.
		# Set to "tcp" if you need TCP support.
		endpoint-type = udp

		# frame-size defaults to 512, which is what's recommended over commodity Internet.
		# If you're using fast ethernet, 1432 is generally a safe frame size.
		# If you're using Gigabit ethernet, use 8932 frames. The larger the frame, the more
		# metrics we can stuff into a single transmission to StatsD.
		frame-size = 512

		# Enables multi-frame metrics. Multi-frame means that more metric reports get
		# included in a single network round trip, but the amount of data loss that occurs
		# in the event of a dropped UDP packet increases porportionately. For high throughput
		# systems, it's generally recommended to turn this setting on.
		multi-frame = on
	}
}

Aside from configuring the phobos.monitoring.provider-type to statsd the only mandatory setting is the statsd.endpoint, which tells the underlying StatsD driver which node to connect to for publication of its metrics.

We typically recommend you leave the endpoint-type=udp value on by default as that tends to be the lowest overhead and least hassle overall, but if your network can't support UDP then our driver still fully supports TCP connectivity for StatsD as well.

Third Party Samples

Here are some examples of Phobos users making use of our OpenTracing integration in the wild. Please take a look at these if you would like to get an idea of how you can put this feature to use.

• Monitoring Akka.NET with Datadog and Phobos: Metrics