Monitoring
Track your deployments in real-time to ensure successful execution.
Deployment Dashboard
Section titled “Deployment Dashboard”The deployment detail page provides monitoring:
┌─────────────────────────────────────────────────────────────┐│ Deployment: customer-portal v1.3.0 → Production │├─────────────────────────────────────────────────────────────┤│ ││ Status: ● In Progress Started: 2 min ago ││ Progress: ████████████░░░░░░░░ 60% ││ ││ ───────────────────────────────────────────────────────── ││ ││ Targets: ││ ┌────────────────┬──────────┬─────────────────────────┐ ││ │ Target │ Status │ Current Step │ ││ ├────────────────┼──────────┼─────────────────────────┤ ││ │ web-prod-01 │ ✓ Done │ Completed │ ││ │ web-prod-02 │ ✓ Done │ Completed │ ││ │ web-prod-03 │ ● Running│ deploy-backend (2/3) │ ││ │ web-prod-04 │ ○ Pending│ Waiting │ ││ └────────────────┴──────────┴─────────────────────────┘ ││ ││ [View Logs] [Cancel] ││ │└─────────────────────────────────────────────────────────────┘Status Indicators
Section titled “Status Indicators”Deployment Status
Section titled “Deployment Status”| Status | Icon | Description |
|---|---|---|
| Pending | ○ | Waiting to start |
| Queued | ◔ | In dispatch queue |
| Running | ● | Currently executing |
| Success | ✓ | Successfully finished |
| Failed | ✗ | Execution failed |
| Cancelled | ⊘ | Manually cancelled |
| RollingBack | ↺ | Rollback in progress |
| RolledBack | ↩ | Rolled back |
Target Status
Section titled “Target Status”| Status | Description |
|---|---|
| Pending | Waiting for turn |
| Queued | Step is queued on the target |
| Running | Currently executing |
| Completed | Successfully finished |
| Failed | Execution failed |
| Skipped | Skipped due to earlier failure |
| Cancelled | Cancelled by user or system |
Progress Tracking
Section titled “Progress Tracking”Overall Progress
Section titled “Overall Progress”Progress: ████████████░░░░░░░░ 60% (6 of 10 steps)The progress bar shows:
- Percentage complete
- Steps completed vs total
- Visual progress indicator
Per-Target Progress
Section titled “Per-Target Progress”Each target shows its current step:
┌─────────────────────────────────────────────────────────────┐│ web-prod-03: Running │├─────────────────────────────────────────────────────────────┤│ ││ Solution: customer-portal v1.3.0 ││ Environment: Production ││ ││ Sequences: ││ 1. ✓ run-migrations (completed in 45s) ││ 2. ● deploy-backend (running - step 2 of 4) ││ 3. ○ deploy-frontend (pending) ││ ││ Current Action: copy-files ││ Duration: 23 seconds ││ │└─────────────────────────────────────────────────────────────┘Execution Flow Visualization
Section titled “Execution Flow Visualization”Parallel Execution View
Section titled “Parallel Execution View”Sequential Execution View
Section titled “Sequential Execution View”Rolling Execution View
Section titled “Rolling Execution View”Batch 1: ✓ Complete (web-01, web-02)Batch 2: ● Running (web-03, web-04)Batch 3: ○ Pending (web-05, web-06)Real-Time Updates
Section titled “Real-Time Updates”Deployments update in real-time without page refresh:
Update Types
Section titled “Update Types”| Update | Trigger |
|---|---|
| Status change | Target starts/completes/fails |
| Progress update | Step completion |
| Log output | Command execution output |
| Error notification | Failure detected |
Connection Status
Section titled “Connection Status”┌──────────────────────────────────┐│ ● Connected - Live updates │└──────────────────────────────────┘If disconnected:
┌──────────────────────────────────┐│ ○ Reconnecting... │└──────────────────────────────────┘Failure Monitoring
Section titled “Failure Monitoring”Failure Indicators
Section titled “Failure Indicators”┌─────────────────────────────────────────────────────────────┐│ Deployment Failed │├─────────────────────────────────────────────────────────────┤│ ││ ✗ web-prod-03 failed at step: deploy-backend ││ ││ Error: Command exited with code 1 ││ Action: copy-files ││ Duration: 12 seconds ││ ││ ┌───────────────────────────────────────────────────────┐ ││ │ rsync: connection unexpectedly closed │ ││ │ rsync error: error in rsync protocol data stream │ ││ │ (code 12) at io.c(235) [sender=3.2.3] │ ││ └───────────────────────────────────────────────────────┘ ││ ││ [View Full Logs] [Retry] [Cancel] ││ │└─────────────────────────────────────────────────────────────┘Failure Impact
Section titled “Failure Impact”Based on failure strategy:
| Strategy | Result |
|---|---|
| Stop | Remaining targets skipped |
| Continue | Other targets proceed |
| Ignore | Continues as if succeeded |
Metrics and Statistics
Section titled “Metrics and Statistics”Deployment Metrics
Section titled “Deployment Metrics”| Metric | Description |
|---|---|
| Total Duration | Time from start to finish |
| Target Count | Number of targets |
| Success Rate | Percentage successful |
| Average Duration | Mean deployment duration (ms) |
Target Metrics
Section titled “Target Metrics”| Metric | Description |
|---|---|
| Start Time | When target began |
| End Time | When target completed |
| Duration | Total execution time |
| Steps Completed | Number of steps run |
History and Timeline
Section titled “History and Timeline”Deployment Timeline
Section titled “Deployment Timeline”┌─────────────────────────────────────────────────────────────┐│ Timeline │├─────────────────────────────────────────────────────────────┤│ ││ 14:30:00 Deployment created by admin ││ 14:30:01 Started on web-prod-01, web-prod-02 ││ 14:30:45 web-prod-01 completed ││ 14:31:02 web-prod-02 completed ││ 14:31:03 Started on web-prod-03, web-prod-04 ││ 14:31:45 web-prod-03 failed: copy-files ││ 14:31:46 Deployment stopped (failure strategy: stop) ││ │└─────────────────────────────────────────────────────────────┘Event Types
Section titled “Event Types”| Event | Description |
|---|---|
| Created | Deployment initiated |
| Started | Execution began on target |
| Step Complete | Individual step finished |
| Target Complete | All steps done on target |
| Target Failed | Error on target |
| Cancelled | User cancelled deployment |
| Completed | All targets finished |
Monitoring Dashboard Widget
Section titled “Monitoring Dashboard Widget”The main dashboard shows active deployments:
┌─────────────────────────────────────────────────────────────┐│ Active Deployments │├─────────────────────────────────────────────────────────────┤│ ││ ┌────────────────────────┬──────────┬────────────────┐ ││ │ Deployment │ Progress │ Status │ ││ ├────────────────────────┼──────────┼────────────────┤ ││ │ customer-portal v1.3.0 │ 60% │ ● In Progress │ ││ │ auth-service v2.0.0 │ 100% │ ✓ Completed │ ││ │ worker v1.5.0 │ 25% │ ● In Progress │ ││ └────────────────────────┴──────────┴────────────────┘ ││ │└─────────────────────────────────────────────────────────────┘Notifications
Section titled “Notifications”In-App Notifications
Section titled “In-App Notifications”┌──────────────────────────────────────────────────┐│ ✓ Deployment Complete: customer-portal v1.3.0 ││ to Production (12 targets) ││ [View] [×] │└──────────────────────────────────────────────────┘Notification Events
Section titled “Notification Events”| Event | Notification |
|---|---|
| Deployment complete | Success message |
| Deployment failed | Error with details |
| Client registration pending | Action required |
Best Practices
Section titled “Best Practices”1. Monitor Actively
Section titled “1. Monitor Actively”Stay on the deployment page during critical deployments:
- Watch for failures
- Be ready to cancel if needed
- Monitor resource impact
2. Set Appropriate Timeouts
Section titled “2. Set Appropriate Timeouts”Configure reasonable timeouts to detect hung operations:
Step timeout: 300 seconds- Too short: False failures- Too long: Delayed failure detection3. Use Rolling Deployments
Section titled “3. Use Rolling Deployments”For better monitoring:
- Smaller batches = easier to track
- More time to react to failures
- Clear progress visibility
4. Review History
Section titled “4. Review History”After completion, review:
- Total duration
- Any slow steps
- Error patterns
- Success rate
Troubleshooting
Section titled “Troubleshooting”Updates Not Appearing
Section titled “Updates Not Appearing”Cause: SSE (Server-Sent Events) connection lost
Solution: Refresh the page to reconnect. Live monitoring streams over an
open HTTP text/event-stream connection (server-to-client); reconnection
happens over normal HTTP.
Progress Stuck
Section titled “Progress Stuck”Cause: Long-running step or timeout
Solution: Check target logs for current activity
Status Shows Unknown
Section titled “Status Shows Unknown”Cause: Connection issue with Thorax
Solution: Verify Thorax is running and accessible
Next Steps
Section titled “Next Steps”- Log Streaming - View real-time logs
- Cancellation - Stop deployments
- Troubleshooting - Resolve issues
- Overview - Return to deployments overview
