Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.foglamp.dev/llms.txt

Use this file to discover all available pages before exploring further.

A workflow is a named, repeatable process (e.g. deploy-digest); a workflow run is one execution of it. Tag your calls with a workflowName and a shared workflowRunId and Foglamp stitches them into a single run — see the data model.
workflowName and workflowRunId are passed together — both or neither. Reuse the same workflowRunId (a job id, request id, …) across every call in one execution. Traces with no workflow land in an Ungrouped bucket.

​
Workflows list

A card per workflow over the selected range, each showing run count, trace count, tokens, cost, last-run time, and an error badge when any run failed.

​
Workflow detail

Opening a workflow shows two things:
  • Run flow — a graph of the selected run, one node per trace, coloured by status and labelled with name, start time, and duration. Click a node to open that trace; each node also has a replay shortcut.
  • Runs table — every run of the workflow with its trace count, duration, cost, and timestamp. Click a row to load it into the flow graph above.

​
Renaming a run

A run is identified by its workflowRunId, which is often a UUID. Click the pencil next to a run to give it a friendly label — “Nightly digest · May 24” instead of the raw id. The label is stored against the workflowRunId; the id itself remains the canonical identity, so renaming is purely cosmetic and reversible.