Linear → Panaptico Integration Guide

Work with Panaptico from Linear

Use Panaptico's IT management capabilities directly with Linear by importing issues or mentioning @Panaptico in comments for incident investigation and infrastructure automation.

Installation

You must be a Panaptico admin to connect the Linear integration. Other team settings are available to non-admin members.

Setup Steps

Go to Panaptico Integrations page
Click "Connect" next to Linear
Authorize Panaptico to access your Linear workspace
Select default team for issue synchronization
Click "Authorize"
Complete remaining setup in Panaptico:
- Connect IT accounts (if not already connected)
- Configure incident response preferences
- Set up notification channels

Account Linking

First use prompts account linking between Panaptico and Linear.

How to Use

Import Linear issues into Panaptico or mention @Panaptico in comments. Panaptico analyzes issues and automatically investigates AWS-related incidents.

Importing Issues

Open Linear issue
Copy issue ID (e.g., OPS-123)
In Panaptico: "Import Linear OPS-123"
Panaptico links to existing issue without duplication

Mentioning Panaptico

Mention @Panaptico in a comment to trigger investigation or provide additional context, for example: "@Panaptico investigate why users can't access EC2 instances in us-east-1".

Workflow

Panaptico provides real-time investigation updates in Linear comments and can autonomously fix issues when authorized. Track detailed progress in Panaptico dashboard.

Investigation Capabilities

When Panaptico investigates a Linear issue, it:

Analyzes CloudTrail logs for recent changes
Checks IAM permissions and policies
Examines CloudWatch metrics and logs
Identifies root causes and patterns
Suggests or applies fixes
Updates Linear with findings

Example Investigation

Linear Issue: "Dario can't create S3 buckets"

Panaptico Response:

Investigating Linear OPS-456...

Initial finding: Missing s3:CreateBucket permission
→ Digging deeper...

Discovered:
- Policy removed during "Q4 Security Audit" 2 hours ago
- Dario is part of 3 groups, all had S3 permissions reduced
- 17 other users affected but haven't reported yet
- This is the 3rd time this month permissions were over-restricted

Root cause: Overly aggressive security audit
Systemic issue: No validation process for permission removals

Fix options:
1. Re-attach S3FullAccess policy
2. Create custom policy with s3:CreateBucket
3. Add to S3Admins group

Autonomous Mode

Grant Panaptico permission to work independently by commenting:

"@Panaptico work on it yourself" - Full autonomous investigation and remediation
"@Panaptico investigate and update Linear" - Investigation only, updates Linear with findings
"@Panaptico fix this and create subtasks" - Fix issue and create Linear subtasks for follow-up

Linear Actions

Panaptico can perform these Linear operations:

Add comments: Investigation findings, progress updates
Create sub-issues: Break down complex problems
Update status: Mark as investigating, blocked, resolved
Set priority: Adjust based on impact assessment
Add labels: Tag with AWS service, incident type
Link issues: Connect related incidents
Attach evidence: CloudWatch graphs, logs (as links)

Configuration

Configure Panaptico behavior from Dashboard → Integrations → Linear.

| Setting | Location | Description | |-------------------|---------------------|-------------------------------------------| | Default Team | Panaptico Dashboard | Primary Linear team for issue creation | | Auto-investigate | Panaptico Dashboard | Automatically investigate imported issues | | Fix Authorization | Panaptico Dashboard | Permission level for autonomous fixes | | Update Frequency | Panaptico Dashboard | How often to sync findings to Linear |

Configuration Options

Configure Panaptico behavior using several methods:

Issue description or comments: Use [key=value] syntax

@panaptico investigate [region=us-west-2]
@panaptico fix [auto-approve=true] [notify=security-team]

Issue labels: Apply labels for common configurations

aws-incident - Triggers immediate investigation
auto-fix - Allows autonomous remediation
security-critical - Escalates to security team

Supported configuration keys:

region: AWS region to focus investigation
service: Specific AWS service (ec2, s3, iam, etc.)
auto-approve: Allow fixes without confirmation
depth: Investigation depth (basic, deep, forensic)

Incident Types Supported

Permission Issues: IAM policy problems, access denied errors
Performance Problems: High latency, resource constraints
Security Incidents: Suspicious activity, compliance violations
Cost Anomalies: Unexpected charges, resource waste
Service Outages: Availability issues, failed deployments
Configuration Errors: Misconfigurations, drift detection

Best Practices

Clear Issue Titles: Include service name and symptom (e.g., "RDS connection timeouts in prod")
Provide Context: Include error messages, timestamps, affected resources
Use Labels: Tag with AWS service for faster routing
Set Priority: P1 for outages, P2 for degradation, P3/P4 for non-critical
Follow Up: Review Panaptico's findings and approve fixes

Privacy & Security

Panaptico only accesses AWS resources you've authorized
Investigation logs are retained for 90 days
No AWS credentials are stored in Linear
All communications are encrypted
Audit trail maintained for all actions

Troubleshooting

Issue not importing?

Verify Linear integration is active
Check issue ID format (TEAM-123)
Ensure you have access to the issue

Investigation not starting?

Confirm AWS credentials are connected
Check if issue contains AWS-related content
Verify Panaptico has necessary permissions

Updates not appearing in Linear?

Check Linear API rate limits
Verify webhook configuration
Ensure Linear user has comment permissions

Ready to Get Started?

Start by visiting your Panaptico dashboard to enable the Linear integration and begin streamlining your AWS incident management workflow.

Need help? Contact support at support@panaptico.com