Open PRs

Variable Reversible Fix the problem at the source. Tero opens a pull request to remove or modify the instrumentation that’s generating waste. Your team reviews and merges.

Use this for code-level issues like accidental debug statements, excessive payloads, or logs in hot paths. The application stops generating the waste, so nothing needs filtering downstream.

How it works

Tero analyzes your codebase to find the instrumentation generating the waste. It creates a branch, makes the change, and opens a pull request. Your team reviews the PR like any other code change.

Setup

Connect your source control:

GitHub

Install the Tero GitHub App to enable pull requests.

Example

Tero identifies a debug log statement in checkout-api that shipped to production. The log says "got here lol" and fires 50,000 times per day. You approve the policy and select “Open PRs.” Tero locates the log statement in your codebase:

# src/checkout/service.py, line 142
def process_order(order):
    logger.debug("got here lol")  # <-- Tero removes this line
    ...

Tero opens a pull request:

Title: Remove debug log from checkout-api

This debug statement shipped to production and generates 50,000 logs/day.
It doesn't appear in any dashboard or alert.

Identified by Tero: https://app.tero.dev/policies/abc123

Your team reviews the PR. Once they merge and deploy, the application stops generating those logs.

When to use

Open PRs works best when:

The waste is a code mistake (debug logs, forgotten print statements)
The fix is straightforward (remove a line, change a log level)
You want a permanent fix

For configuration-based issues (debug mode left on), Tero can also open PRs to change config files if they’re in version control.

Enforce in provider Create tickets

Introduction

Issues

Master Catalog

Policies

Integrations

Reference

How it works

Setup

GitHub

Example

When to use

​How it works

​Setup

GitHub

​Example

​When to use

How it works

Setup

Example

When to use