Skip to main content
An entity profile collects every thread that shares a reference, such as a customer_id or an agent_id, and shows their history and metrics in one place. The threads themselves aren’t merged.

Set up a profile type

  1. In Entity Profiles, create a profile type and choose the reference key that identifies the entity, for example agent_id for an “Agents” type.
  2. Have your services attach that reference to their threads:
    With OpenTelemetry, set threadify.ref.agent_id on the span instead.
Profiles appear as threads with that reference arrive. You can also create a profile type and named profiles with the CLI, before any activity:
Use the type ID that the first command returns. Your plan sets how many profiles you can have.

Choose metrics

Metrics are configured per profile type in the dashboard. For example: failed refunds, approval violations, or how long runs take. Nothing is measured until you configure it. Open a profile to see its metrics, delivery health and history. Select any thread to see its steps and validation results. New activity can take a few seconds to appear.

Read the numbers carefully

A run that was retried can end in success after several failures or rule breaks. Look at these together:
  • Completion rate: how often runs eventually finished.
  • Failed steps and retries: problems along the way.
  • Validation findings: whether runs followed the contract.
  • Delivery health and trend: a summary to point you at what to investigate.

Walkthrough

To read profiles from code, see Entity profile queries.