jason 075d766964 first | 3 anos atrás | |
---|---|---|
.. | ||
statsd | 3 anos atrás | |
.travis.yml | 3 anos atrás | |
CHANGELOG.md | 3 anos atrás | |
LICENSE.txt | 3 anos atrás | |
README.md | 3 anos atrás |
datadog-go is a library that provides a dogstatsd client in Golang.
Go 1.7+ is officially supported. Older versions might work but are not tested.
$ go get github.com/DataDog/datadog-go/statsd
// Create the client
c, err := statsd.New("127.0.0.1:8125",
statsd.WithNamespace("flubber."), // prefix every metric with the app name
statsd.WithTags([]string{"region:us-east-1a"}), // send the EC2 availability zone as a tag with every metric
// add more options here...
)
if err != nil {
log.Fatal(err)
}
// Send some metrics!
err = c.Gauge("request.queue_depth", 12, nil, 1)
err = c.Timing("request.duration", duration, nil, 1) // Uses a time.Duration!
err = c.TimeInMilliseconds("request", 12, nil, 1)
err = c.Incr("request.count_total", nil, 1)
err = c.Decr("request.count_total", nil, 1)
err = c.Count("request.count_total", 2, nil, 1)
You can find a list of all the available options here.
DD_AGENT_HOST
and (optionally) the DD_DOGSTATSD_PORT
environment variables to build the target address if the addr
parameter is empty.DD_ENTITY_ID
environment variable is found, its value will be injected as a global dd.internal.entity_id
tag. This tag will be used by the Datadog Agent to insert container tags to the metrics. You should only append
to the c.Tags
slice to avoid overwriting this global tag.The version 6 (and above) of the Agent accepts packets through a Unix Socket datagram connection. Details about the advantages of using UDS over UDP are available in our docs.
You can use this protocol by giving a unix:///path/to/dsd.socket
address argument to the New
constructor.
When transporting DogStatsD datagram over UDS, two modes are available, "blocking" and "asynchronous".
"blocking" allows for error checking but does not guarantee that calls to the library will return immediately. For example client.Gauge(...)
might take an arbitrary amount of time to complete depending on server performance and load. If used in a hot path of your application, this behavior might significantly impact its performance.
"asynchronous" does not allow for error checking but guarantees that calls are instantaneous (<1ms). This is similar to UDP behavior.
Currently, in 2.x, "blocking" is the default behavior to ensure backward compatibility. To use the "asynchronous" behavior, use the statsd.WithAsyncUDS()
option.
We recommend enabling the "asynchronous" mode.
If you plan on sending metrics at a significant rate using this client, depending on your use case, you might need to configure the client and the datadog agent (dogstatsd server) to improve the performance and/or avoid dropping metrics.
DogStatsD accepts packets with multiple statsd messages in them. Using the statsd.Buffered()
option will buffer up commands and send them when the buffer is reached or after 100msec.
Ex:
client, err := statsd.New("127.0.0.1:8125",
statsd.Buffered(), // enable buffering
statsd.WithMaxMessagesPerPayload(16), // sets the maximum number of messages in a single datagram
)
In very high throughput environments it is possible to improve performance further by changing the values of some kernel options.
If you're still seeing datagram drops after enabling and configuring the buffering options, the following kernel options can help:
sysctl -w net.unix.max_dgram_qlen=X
- Set datagram queue size to X (default value is usually 10).sysctl -w net.core.wmem_max=X
- Set the max size of the send buffer for all the host sockets.Run the tests with:
$ go test
Please see: http://godoc.org/github.com/DataDog/datadog-go/statsd
datadog-go is released under the MIT license.
Original code by ooyala.