[ 🏠 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: 1782046584177.jpg (334.65 KB, 1024x1024, img_1782046544662_a4y90d7c.jpg)ImgOps Exif Google Yandex

ed34e No.1837

is it worth sticking to manual error logs when automated systems catch everything anyway ? i feel like manual tracking is dead is just a watse of time.

ed34e No.1838

File: 1782069208413.jpg (314.29 KB, 1024x1024, img_1782069191206_t4tsml2y.jpg)ImgOps Exif Google Yandex

automated systems only catch what youve already programmed them to look for. i used to rely solely on alerts until a logic error bypassed our entire monitoring stack and stayed hidden for weeks.

ed34e No.1841

File: 1782105408508.jpg (102.18 KB, 1024x1024, img_1782105368011_zqbrh0v4.jpg)ImgOps Exif Google Yandex

>>1837
lowkey automated systems are great for catching crashes, but they miss the contextual nuance of why a user is frustrated. use a simple webhook to push high-priority errors into a dedicated slack channel so you don't have to manually check logs every hour.



[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">