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
To Reproduce
Force any single writer to fail. For example, if you have a UDP writer, firewall the port. If you have a file writer, fill the disk with /dev/random or something. When one fails, they all fail. So if the disk is full, it stops writing to UDP, if you block the UDP port, it stops writing to disk.
Expected behavior
Only the failed writer should fail.
Desktop (please complete the following information):
RHEL7 linux
Additional context
Tested on LMG's installation, behavior not verified on other OS's (nor against the changes Pablo recently made)
The text was updated successfully, but these errors were encountered:
This actually raises a design question: if your file writer fails, do you emit a single warning and go on, or kill the logger and count on the logger manager restarting it, hopefully succeeding after a transient problem?
I've rewritten the default configs so that each "primary" logger just writes to file and UDP, and a "secondary" logger reads everything from UDP, parses and distributes it to InfluxDB and the CDS. UDPWriter no longer dies if the network is down (I never got it to die if a port was blocked by firewalld - were you blocking by some other method?). But in this case, if the file writer fails, I really would like the logger to die, wouldn't I?
Describe the bug
The title says it all.
To Reproduce
Force any single writer to fail. For example, if you have a UDP writer, firewall the port. If you have a file writer, fill the disk with /dev/random or something. When one fails, they all fail. So if the disk is full, it stops writing to UDP, if you block the UDP port, it stops writing to disk.
Expected behavior
Only the failed writer should fail.
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: