-
Notifications
You must be signed in to change notification settings - Fork 5.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
Unix domain socket listener #1516
Milestone
Comments
please do! 👍 |
This sounds very useful. |
sparrc
pushed a commit
that referenced
this issue
Feb 2, 2017
mlindes
pushed a commit
to Comcast/telegraf
that referenced
this issue
Feb 6, 2017
closes influxdata#1516 closes influxdata#1711 closes influxdata#1721 closes influxdata#1526
maxunt
pushed a commit
that referenced
this issue
Jun 26, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Proposal:
Similar to the tcp_listener and udp_listener input plugins, it would be useful to have a unix_listener input plugin.
Current behavior:
No unix domain socket listener.
Desired behavior:
Have a unix domain socket listener.
Use case: [Why is this important (helps with prioritizing requests)]
The main benefit of a unix domain listener over a tcp listener on 127.0.0.1 is access control. Permissions of who can write to the unix domain socket can be controlled. With the tcp listener, anyone on the server could submit metrics, possibly polluting, poisoning, or overwhelming the output database.
I'd be willing to write this. It'd be very trivial to do, just wanted to open the idea up here first.
The text was updated successfully, but these errors were encountered: