Skip to main content
You approved a rule. Now what? Tero enforces it. You choose where and how. Some options are immediate and automatic. Others delegate to your engineers.

Enforce at edge

Execute rules before data leaves your network. Drop, sample, transform, redact.

Enforce in provider

Configure exclusion filters and routing rules directly via API. No deployment required.

Open PRs

Fix instrumentation at the source. Tero opens the PR, your team reviews.

Create tickets

Assign work to engineers in Linear or GitHub Issues.

Notify

Alert teams in Slack or email.

Set SLOs

Quality targets for teams to meet. Track progress over time.

​
Which to use?

MethodResolutionReversibleBest for
Enforce at edgeImmediateReversibleMost categories
Enforce in providerImmediateReversibleNo Edge deployed
Open PRsVariableReversibleCode-level fixes
Create ticketsVariable—Human decisions needed
NotifyVariable—Awareness
Set SLOsOngoingReversibleLong-term tracking
Tero recommends an enforcement method for each category. You can override, combine, or change later.