How attributes appear in common backends
Jaeger displays the array attribute
elementum.automation.workflow_chain as a JSON string.
Find a run by its run id
Every run has an id,elementum.automation.execution_id, shown in the Elementum run history. It is on the workflow span and on every action span of the run.
Open the trace from any matching span to see the whole run, including the trigger and, for a continued webhook, your own spans.
To find all runs of one automation, filter on
elementum.automation.id. To find runs of one published version, add elementum.automation.workflow_version.
Find failed steps
Failed action spans have statusERROR and elementum.action.status = FAILURE. Failed HTTP calls have status ERROR and an error.type.
Read the result:
elementum.automation.task_labelnames the step as it was named in the automation.elementum.error.messagesaysExecutor returned FAILEDwhen the step completed and reported a failure, or the class name of the error when one was raised.- A failed
send_api_requestoften has a failed HTTP client span under it. Itshttp.response.status_codeanderror.typeshow what the remote system answered. elementum.automation.retry_countgreater than0means Elementum retried the step. Each attempt is its own span.
elementum.toe_id and the run id to Elementum support, or open the run in the Elementum run history.
Measure slow partner calls
This recipe needs the HTTP client span, which is being released. See Send trace headers to other systems.
CLIENT and carry server.address. Their duration covers the whole call, including the response body.
- Group by
server.addressto compare partners, or byelementum.automation.task_labelon the parent span to compare steps. url.fullkeeps the path, so you can also group by endpoint. Query values are alwaysREDACTED.- Error rate per partner: count client spans with
error.typeset, grouped byserver.address.
Follow a trace into a partner system
- Turn on Include Trace Header on the Send API Request step. See Send trace headers to other systems.
- Make sure the partner system reads
traceparentand sends its spans to a backend you can query. If it uses a different backend, share the trace id with the partner. It is the same in both places. - Open the run’s trace. The partner’s server span is a child of the Elementum client span.
See a run from your own request
Sendtraceparent on your webhook call. See Continue your trace into Elementum. Then search for your own request as usual. The Elementum spans are under your client span.
Measure how long a run took
Theautomation.workflow span marks the start of a run and ends quickly, so its duration is not the run’s duration. The exception is a run started by a synchronous execution request, where the workflow span covers the whole run. Otherwise:
- Measure from the start of
automation.triggerto the end of the last action span of the run. - Or group action spans by
elementum.automation.execution_idand take the earliest start and latest end.
Find runs that one trigger started
One trigger firing can start several runs. They are all in the trigger’s trace.- For a continued webhook, the workflow spans are children of the trigger span. In Tempo:
{ name = "automation.trigger" && span.elementum.automation.trigger_type = "WEB_HOOK" } >> { name = "automation.workflow" } - For other runs, each workflow span has a span link to the trigger span and may not be its child. Open the trigger’s trace and list its
automation.workflowspans, or follow the links if your backend shows them.
Track automations in dashboards
Useful groupings for dashboards and alerts:
Exclude Elementum’s bookkeeping steps with
elementum.automation.system_task != true.
Because delivery is best effort, use these for trends and alerts, not for billing or audit counts.