Overview
The Inbox is Metoro’s way of telling you when you need to take action. It’s designed to be as low-noise as possible, surfacing only significant issues that require your attention.Accessing the Inbox
Navigate to Inbox in the main navigation or go directly to your Inbox.What Appears in the Inbox
The Inbox surfaces items from multiple sources that require action:| Source | Item Types |
|---|---|
| Guardian AI | Bugs detected, suggested fixes, investigation findings |
| Issue Detection | OOM events, CPU throttling, right-sizing recommendations |
| Anomaly Detection | Error rate spikes, latency anomalies |
| Deployment Verification | Failed verifications, breaking changes detected |
| Configuration | Setup issues, integration problems |
Items in the Inbox are curated to be actionable. We intentionally keep it low-noise so that when something appears, it’s worth your attention.
Working with Inbox Items
Reviewing Items
- Click on an inbox item to view full details
- Review the summary and any investigation details
- Check the suggested actions
Applying Fixes
When a fix is suggested:- Review the proposed changes
- Click Accept to apply the fix (creates a PR for code changes)
- Or click Dismiss if the fix isn’t appropriate
Managing Items
- Resolve - Mark an item as resolved after addressing it
- Dismiss - Remove an item if it’s not relevant
- Snooze - Temporarily hide an item to address later
Inbox Notifications
You can configure notifications to alert you when new items appear in your inbox.Setting Up Notifications
- Navigate to Settings → Features → Inbox Notifications
- Click Add Notification Configuration
- Configure your notification rules
Notification Filtering
Items are tagged with metadata you can use for routing:| Tag | Description | Example |
|---|---|---|
service | The affected service | payment-service |
environment | The environment | prod |
severity | Issue severity | critical, high, medium, low |
type | Type of issue | bug, security, performance, resource |
source | Where the item came from | guardian, issue-detection, anomaly-detection |
Example Configuration
Route inbox items to the team responsible for the affected service:- Service-Based Routing
- Severity-Based Routing
- Source-Based Routing
- Combined Filters
Config 1:
- Filter:
service = payment-service - Destination:
#payments-team
- Filter:
service = auth-service - Destination:
#identity-team
Inbox Philosophy
The Inbox is designed with these principles:Low Noise
We only surface items that truly need attention. You shouldn’t be overwhelmed with notifications—when something appears in your inbox, it matters.Actionable
Items should be actionable. We try to provide not just information about problems, but concrete steps to resolve them.Smart Routing
Use notification configurations to route items to the right people. This ensures the team responsible for a service gets notified about issues affecting their service.Best Practices
Check Regularly
Make the Inbox part of your workflow. Check it regularly to stay on top of issues.Configure Notifications
Set up notifications so critical issues reach you immediately:- Critical issues → immediate notification to incidents channel
- Lower severity → daily digest or general channel
Review Suggested Fixes
When a fix is suggested:- Understand the root cause first
- Review the proposed changes carefully
- Test in a non-production environment if possible
- Apply and monitor the results
Provide Feedback
If suggestions aren’t helpful:- Dismiss unhelpful items
- Reach out to our team with feedback
- This helps us improve the system