Turn anomalies and error traces into pull requests
Start from an anomaly or error trace. Tracekit reviews the production evidence and mapped repository. It opens a pull request when it finds a useful code fix.
Unhandled checkout exception in checkout-api
Evidence reviewed
Exception, problem spans, release, and source context
Repository inspected
Source files read through GitHub APIs
Fix prepared
3 focused file changes proposed
Handle the checkout validation exception
Pull request openClose the loop without losing control
Tracekit connects production context to the GitHub workflow your team already uses.
Production evidence included
The agent reviews anomaly details or error-trace context. Evidence can include exceptions, problem spans, source locations, releases, and repeated database statements.
A fix only when useful
The agent reviews the evidence and repository first. It stops without a pull request when the evidence does not support a useful fix.
Normal GitHub pull requests
Tracekit creates a normal pull request with its evidence and rationale. Your team reviews it through the usual GitHub workflow.
Service-to-repository mapping
Map each OpenTelemetry service to its repository and base branch. Add a source root when the service lives in a monorepo.
Human-controlled delivery
Tracekit never merges or deploys the pull request. Your repository checks and approval rules stay in control.
Administrator notification
Tracekit emails verified organization administrators after pull request creation. The email includes details for review.
From production evidence to code review
Your team starts each remediation and keeps the final decision.
Connect GitHub
An organization administrator installs the Tracekit GitHub App and selects the repositories Tracekit can access.
Map the service
Choose the repository, base branch, and optional source root for each OpenTelemetry service.
Choose the evidence
Open an anomaly or error trace, then select Create fix. Tracekit requires remediation.create and an active service mapping.
Review the pull request
Tracekit opens a pull request when a code fix is useful. Your team reviews the change and repository checks.
Designed for review before merge
Tracekit prepares the change. GitHub keeps your code review, repository checks, approval rules, and deployment process in place.
Repository safeguards
Clear boundaries for every remediation run
- Reads files through GitHub APIs
- Does not clone repositories
- Does not execute customer code
- Never merges or deploys changes
- Blocks GitHub workflow changes
- Keeps access inside the configured source root
Move from evidence to a reviewable fix
Connect GitHub, map your services, and create a fix from the next actionable anomaly or error trace.