All checks were successful
Server Tests / Mocha – Unit & Utility Tests (push) Successful in 42s
+ Added public data export API enhancements, tests, and customer documentation + Extended /api/v1 data export endpoints with richer session, records, area, and async export output + Added confirmed/fallback report values, client metadata, mapped area, over-spray, volume/apprate (string) units, and weather blocks + Normalized flowController to "No FC" and align record field names with playback output + Converted record wind speed output to knots, add Fligh Mater only record/export fields behind fm=true, and persist fm on export jobs + Added export status/area constants, HTTP 202 support, route-level API docs, and per-account export rate limiting support + Added comprehensive endpoint, format, and verification test coverage plus test-suite README + Added customer-facing data export design, integration, rate-limit, and documentation index guides + Updated README/DLQ docs and related documentation links to current HTTPS dashboard paths
4.6 KiB
4.6 KiB
DLQ Documentation Index
Navigation: 📖 Index | 🚀 Quick Start | 📚 API Reference | 🔧 Operations | 🏗️ System Guide
Complete documentation for the Dead Letter Queue (DLQ) system.
Quick Links
- 🚀 Quick Start Guide - Get started in 5 minutes
- 📖 API Reference - Complete API documentation
- 🔧 Operations Guide - Advanced operations and troubleshooting
- 🏗️ System Guide - Architecture and internals
Architecture Overview
The DLQ system provides global, queue-native operations for managing failed tasks across all queue types:
flowchart TB
subgraph API["Global DLQ API"]
endpoint["/api/dlq/:queueName/*"]
end
subgraph Queues["Supported Queues"]
pt[partner_tasks]
jobs[dev_jobs]
future[Future queues...]
end
endpoint --> pt
endpoint --> jobs
endpoint --> future
style API fill:#e1f5ff
style Queues fill:#f0f0f0
Supported Queues:
partner_tasks(partner log processing)dev_jobs(job processing)- Any future queue types (notifications, analytics, etc.)
Key Features:
- ✅ Direct RabbitMQ operations (no MongoDB coupling)
- ✅ Supports multiple queue types
- ✅ Preserves original message content
- ✅ Works with any task type
Documentation Structure
Getting Started
- DLQ Quick Start
- Web dashboard access
- Common operations
- API examples
- Troubleshooting basics
API Documentation
- DLQ API Reference
- All endpoints with examples
- Request/response formats
- Authentication
- Error handling
Operations & Maintenance
- DLQ Operations Guide
- Monitoring strategies
- Manual recovery procedures
- Multi-queue operations
- Best practices
- Alert thresholds
System Architecture
- DLQ System Guide
- Architecture overview
- Component details
- Message flow
- Integration patterns
Quick Examples
View DLQ Messages
curl http://localhost:4100/api/dlq/partner_tasks/messages?limit=20 \
-H "Authorization: Bearer $TOKEN"
Retry All Messages
curl -X POST http://localhost:4100/api/dlq/partner_tasks/retryAll \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"maxMessages": 50}'
Multiple Queues
# Partner queue
curl -X POST http://localhost:4100/api/dlq/partner_tasks/retryAll ...
# Job queue
curl -X POST http://localhost:4100/api/dlq/dev_jobs/retryAll ...
# Future queue (no code changes needed!)
curl -X POST http://localhost:4100/api/dlq/notifications/retryAll ...
Tools & Interfaces
Web Dashboard
https://localhost:4100/dlq-monitor.html
- Real-time statistics
- View messages
- One-click retry
- Queue selection
API Integration
curl http://localhost:4100/api/dlq/:queueName/stats \
-H "Authorization: Bearer $TOKEN"
Related Documentation
Archived Documentation
Old partner-specific documentation has been moved to archived/:
- These files document the pre-refactoring implementation
- Kept for historical reference only
- See
archived/README.mdfor migration guide
Change Log
December 19, 2025 - Global DLQ Architecture Refactoring
- Moved from
/api/partners/dlq/*to/api/dlq/:queueName/* - Created new global documentation set
- Archived old PARTNER_DLQ_*.md files
- Support for multiple queue types
Previous - Partner-specific implementation
- See archived documentation for history
Contributing
When updating DLQ documentation:
-
Update the appropriate guide based on change type:
- API changes → Update API Reference
- Operations → Update Operations Guide
- Architecture → Update System Guide
-
Keep examples consistent across all docs
-
Update this index if adding new documentation files
-
Test all curl examples before committing
Support
For questions or issues:
- Check Troubleshooting section
- Review System Guide for architecture details
- Contact: trungh@agnav.com