VRS Monitoring & Diagnostics Dashboard

Display active recorder status. (Multiple MediaServer status visible somewhere)
Show recorder/resource utilization. (Docker stats, Linux stats visible somewhere)(Storage etc)
Surface service health and errors. (Healthcheck visible somewhere) (Containers Error logs and also Fix (trouble shoot guide))
Monitor indexing and recording status. ( Number of calls, call status, number of archived calls, active calls) (failed correlation)
Provide tracing/logging to investigate missing call recordings reported by agents.
Trouble Shoot Documentation

#	Customer Requirement	Solution Scope	Feedback	Effort
1	Active recorder status (multiple MediaServer status visible)	Live status panel per FreeSwitch MediaServer/recorder instance: up/down, registered channels, active recordings, last heartbeat.		Design, ESL exporter dev, Adding to Dashboard and testing.
2	Recorder / resource utilization (Docker & Linux stats, storage)	Per-container CPU/memory/network/disk panels; host-level CPU, memory, disk, storage capacity & trend forecasting.		Design, cAdvisor/Node Exporter setup, Dashboard panels, Testing
3	Service health, container error logs, troubleshooting	Aggregated health-check board per service; searchable error-log explorer.		Design, cAdvisor/Node Exporter setup, Dashboard panels, Testing
4	Indexing & recording status monitoring	Dashboards for call volume, call status breakdown, active vs. archived calls, and a dedicated failed-correlation view (recorded but not correlated).		Design, Correlation engine (call/recording/index reconciliation logic), Dashboard views, Testing:
5	Tracing/logging for missing recordings	Call-ID based trace view, recorder logs, mixing logs and correlation logs into one timeline.	audio is breaking/dropping packets. can be traced from here? agent wise stats in %age.	Design, Trace/timeline builder (log stitching), RTP/packet-loss metric capture (addresses feedback), Agent-wise % stats module (addresses feedback) Testing This task include Rnd as well timeline for this task may vary.
6	Troubleshooting documentation	Structured, versioned runbook library, cross-linked from every alert/error surfaced in the dashboard.		Content drafting, Linking to dashboard/alerts, Review.