7 posts tagged with "Self-hosted"
View All TagsWhen OTEL tracing is enabled, a job run through a webhook or REST endpoint with a W3C traceparent header is connected to the caller's distributed trace. The job span and its flow step and script spans are relocated under the caller's span so the whole execution appears as one end-to-end trace, instead of as a separate one.
New features
- A traceparent header on the run endpoints connects the job to the inbound distributed trace.
- The job span, its flow steps and script subprocess relocate under the caller span in your tracing backend.
- The inbound traceparent is exposed as the TRACEPARENT env var and propagated to every flow step.
- Invalid traceparent headers are ignored, so the job_id / root_job trace lookup keeps working.
OTEL trace context exposed in jobs
Self-hostedWhen OTEL tracing is enabled, Windmill now exposes the W3C trace context of each job as TRACEPARENT and related env vars in the runtime, so user scripts can propagate context to downstream services across all supported languages.
New features
- TRACEPARENT environment variable set on every job runtime when OTEL is enabled.
- Format follows the W3C Trace Context spec: 00-{trace_id}-{span_id}-01.
- Available across all supported languages: Python, Bash, Bun, Deno, Go, TypeScript, Rust, C#, Ruby, Nu, Java, PHP.
Windmill operational metrics over OTLP
Self-hostedWindmill can now export its own operational metrics to any OTLP-compatible collector alongside traces and logs, complementing the existing Prometheus /metrics endpoint with a push-based option.
New features
- New "Metrics" toggle under Instance settings → OTEL/Prom.
- Operational metrics pushed to the same OTLP collector used for traces and logs.
- Complements the Prometheus /metrics scrape endpoint on port 8001 (push vs. pull).
Git sync available on Community Edition
Self-hostedGit sync is now available on Community Edition for workspaces with up to 2 users, in addition to Cloud and Enterprise Self-Hosted, with the same feature set including push, pull, GPG signing, and wmill.yaml configuration.
New features
- Git sync on Community Edition workspaces with up to 2 users.
- Same feature set as the Enterprise version: push, pull, GPG signing, wmill.yaml-driven configuration.
- Pricing-tier difference is enforced at the workspace user count, not at feature flags.
Self-hosted superadmins can now require every HTTP route to be served under /api/r/{workspace_id}/{route} via a single instance setting, matching the Cloud behavior and locking the per-route toggle.
New features
- New "HTTP route workspace prefix" instance setting under superadmin settings.
- When enabled, all routes are served under /api/r/{workspace_id}/{route}, regardless of the per-route toggle.
- The per-route toggle is disabled and labeled as enforced by the instance setting.
Superadmins can configure AI providers (OpenAI, Anthropic, Google AI, Azure, Bedrock, customai) at the instance level so every workspace inherits the same models, headers, and routing without per-workspace setup.
New features
- Configure AI providers (OpenAI, Anthropic, Google AI, Azure, Bedrock, customai, etc.) once at the instance level.
- Workspaces inherit instance defaults and can still override per-workspace.
- Centralizes model selection, base URLs, and shared credentials for self-hosted deployments.
HTTP and protobuf OTEL exporters
Self-hostedWindmill can now export OpenTelemetry traces, metrics, and logs over HTTP/protobuf and HTTP/JSON in addition to gRPC, broadening the set of compatible OTLP collectors and managed observability backends.
New features
- New OTLP exporter protocol options: gRPC, HTTP/protobuf, and HTTP/JSON.
- Compatible with managed observability backends that only accept HTTP-based OTLP.
- Exporter protocol is configurable per signal alongside the existing endpoint setting.