Installation & Setup
Installation & Setup
Section titled “Installation & Setup”Complete guide to installing and configuring the Overwatch Chrome Extension for your monitoring platforms.
Installation Methods
Section titled “Installation Methods”Chrome Web Store Installation (Recommended)
Section titled “Chrome Web Store Installation (Recommended)”The easiest way to install the extension is through the Chrome Web Store:
-
Open Chrome Web Store
- Navigate to the Chrome Web Store
- Search for “Overwatch Platform Extension”
-
Add to Chrome
- Click the “Add to Chrome” button
- Review the required permissions
-
Confirm Installation
- Click “Add extension” in the confirmation dialog
- Wait for installation to complete
-
Verify Installation
- The Overwatch icon should appear in your Chrome toolbar
- Icon will be grayed out until configured
Advantages:
- Automatic updates
- Verified and secure
- One-click installation
- No manual file management
Manual Installation (For Development)
Section titled “Manual Installation (For Development)”For development or custom builds, install the extension manually:
-
Download Extension Package
- Obtain the extension package from your administrator
- Or build from source:
npm run build:dev(development) ornpm run build:prod(production)
-
Enable Developer Mode
- Open Chrome → Settings → Extensions
- Or navigate to
chrome://extensions/ - Toggle “Developer mode” in the top right
-
Load Unpacked Extension
- Click “Load unpacked” button
- Navigate to the extension directory
- Select
extension/build/dev(development) orextension/build/prod(production)
-
Verify Installation
- Extension should appear in the list
- Toggle it on if disabled
- Overwatch icon appears in toolbar
When to Use:
- Testing development builds
- Using custom organization builds
- Contributing to extension development
- Local platform testing (localhost integrations)
Initial Configuration
Section titled “Initial Configuration”Step 1: Extension Activation
Section titled “Step 1: Extension Activation”After installation, configure your Overwatch connection:
-
Open Extension Popup
- Click the Overwatch icon in Chrome toolbar
- Or use keyboard shortcut:
Ctrl+Shift+O(Cmd+Shift+O on Mac)
-
Enter Organization URL
- Enter your Overwatch instance URL
- Format:
https://your-org.overwatch.com - Click “Connect”
-
Authenticate
- Enter your Overwatch credentials
- Or use Single Sign-On if configured
- Click “Sign In”
-
Verify Connection
- Extension icon should turn green
- Connection status: “Connected”
- Your organization name should display
Organization Settings:
{ "organization_url": "https://your-org.overwatch.com", "api_endpoint": "/api/v1", "websocket_endpoint": "/ws", "auto_connect": true}Step 2: Platform Permissions
Section titled “Step 2: Platform Permissions”Grant permissions for each monitoring platform you use:
-
Navigate to Platform
- Open your monitoring platform (e.g., Datadog)
- Extension will detect the platform automatically
-
Grant Permissions
- Click “Allow” when prompted
- Review requested permissions
- Confirm platform access
-
Configure Detection
- Enable automatic alert detection
- Configure which data to extract
- Set notification preferences
-
Test Detection
- Navigate to an alert or dashboard
- Extension should detect context
- Verify extracted data is accurate
Supported Platforms:
- ✅ Datadog (app.datadoghq.com)
- ✅ New Relic (one.newrelic.com)
- ✅ Grafana Cloud (grafana.com)
- ✅ PagerDuty (app.pagerduty.com)
- ✅ SigNoz Cloud (signoz.io)
- ✅ Elasticsearch Cloud
- ✅ Kibana (cloud.elastic.co)
- ✅ Sentry (sentry.io)
- ✅ Honeycomb (ui.honeycomb.io)
Step 3: Verification
Section titled “Step 3: Verification”Verify extension is working correctly:
-
Check Connection Status
- Extension icon should be green
- Tooltip should show “Connected”
-
Test Platform Detection
- Navigate to a known monitoring platform
- Open an alert or dashboard
- Extension should detect context
-
Test Incident Creation
- Click extension icon on alert page
- Verify context is extracted
- Test “Create Incident” button
-
Verify Backend Communication
- Open browser DevTools (F12)
- Go to Console tab
- Look for “Overwatch Extension” logs
- Should see successful API calls
Platform-Specific Setup
Section titled “Platform-Specific Setup”Datadog Setup
Section titled “Datadog Setup”Enable Datadog Integration:
- Navigate to Datadog (app.datadoghq.com)
- Open any alert or dashboard
- Click Overwatch extension icon
- Select “Enable Datadog Integration”
- Configure extraction settings:
- ✅ Auto-detect alerts
- ✅ Extract metrics
- ✅ Extract logs
- ❌ Capture screenshots (optional)
- Click “Save Settings”
What Gets Extracted:
- Alert name, severity, status
- Affected hosts and services
- Metric values and thresholds
- Log messages and timestamps
- Dashboard context and URLs
New Relic Setup
Section titled “New Relic Setup”Enable New Relic Integration:
- Navigate to New Relic (one.newrelic.com)
- Open any error or APM page
- Click Overwatch extension icon
- Select “Enable New Relic Integration”
- Configure extraction settings:
- ✅ Auto-detect errors
- ✅ Extract traces
- ✅ Extract stack traces
- ✅ Capture screenshots
- Click “Save Settings”
What Gets Extracted:
- Error class and message
- Stack traces and affected code
- Transaction details
- Performance metrics
- User impact data
Grafana Setup
Section titled “Grafana Setup”Enable Grafana Integration:
- Navigate to Grafana (your-instance.grafana.com)
- Open any dashboard
- Click Overwatch extension icon
- Select “Enable Grafana Integration”
- Configure extraction settings:
- ✅ Auto-detect alerts
- ✅ Extract panel data
- ✅ Extract time series
- ✅ Capture screenshots
- Click “Save Settings”
What Gets Extracted:
- Dashboard and panel titles
- Alert rules and status
- Metric queries (PromQL, LogQL)
- Time range and variables
- Annotation and events
PagerDuty Setup
Section titled “PagerDuty Setup”Enable PagerDuty Integration:
- Navigate to PagerDuty (app.pagerduty.com)
- Open any incident
- Click Overwatch extension icon
- Select “Enable PagerDuty Integration”
- Configure extraction settings:
- ✅ Auto-sync incidents
- ✅ Extract escalation policy
- ✅ Extract timeline
- Click “Save Settings”
What Gets Extracted:
- Incident ID and title
- Service and escalation policy
- Assigned team members
- Timeline and activity log
- Related alerts
Browser Compatibility
Section titled “Browser Compatibility”Supported Browsers
Section titled “Supported Browsers”Google Chrome (Version 88+)
- Full feature support
- Best performance
- Automatic updates
- All platforms supported
Microsoft Edge (Version 88+, Chromium-based)
- Full feature support
- Excellent compatibility
- Same features as Chrome
Brave Browser (Version 1.20+)
- Full feature support
- Privacy-focused
- Chrome extension compatible
Opera (Version 74+)
- Full feature support
- Chrome extension compatible
Firefox
- Not currently supported
- Different extension architecture
- Requires separate build
Safari
- Not currently supported
- Different extension APIs
- Requires native implementation
Mobile Browsers
- Not supported
- Extension architecture limitations
Known Limitations
Section titled “Known Limitations”- Firefox and Safari are not currently supported
- Some features require specific Chrome APIs not available in other browsers
- Mobile browsers are not supported due to extension architecture
- Requires Chrome 88+ or equivalent Chromium-based browser
Post-Installation Checklist
Section titled “Post-Installation Checklist”After installation, verify these items:
- Extension icon visible in Chrome toolbar
- Connection status shows “Connected”
- Organization name displays correctly
- At least one platform integration enabled
- Test incident creation works
- Browser console shows no errors
- Extension version matches expected (v2.0+)
- Keyboard shortcuts work (test
Ctrl+Shift+O)
Troubleshooting Installation
Section titled “Troubleshooting Installation”Extension Not Appearing
Section titled “Extension Not Appearing”Symptoms: Extension icon not visible in toolbar
Solutions:
- Check if extension is enabled in chrome://extensions/
- Pin extension to toolbar (click puzzle icon → pin)
- Restart Chrome browser
- Reinstall extension
Permission Errors
Section titled “Permission Errors”Symptoms: “Permission denied” or “Access blocked” errors
Solutions:
- Review requested permissions
- Ensure Chrome version is 88+
- Check organization firewall settings
- Try manual installation method
Connection Failures
Section titled “Connection Failures”Symptoms: “Cannot connect to Overwatch” errors
Solutions:
- Verify organization URL is correct
- Check network connectivity
- Verify Overwatch instance is accessible
- Check browser console for specific errors
- Contact administrator for network configuration
Platform Detection Issues
Section titled “Platform Detection Issues”Symptoms: Extension doesn’t detect monitoring platform
Solutions:
- Verify platform is in supported list
- Check if platform-specific permission granted
- Refresh page and wait for content to load
- Enable platform in extension settings
- Check browser console for errors
Next Steps
Section titled “Next Steps”Now that the extension is installed:
- Configure Settings → - Customize behavior and preferences
- Platform Guides → - Platform-specific usage guides
- On-Demand Reporting → - Learn about problem reporting
- Workflows → - Common usage workflows
Need Help?
Section titled “Need Help?”If you encounter installation issues, contact support@overwatch-observability.com.
Related Documentation:
- Configuration - Extension settings and preferences
- Troubleshooting - Common issues and solutions
- User Guide - Platform usage guide