Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate with telegraf and grafana to visualize EPS #22

Open
thangld322 opened this issue Sep 2, 2019 · 1 comment
Open

Integrate with telegraf and grafana to visualize EPS #22

thangld322 opened this issue Sep 2, 2019 · 1 comment

Comments

@thangld322
Copy link

Hello.
I'm using your go-statsd to count events in my logs shipper app.
Everytimes it receives an event, it increases stat.inputEvents by one. Then, every second, I push that counter to telegraf server. Then, I use grafana to visualize this stat:
SELECT "value" FROM "stat_inputEvents" WHERE $timeFilter GROUP BY time($interval)

My settings is:
statsd.NewClient(statsdHost + ":" + strconv.Itoa(statsdPort), statsd.MaxPacketSize(400), statsd.MetricPrefix(""), statsd.FlushInterval(time.Second))

Since I flush it every second. Shouldn't this graph show Events Per Second of my shipper?
But it has almost 300k EPS average while the source that provides events to my shipper only has 60k EPS...
Can you tell me what I did wrong here please? Thank you so much!

@smira
Copy link
Owner

smira commented Sep 2, 2019

Hi @thangld322!

go-statsd as a library doesn't do any aggregation on the metrics. So if you increase some counter by one 1000 times, it sends one thousand increments for the counter to the server. Flush interval is only used to flush packets to the server if there's not enough data yet to build a full packet. So it controls maximum latency for metric. Usually there's some kind of aggregation between statsd client and time-series database which might affect the queries you're using.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants