123, then the shared connectivity code would check if the override resource is set, and if the workflow_id stored in it is 123 it would apply the override config. This way the normal pipelines can continue running unaffected.WM_FLOW_PATH and WM_FLOW_JOB_ID which contains info about the immediately encapsulating flow. Since we'll be dealing with nested flows here it won't work.Weekly kenote to tell you about our latest updates https://discord.com/channels/930051556043276338/1278977038430240813 https://youtube.com/live/2dGd9TdT8xs?feature=share
henri-c · 4d ago
### HTTP tracing (EE) Capture HTTP requests made by job scripts as observability spans Features: - View HTTP request traces (method, URL, status, timing) in the job details UI - Auto-instrumentation for Native TypeScript, MITM proxy for other languages - Integrates with external OpenTelemetry collectors changelog: https://www.windmill.dev/changelog/http-tracing docs: https://www.windmill.dev/docs/advanced/instance_settings#http-tracing Additionally jobs memory metrics are now fully OSS!
Pyra · 2w ago
First keynote of the year here https://discord.com/channels/930051556043276338/1278977038430240813 🙂
henri-c · 4w ago