After completing this topic, you can review candidate Runs, adjust membership, manage statistics, update alignments, and track configuration changes over time.Documentation Index
Fetch the complete documentation index at: https://docs.siftstack.com/llms.txt
Use this file to discover all available pages before exploring further.
New to Families? Read the Overview to understand how members, alignments, and statistics work together before proceeding.
When to use this workflow
Use this workflow on an ongoing basis after initial Family setup. As new Runs are ingested, the Family’s candidate query surfaces matching Runs for review. This workflow covers how to act on those candidates, adjust membership, manage statistics, and update the Family configuration when your test program or requirements change.Before you begin
- An existing Family. See Group Runs into a Family.
- A candidate query configured on the Family is recommended for automated candidate surfacing; see the candidate query step in Group Runs into a Family.
Complete the workflow
Step 1: Review candidate Runs
In the Family overview page, if the Family has a candidate query and unreviewed matching Runs exist, the page shows a N Family candidates to review.- Click the callout to open the Family in edit mode on the Candidates tab.
- Review the matching Runs and decide whether each one belongs in the Family.
- Select the Runs you want to act on and use Bulk Actions > Include in Family or Exclude from Family.
- When excluding, enter a rationale. This is stored in version history.
- Click Save.
You can also review candidates from an active Explore session without navigating away. Hover over the Family in the data source panel to see the candidate count, then click Review Run(s) to inspect them in Explore before committing.
Step 2: Add or exclude members manually
To update membership outside the candidate flow:- Open the Family overview page.
- Click Edit.
- In the Membership step, use the search field to find Runs by name or Asset.
- Use + to include or − to exclude each Run.
- Click Save.
Step 3: Edit the candidate query
To change the CEL expression that surfaces candidate Runs:- In the Family overview, click Edit Family.
- In the Membership step, click Edit candidate query.
- Update the CEL expression. Click Show CEL documentation in the editor for syntax reference.
- Click Preview to verify the updated query returns the expected Runs.
- Click Save.
Step 4: Manage statistics
Statistics compute aggregate time series across all included members. You can view, edit, duplicate, or delete them from the Family Analysis section of the Family overview page. To view a statistic: Click the statistic name to open the preview. The preview shows the aggregate time series and theinput_count diagnostic series.
To edit a statistic:
- Open the statistic options and click Preview/Edit Stat.
- Update the channel, aggregation type, output rate, data ranges, or fallback channels.
- Click Save. Sift recomputes the statistic with the updated configuration.
Step 5: Update alignments
If your test program has changed, for example, a new event type has been introduced or a channel has been renamed, you may need to update the alignment configuration.- Open the Family in edit mode.
- In the Align Data step, edit the alignment name, type, or reference event.
- Click Save.
Step 6: More options
The More options menu (the ⋮ button on the Family overview page) provides the following actions. Share: Copies a shareable link to the Family overview page to your clipboard. Duplicate: Creates a copy of the Family with the same configuration, members, statistics, and alignments. The duplicate opens as a new draft for you to rename and modify before saving. Download YAML: Downloads the Family’s full configuration as a YAML file. Use this to version-control configurations outside Sift, share configurations across environments, or seed a new Family from an existing one. Upload YAML: Replaces the Family’s configuration with a YAML file you provide. On save, Sift validates field names and returns an error for any unrecognized field. Invalid field values are automatically corrected. Edit as YAML: Opens the Family configuration in an inline YAML editor. Click Save when done. On save, Sift validates field names and returns an error for any unrecognized field. Invalid field values are automatically corrected. Archive: Marks the Family as read-only. See Archive a Family below. View Family Docs: Opens the Families documentation in a new tab.Step 7: Review version history and revert
Every save to a Family creates a version history entry. To review the history:- Open the Family overview page.
- Click the Version history tab.
- In the Version history tab, find the version you want to restore.
- Click Revert to this version.
- Confirm. Sift creates a new version history entry recording the revert.
Archive a Family
When a test program is complete and the Family no longer needs to be updated, archive it to mark it as read-only.- On the Family overview page, click More options.
- Select Archive and confirm.
Verify the result
After working through this workflow:- The Family member count reflects your current review decisions.
- Excluded Runs appear in the Excluded tab with their recorded rationale.
- Version history shows a complete audit trail of all changes.
- Any updated statistics have been recomputed and are available in Explore and Rules.
Next steps
- To visualize the updated Family in Explore, see Compare Runs visually against a Family baseline.
- To update Family Rules after a configuration change, see Detect statistical deviations using Family Rules.