You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question for the future, definitely not near future (considering you are close to a release).
With Go permitting plug-in architecture in recent builds, have you given thought to separating the tailing functions from the metrics processing function to be incorporated as a plugin?
You have a phenomenally structured and well-built tailing function. I wouldn't want to duplicate efforts for another project considering yours has been put through tests and real-life examples.
I wanted to write a "tail-to-syslog forwarder" (multiplatform, but specifically for windows clients, as there currently is none), but realized I'd be duplicating most of your tailing and filewatching code.
I realize the syslog forwarding is out of scope of this project, that's why I was curious about the loadable plugins potential.
The text was updated successfully, but these errors were encountered:
jaqx0r
added
the
question
This issue looks like a usage problem, not a bug or feature request
label
Nov 5, 2018
Question for the future, definitely not near future (considering you are close to a release).
With Go permitting plug-in architecture in recent builds, have you given thought to separating the tailing functions from the metrics processing function to be incorporated as a plugin?
You have a phenomenally structured and well-built tailing function. I wouldn't want to duplicate efforts for another project considering yours has been put through tests and real-life examples.
I wanted to write a "tail-to-syslog forwarder" (multiplatform, but specifically for windows clients, as there currently is none), but realized I'd be duplicating most of your tailing and filewatching code.
I realize the syslog forwarding is out of scope of this project, that's why I was curious about the loadable plugins potential.
The text was updated successfully, but these errors were encountered: