-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
in_statsd: new input plugin #1546
Comments
I've been working on this issue since today, and will update |
@eduardo I reached the point that I can receive and parse incoming statsd
Now I'm seeing that there are two possible ways to go. One way is to emit
Another way is to aggregate records in
Which way do you think is appropriate? The easier route is the former |
After some thought, I've come to the conclusion that we should process For instance, according to the spec, Indeed, this is what many statsd-compatible servers do. For example,
a statsd-compatible server is expected to produce the following output:
I have spent much of today implementing |
from a consumer perspective, what makes easier to process the metrics or aggregate them later in a database?, what do you see in some use cases ? |
@edsiper I did a bit of research on this matter and posted a PR to #1741.
I'd greatly appreciate if I can get some feedback from you on that patch. |
@talawahtech If possible, can you check #1741 and give us some feedback? |
@edsiper After re-reading your comment, I posted a simpler patch at #1756, It can emit incoming metrics as msgpack records without loss of information,
I'm looking forward to your review and feedback! |
FYI: PR #1756 reviewed and commented |
@fujimotos yes, I think the approach in #1756 is more in line with how I plan to use it. I haven't gotten a chance to test it out yet, but I will try and provide feedback when I do. Thanks for working on this! |
Implemented by @fujimotos on #1756 |
Is your feature request related to a problem? Please describe.
I am currently interested in collecting and storing performance logs from cadvisor using its ability to export data to statsd. But this would also be a general solutions for storing performance logs from other systems that support statsd as an output format.
Describe the solution you'd like
A new input plugin that accepts data in the statsd format. Similar in concept to in_collectd.
Additional context
There are cases where it is preferable to store performance related data in a "logging" backend instead of a traditional metrics backend. Oftentimes this allows for better correlation against related data and more sophisticated querying.
The text was updated successfully, but these errors were encountered: