Adding a new directory monitor input plugin. #8751
Conversation
![telegraf-tiger[bot]](https://avatars.githubusercontent.com/in/94907?s=60&v=4){kind=small}
There was a problem hiding this comment.
Thanks so much for the pull request!
🤝 ✒️ Just a reminder that the CLA has not yet been signed, and we'll need it before merging. Please sign the CLA when you get a chance, then post a comment here saying !signed-cla
There was a problem hiding this comment.
🤝 ✒️ Just a reminder that the CLA has not yet been signed, and we'll need it before merging. Please sign the CLA when you get a chance, then post a comment here saying !signed-cla
There was a problem hiding this comment.
🤝 ✒️ Just a reminder that the CLA has not yet been signed, and we'll need it before merging. Please sign the CLA when you get a chance, then post a comment here saying !signed-cla
ivorybilled
dismissed
telegraf-tiger’s stale review
I'm being attacked by a tiger
There was a problem hiding this comment.
🤝 ✒️ Just a reminder that the CLA has not yet been signed, and we'll need it before merging. Please sign the CLA when you get a chance, then post a comment here saying !signed-cla
sjwang90
added
new plugin
plugin/input
There was a problem hiding this comment.
Looks well thought through. I think we can clean it up further. Mostly minor feedback, but I think I'd like the parallelism to go away. It complicates the code and we're not going to get any better throughput for it. Keep in mind the limiting factor is going to be the TrackingMetrics by a long shot.
ivorybilled
force-pushed
the
directoryMonitorPlugin
branch
from
bf1c805
to
fdac2c5
Compare
|
!retry-checks |
This will monitor and parse all files coming into a single configured directory.
Closes #7548