Return workflow observability reports via webhook and HTTP analytics APIs

Quick overview

This workflow exposes a POST webhook that collects workflow execution metrics, traces, error/failure data, and cost analytics via HTTP endpoints, then aggregates the results into a single observability report with basic insights and returns it to the caller.

How it works

1. Receives an observability query via a POST webhook.
2. Validates and normalizes the request into a query context (time range, workflow IDs, environment, and toggles for traces/costs).
3. Calls an HTTP endpoint to fetch execution metrics such as run counts, success rate, duration, and throughput.
4. Calls HTTP endpoints to fetch distributed traces plus error and failure data for the same time range.
5. Calls an HTTP endpoint to fetch cost analytics, including estimated totals and cost per successful execution.
6. Aggregates collection statuses and compiles a unified observability report with metrics, optional traces/costs, and generated insights, then returns it in the webhook response.

Setup

1. Configure the webhook endpoint (path: /observability, method: POST) in the system that will send observability requests.
2. Replace the placeholder HTTP endpoints (currently httpbin.org) with your real observability/telemetry APIs for metrics, traces, errors, and cost analytics.
3. If your APIs require authentication, add the needed HTTP credentials/headers to the HTTP Request steps.
4. Adjust request parameters you expect clients to send (for example from, to, workflowIds, includeTraces, includeCosts, and granularity) to match your environment and data sources.