Services
Create and manage services in BlameTrail — the foundation for monitors, deploys, and incident tracking.
A service is the top-level object in BlameTrail. It represents a deployable unit that your team owns — an API, a website, a background worker, or any other component. Monitors, deploys, and incidents all belong to a service.
Creating a service
- Navigate to Services in the sidebar.
- Click Add Service.
- Fill in the required and optional fields:
| Field | Required | Description |
|---|---|---|
| Name | Yes | A human-readable label (e.g., payments-api, marketing-site). |
| Environment | Yes | production, staging, or development. |
| Type | Yes | web, api, worker, database, or internal. |
| URL | No | The base URL of the service. Used for reference; monitors have their own URLs. |
| Repository | No | A GitHub repository (e.g., org/repo). Enables commit enrichment for deploys. |
- Click Save.
Deploy webhook token
When you create a service, BlameTrail automatically generates a deploy webhook token. This token authenticates deploy events sent from your CI/CD pipeline.
The token is displayed once on creation. Copy it and store it as a secret in your CI/CD system (e.g., a GitHub Actions secret). If you lose the token, you can rotate it from the service detail page — this immediately invalidates the previous token.
See Quickstart for a CI/CD integration example.
Repository linking
Linking a GitHub repository to a service enables deploy enrichment. When BlameTrail receives a deploy event for a linked service, it automatically fetches:
- Full commit messages
- Pull request titles and numbers
- Changed files and diffs
This metadata is surfaced in suspect scoring and commit analysis, giving your team more context when investigating incidents.
To link a repository, enter the repository identifier (e.g., org/repo) in the Repository field when creating or editing the service. Your organization must have a GitHub token configured in Organization > Integrations for enrichment to work.
Editing a service
- Open the service from the Services list.
- Update any fields.
- Click Save.
Changing the environment or type does not affect existing monitors or incidents. Updating the repository will apply enrichment to future deploys.
Deleting a service
Deleting a service permanently removes it along with all associated monitors, deploys, and incidents. This action cannot be undone.
- Open the service from the Services list.
- Click Delete Service.
- Confirm the deletion.
Core Concepts
Understand the key building blocks of BlameTrail — services, monitors, deploys, incidents, suspect scoring, commit analysis, fix proposals, notifications, on-call paging, postmortems, and status pages.
Monitors
Configure HTTP health checks to detect outages and latency issues automatically.