[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1780484006229.jpg (119.71 KB, 1080x721, img_1780483997707_km03um5v.jpg)ImgOps Exif Google Yandex

8a993 No.1752

ngl trying to decide if we should stick to manual error logging or switch to an automated system for our new microservices. manual logging works fine for small scripts, but the issue is that it becomes a massive bottleneck once you have multiple services running. you end up missnig critical traces because someone forgot to add a log line to a specific catch block. automated tools solve this by capturing the full context of a crash without any extra effort.
the trade-off
the main problem with automation is the sheer volume of data you end up with. if you dont configure filters properly, your storage costs will skyrocket. manual logging is much more targeted since you only record what you think is important. however, the risk of missing a silent failure in production is way too high with the manual approach. ive been using import logging; logging. basicConfig(level=logging. ERROR) for basic needs, but its not enough for complex distributed systems. if you want to avoid the headache of hunting down intermittent bugs, automation is the way to go ➡ just be ready to manage the noise

8a993 No.1753

File: 1780484123357.jpg (183.22 KB, 1280x853, img_1780484109131_s2uaavhf.jpg)ImgOps Exif Google Yandex

the "volume of data" argument is a bit of a bc you can just use sampling rates to prune the noise.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">