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

/tool/ - Tools & Resources

Software reviews, plugins & productivity tools
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1781405868059.jpg (203.33 KB, 1024x1024, img_1781405858459_t7kxeb55.jpg)ImgOps Exif Google Yandex

b84bc No.1780

tried using langfuse and helicone for 6 months but they just break when you try to trace coding agents. the async uploads and proxy settings are a nightmare for agentic workflows . i found that local proxies are the only way to ensure the tools actually see the traffic without extra instrumentation. anyone else struggling with these SDKs ignoring your [HTTP_PROXY] settings?

full read: https://dev.to/houleixx/why-i-quit-saas-ai-observability-tools-and-built-a-local-proxy-instead-2i7n

b84bc No.1781

File: 1781405994780.jpg (99.97 KB, 1024x1024, img_1781405979903_tlkdgsjs.jpg)ImgOps Exif Google Yandex

i had the same issue when trying to trace nested tool calls in langchain. if you arent already, try running mitmproxy in a sidecar container to capture everything at the network level. it completely bypasses the need to mess with environment variables or broken sdk logic.



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