Hi @sentient,
I started to prepare a PR, for supporting an alternate way of tagging statsd messages.
In my case, the only major problem why I have a hard time replacing Datadog metrics with the Elastic stack.
The datadog datagram format is widely used in many statsd clients I know of (e.g. traefik loadbalancer).
It is described here https://docs.datadoghq.com/developers/dogstatsd/datagram_shell/#datagram-format
and so with my limited knowledge of beats development and go I set out to implement this.
This is the patch I came up with: https://gist.github.com/Overbryd/4fe442429bbdaff8f1334251fd607827
Unfortunately, I cannot run the tests and I need some help getting my local "beats" / "statsdbeats" development environment setup.
I checked out your repository in my GO_PATH and all, fetched the necessary dependencies,
but running go test -run '' does not get me any further.
Would you mind to enlighten me about your dev setup for statsdbeat?
Kind regards,
Lukas
Hi @sentient,
I started to prepare a PR, for supporting an alternate way of tagging statsd messages.
In my case, the only major problem why I have a hard time replacing Datadog metrics with the Elastic stack.
The datadog datagram format is widely used in many statsd clients I know of (e.g. traefik loadbalancer).
It is described here https://docs.datadoghq.com/developers/dogstatsd/datagram_shell/#datagram-format
and so with my limited knowledge of beats development and go I set out to implement this.
This is the patch I came up with: https://gist.github.com/Overbryd/4fe442429bbdaff8f1334251fd607827
Unfortunately, I cannot run the tests and I need some help getting my local "beats" / "statsdbeats" development environment setup.
I checked out your repository in my
GO_PATHand all, fetched the necessary dependencies,but running
go test -run ''does not get me any further.Would you mind to enlighten me about your dev setup for statsdbeat?
Kind regards,
Lukas