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

in_statsd: add a new input plugin for statsd #1741

Closed
wants to merge 1 commit into from

Conversation

fujimotos
Copy link
Member

This is a new plugin that receives metrics via UDP and outputs
aggregated statistics over them. It's designed to be compatible
with the most popular statsd implementation:

 https://github.com/statsd/statsd

For example, if you sends the messages as follows:

$ echo "foo:1|c" > /dev/udp/127.0.0.1/8125
$ echo "foo:10|c" > /dev/udp/127.0.0.1/8125

... then this plugin outputs the following record:

{"type"=>"counter", "bucket"=>"foo", "count"=>11.000000, "rate"=>11.000000}

With this, we can use Fluent Bit as a general solution for
aggregating performance logs.

Signed-off-by: Fujimoto Seiji [email protected]

This is a new plugin that receives metrics via UDP and outputs
aggregated statistics over them. It's designed to be compatible
with the most popular statsd implementation:

     https://github.com/statsd/statsd

For example, if you sends the messages as follows:

    $ echo "foo:1|c" > /dev/udp/127.0.0.1/8125
    $ echo "foo:10|c" > /dev/udp/127.0.0.1/8125

... then this plugin outputs the following record:

    {"type"=>"counter", "bucket"=>"foo", "count"=>11.000000, "rate"=>11.000000}

With this, we can use Fluent Bit as a general solution for
aggregating performance logs.

Signed-off-by: Fujimoto Seiji <[email protected]>
@fujimotos
Copy link
Member Author

Nah. I think I was overthinking the specification.

Reading #1546:

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.

What's actually required is a simpler plugin that can handle statsd
protocol. If aggregation is required, we can do it later on database.

@fujimotos fujimotos closed this Nov 19, 2019
@fujimotos fujimotos deleted the sf/in-statsd branch December 6, 2019 07:03
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

Successfully merging this pull request may close these issues.

1 participant