Categories

​

Overview

• An assertion belongs to at most one category.
• A scenario can belong to any number.
• Categories belong to the organization, not to one traced function. A function’s Categories page shows the same categories with counts for that function only.

​

Why Categorize

• Experiment results by kind of check. An experiment’s rollup has one row per category, so you can see that a change fixed rebooking but regressed tone.
• Sharper generated assertions. When Bitfab generates assertions, it files each one under the category it fits and records why. Passing categoryIds limits generation to those categories.
• A review queue per topic. The Assertions page filters by category, so one person can review every assertion about one kind of behavior.

​

Creating and Editing Categories

Group the assertions on checkout-agent into categories by what they check
Create a category called "Rebooking" for assertions about changing a flight

const category = await client.categories.save({
  title: "Mandate compliance",
  description: "Checks explicit user instructions",
})
await client.traces.saveAssertions({
  traceId,
  assertions: [{ assertion: "Escalates conflicting calendar requests", category_id: category.id }],
})

category = client.categories.save(
    "Mandate compliance", description="Checks explicit user instructions"
)
client.traces.save_assertions(
    trace_id,
    [{"assertion": "Escalates conflicting calendar requests", "category_id": category["id"]}],
)

​

Deleting a Category

​

Tools and Methods