Why Linear?
Linear is ideal for teams that want to track data issues alongside their engineering work:- Automatic issue creation: Schema changes become trackable issues
- Team assignment: Route issues to the right team automatically
- Priority management: Set priority based on alert severity
- Integration with workflows: Issues flow through your existing Linear workflow
Prerequisites
Before you begin:- Linear account with API access
- Permission to create API keys in Linear
- A Linear team where issues will be created
Setup Guide
Step 1: Create a Linear API Key
In Linear:- Click your avatar in the bottom-left corner
- Select Settings
- Go to API in the left sidebar
- Click Create new API key
- Give it a descriptive name (e.g., “AnomalyArmor Integration”)
- Copy the API key
Step 2: Find Your Team ID
In Linear:- Go to the team where you want issues created
- Look at the URL:
https://linear.app/your-workspace/team/ABC/... - The Team ID is the short code after
/team/(e.g.,ABCorDATA)
Step 3: Add Destination in AnomalyArmor
- Log in to AnomalyArmor
- Click Alerts in the left sidebar
- Select Destinations tab
- Click Add Destination
- Select Linear
Step 4: Configure the Destination
Enter the following:| Field | Description | Required |
|---|---|---|
| Name | A descriptive name (e.g., “Linear - Data Team”) | Yes |
| API Key | The API key from Step 1 | Yes |
| Team ID | The team identifier from Step 2 | Yes |
| Project ID | Target project for issues | No |
| Label IDs | Comma-separated label IDs to auto-apply | No |
| Priority | Default issue priority (0-4) | No |
Step 5: Test the Connection
Click Test to create a test issue in Linear.Remember to close or delete the test issue to keep your backlog clean.
Step 6: Save
Click Create Destination to complete the setup.Issue Format
AnomalyArmor creates Linear issues with:| Field | Value |
|---|---|
| Title | Alert title with context |
| Description | Full alert details including asset and change info |
| Team | Your configured team |
| Priority | Based on alert type or your default setting |
| Labels | Any labels you configured |
Priority Mapping
Linear uses 0-4 priority scale:| Priority | Meaning |
|---|---|
| 0 | No priority |
| 1 | Urgent |
| 2 | High |
| 3 | Medium |
| 4 | Low |
Best Practices
Create Focused Alert Rules
Create specific alert rules for Linear to avoid issue overload: Production Schema Issues- Event: Schema Change
- Scope: production databases only
- Conditions: Column removed OR type changed
- Destination: Linear - Data Team
Use Labels for Categorization
Configure label IDs to automatically categorize issues:data-quality- for freshness violationsschema-change- for schema drift alertsurgent- for critical production issues
Combine with Real-Time Notifications
Use Linear for tracking alongside real-time notifications: Critical Data Issues- Destinations: Slack (immediate notification), Linear (issue tracking)
Troubleshooting
”Invalid API key”
Cause: The API key is incorrect or revoked. Fix:- Generate a new API key in Linear settings
- Update the destination in AnomalyArmor
”Team not found”
Cause: Invalid team ID or API key lacks access to the team. Fix:- Verify the team ID in the Linear URL
- Ensure the API key has access to the workspace containing the team
Issues not appearing
Cause: API key permissions or team configuration. Fix:- Verify the API key has write access
- Check the team exists and is active
- Use the Test button to verify connectivity
Security
Data Sent to Linear
Issue content includes:- Asset names (database, schema, table names)
- Change types and descriptions
- Timestamps
- Alert rule information
- Actual data values
- Database credentials
- Connection strings
Revoking Access
To disconnect AnomalyArmor from Linear:- In AnomalyArmor: Delete the Linear destination
- In Linear: Revoke the API key in Settings > API
Next Steps
Alert Rules
Create rules that route to Linear
Slack
Add real-time notifications alongside Linear tracking
