Closed jl2005 closed 5 years ago
Thank you for filing an issue. I will check the detail. BTW, I'm not sure why the plugin should be disabled. Is it enough to just stop using the plugin?
Okay, I got the details. First one is a big bug and complicated, second one is easy to fix. Both cases are caused by concurrent access to a value.
I think this was fixed.
When I use
prometheus_tail_monitor
, I found thatFluend
pos_file
is incorrect. This is becauseprometheus_tail_monitor
will callFilePositionEntry::read_inode
andFilePositionEntry::read_pos
to modify the file pointer. WhenFluentd
is writingpos_file
, it is possible to write to the wrong location. Related issues see pos file error #1953At the same time,
prometheus_tail_monitor
will also iterateFluentd
tails
variable. When Fluentd is updatedtails
, it will causecan't add a new key into hash during iteration
. Related issues see can't add a new key into hash during iteration #1804It is recommended to temporarily Disable
prometheus_tail_monitor
and add it when there is a better implementation.