Logging can be tricky
corner.squareup.com
Logging can be tricky
1–10 of 77 posts
Re: Logging can be tricky
#2If you want tricky, try building a logging service and then enable logging to itself.
Re: Logging can be tricky
#3Compressing the text logs prior to writing them to the disk also helps with these kinds of issues. You can also offload your logging to a dedicated thread and then use a lock free queue to increase your performance even more.
Re: Logging can be tricky
#4If you want tricky, try building a logging service and then enable logging to itself.
I once enable logging on an AWS S3 bucket... which was our 'logs' bucket... which was the stated destination for the bucket logging. It wasn't a particularly costly error, but there was a lot of logspam...
Re: Logging can be tricky
#5Doe this increase the chance that you lose a bit of critical log if a fault causes the system to go down?
Re: Logging can be tricky
#6Doe this increase the chance that you lose a bit of critical log if a fault causes the system to go down?
Yes, but if the logs are just for debugging an application, it usually doesn't matter. Application logs are useful for figuring out why an application crashed, but shouldn't be relevant for figuring out why a system went down. However, if the app crashes while some log information is still in the system buffers, the system will still write them out, even if fsync() is never called.
It's been a few years since I looked at this, but it seems like there's only a small window that data will stay in the buffer before it will get automatically flushed. The nice thing about this automatic flush is that it won't cause the application to block.
Re: Logging can be tricky
#7Grey text on white background? Please help!
Re: Logging can be tricky
#8Grey text on white background? Please help!
You just dont understand sleek, minimal design. How pedestrian.
/s
Re: Logging can be tricky
#9Why would you fsync logs for a high-level service? Are you afraid a power outage is going to cause you to lose service logs?
Re: Logging can be tricky
#10Reminds me of the time I sped up the main business app of a large company by 85% by removing "debug" logging. 2tb/hr of "made it here" isn't really useful at the end of the day.
Not the first time I've seen that by a long shot.
//shakes zimmerframe, shuffles off