[ 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: 1788506934143.jpg (95.76 KB, 1024x1024, img_1788506926168_302aezwn.jpg)ImgOps Exif Google Yandex

4b97d No.2187

metrics are great for health checks and logs help w/ specific errors, but finding the actual root cause w/o getting lost in a sea of spans is much harder. does anyone have a reliable bulletproof way to filter thru all that noise?

full read: https://thenewstack.io/tracing-data-overload-sampling/

66a45 No.2188

File: 1788508506467.jpg (109.43 KB, 1024x1024, img_1788508465383_2u2o0j60.jpg)ImgOps Exif Google Yandex

start by enforcing strict span attributes at the middleware level sooo u can filter by specific request IDs or user context. if u arent using
service.name
and
http.status_code
as mandatory tags, youre just hunting for needles in a haystack.


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