The Observability Chart widget plots platform telemetry for a single resource over time, directly inside a Workshop application. You can use this widget to embed live operational metrics—such as execution counts, latency, and compute utilization—alongside the rest of your workflow, so that operators can spot trends, anomalies, and performance shifts for the entire workflow at a glance.
Module builders configuring an Observability Chart widget can:
The screenshot below shows an operational dashboard built from several Observability Chart widgets: the execution counts and P95 duration for an Escalate Order action, alongside the same metrics for a triagePatient function. A single time range control at the top of the module drives all four charts.

The metrics shown here are the same near real-time metrics surfaced elsewhere in the platform—see AIP observability metrics for more details. The Observability Chart widget lets you embed those metrics in a purpose-built Workshop application.
The widget setup panel is shown below, configured to plot executions for a triagePatient function over a variable-backed time range.

Select the type of resource whose metrics you want to plot. The remaining configuration options depend on this selection. Supported resource types are:
Choose the specific resource—the function, action type, or compute module—to chart. Only one resource can be plotted per widget; add multiple Observability Chart widgets to compare several resources side by side.
Select which metric to plot for the chosen resource. The available metrics depend on the resource type:
The visible time window is controlled by two timestamp variables:
Back these options with Workshop variables to control the range shown, for example, from a Date/Time Picker elsewhere in the module. These variables are also widget outputs. When a user selects a range directly on the chart, the widget writes the new bounds back to the Start time and End time variables. This lets you zoom the chart interactively and drive other widgets from the selected range.
Telemetry is only available while the underlying resource is reporting metrics. If the resource cannot be found, or a compute module is not currently running or has no active session, the widget displays a message in place of the chart rather than an empty plot.