Skip to content

CloudMonitor v2.0.0 — Major Observability & Docker Monitoring Update

Latest

Choose a tag to compare

@ayushcmd ayushcmd released this 21 Nov 03:07
· 14 commits to main since this release
5b96531

CloudMonitor v2.0.0 — Major Observability & Docker Monitoring Update

CloudMonitor v2.0.0 expands the self-hosted monitoring platform with richer dashboards, historical Docker telemetry, streamlined local agent onboarding, and additional security and reliability safeguards.

This release includes the changes in PR #29, along with subsequent documentation updates such as PR #31. This release is a source-code publication, not confirmation that every feature is live on the AWS demonstration environment.

Highlights

Observability dashboards

  • New Host, API Performance, Prometheus Health, and Docker Containers monitoring views.
  • Historical time-series charts, KPI summaries, manual refresh, and selectable 15-minute, 1-hour, 6-hour, and 24-hour windows.
  • Authenticated backend monitoring endpoints and bounded Prometheus queries instead of direct public browser access to Prometheus.
  • More informative chart states and display of unavailable measurements instead of misleading zero values.

Docker history and telemetry

  • Persistent, timestamped container CPU and memory readings, network receive/transmit counters, block read/write counters, and lifecycle or health information.
  • Agent- and container-scoped history queries and timeline events.
  • New Alembic migration 004_container_history for historical metric samples and associated indexes.
  • Improved differentiation between running, offline, stale, unhealthy, and removed containers.

Docker agent onboarding

  • Guided setup for local Docker agent provisioning in trusted development environments, including agent reuse, startup verification, and troubleshooting feedback.
  • Updated install command generation and manual enrollment options for remote hosts.
  • Additional validation and safeguards around provisioning permissions, concurrency, credentials, and tenant boundaries.

Security and reliability

  • Strengthened authentication/authorization for monitoring and provisioning endpoints.
  • Tenant-scoped access to container telemetry and history.
  • Restricted direct Prometheus exposure and routing of supported monitoring requests through backend APIs.
  • Better handling of incomplete container reports, missing telemetry, and transient connection states.

Testing and documentation

  • Added or expanded tests for monitoring dashboards, Docker agent connection status, telemetry history, local provisioning, and security regressions.
  • Updated production security audit documentation.
  • Clarified the three team workstreams—Backend & Monitoring API, Frontend & Dashboard, and AWS Cloud & DevOps—in PR #31.
  • Prepared the README release overview and contributor profile links in PR #32.

Upgrade notes

  1. Database: Back up existing PostgreSQL data and apply Alembic migrations, including 004_container_history, before relying on historical container views.
  2. Docker agent: Check host Docker access and socket privileges, refresh agent images where applicable, and confirm enrollment credentials are handled securely. Local automatic provisioning is intended only for trusted development setups; use manual enrollment for remote hosts.
  3. Monitoring: Verify connectivity to Prometheus and exporters, authenticated metrics queries, and access restrictions for monitoring endpoints after deployment.
  4. Deployment: Preserve .env secrets, persistent database volumes, and deployment-specific configurations when updating containers. Validate local and AWS environments separately; the release does not automatically deploy to EC2.
  5. Tests: Run backend/agent regression checks, frontend build, and Docker Compose validation in your target environment before deploying the new version.

Changes and contributors

Team workstreams: Sarnendu Das (Backend & Monitoring API), Parveen Kumar (Frontend & Dashboard), and Ayush Raj (AWS Cloud Infrastructure, DevOps & Observability).

Scope and limitations

CloudMonitor remains an academic/self-hosted monitoring project. Feature availability depends on the deployed services and their configuration. This GitHub release does not by itself deploy source changes to AWS or certify production readiness.