New features, improvements, and fixes, shipped to all customers automatically.
v1.3.0Feature
Auto Scaling
KubeWatch can now scale your workloads, not just watch them. Define a per-workload policy (thresholds, replica bounds, cooldowns) and the Scaling-Engine acts on the same metrics you already track. The same policy surface drives both runtimes, while what happens underneath fits each: native HorizontalPodAutoscaler and Karpenter objects on Kubernetes, full orchestration on standalone Docker.
Kubernetes: native HPA & Karpenter. For a Kubernetes policy, KubeWatch renders a standard HorizontalPodAutoscaler (and a Karpenter NodePool when node-level scaling is requested) and the in-cluster agent server-side-applies it. The cluster's own controllers execute the scale, so scaling keeps working even if KubeWatch is unreachable.
Docker: orchestrated scaling with a managed load balancer. Standalone Docker has no HPA, so KubeWatch owns the whole loop: it chooses placement by host headroom, scales containers via the Docker Engine, and (optionally) runs a managed Caddy load-balancer pool that health-checks new replicas before sending them traffic.
Dry-run, cooldowns, approvals, and a decision log. Every policy starts in dry-run: it logs exactly what it would do, with the rendered manifest or command, against live data. Asymmetric cooldowns prevent flapping, approval gates hold high-stakes actions for a human, and an append-only decision log answers "why did this scale" after the fact.
One-click rollback. Every action can be rolled back from its history entry. On Kubernetes this cleanly restores the previous scaling envelope; on Docker it restores the previous replica count, with the UI stating plainly when fresh containers will be created.
v1.2.0Feature
Multi-Cluster Dashboard
Monitor all your Kubernetes clusters from a single pane of glass. This release introduces a unified multi-cluster overview, a cluster selector with per-cluster drill-down, and cross-cluster alert aggregation so you can correlate incidents that span multiple environments.
Multi-cluster overview. A new top-level dashboard shows health scores, active alert counts, node readiness, and resource saturation for all registered clusters simultaneously. Clusters are grouped by environment tag (production, staging, development).
Cluster selector. A persistent cluster selector in the top navigation bar lets you switch context instantly. The selector remembers your last-used cluster per browser session and supports keyboard shortcut navigation.
Cross-cluster alert aggregation. Alert rules can now be scoped to "all clusters" or a custom cluster group. Aggregated alerts surface in a unified incident feed with per-cluster breakdowns, so on-call engineers see the full blast radius of a cascading failure at a glance.
Cluster comparison view. Side-by-side metric comparison across up to four clusters makes it easy to verify that a deployment rolled out consistently and that resource usage is symmetric across replicated environments.
Agent v1.2 with multi-cluster identity. The KubeWatch Agent now embeds a cluster identifier in all emitted telemetry. Upgrading to Agent v1.2 is required to use multi-cluster features. Migration is zero-downtime and backward-compatible.
v1.1.0Feature
Alert Engine
A fully redesigned alert engine with threshold-based and rate-of-change rules, native Slack and email integrations, and granular silence rules. Configure once, get notified everywhere your team already works.
Threshold-based alert rules. Define alerts using a YAML-like rule editor or the visual wizard. Conditions support comparison operators (>, >=, <, <=, ==, !=) against any ingested metric. Rules evaluate on configurable windows from 1 minute to 24 hours with configurable consecutive-breach counts to reduce flapping.
Rate-of-change alerts. Alert when a metric increases or decreases by more than a specified percentage over a rolling window. Useful for detecting sudden memory leaks, traffic spikes, or an unexpected drop in request throughput.
Slack integration. Send alert notifications to any Slack channel or DM via an incoming webhook or Bot Token. Notifications include a summary card with severity badge, affected workload, current metric value, and a deep link back to the relevant dashboard panel.
Email notifications. Route alerts to one or more email addresses or distribution lists. Emails are rendered in HTML with an embedded sparkline of the metric over the past hour and a one-click acknowledge link.
Silence rules. Suppress alerts matching a label selector for a defined time window, ideal for planned maintenance. Silences can be created from the alert feed, the rule editor, or the API, and support recurring schedules (e.g., every Sunday 02:00 to 04:00 UTC).
Alert history and audit log. Every alert state transition (firing → resolved, rule created, silence applied) is recorded in an immutable audit log retained for 90 days, giving you a clear post-incident timeline.
v1.0.0Feature
Initial Release
The first public release of KubeWatch. Core support for Docker and Kubernetes monitoring, live log streaming, and a basic alerting foundation. This is the foundation on which everything else is built.
Docker monitoring. Monitor running containers on any Docker-enabled host. Track CPU usage, memory consumption, network receive/transmit rates, block I/O, container uptime, and restart counts. Containers are auto-discovered when the Agent starts and removed from the view automatically on exit.
Kubernetes monitoring. Deploy the Agent as a DaemonSet and immediately gain visibility into node resource usage, pod scheduling events, container restarts, PersistentVolume capacity, and Deployment/StatefulSet/DaemonSet replica health across all namespaces.
Live log streaming. Stream stdout and stderr from any container in real time directly in the dashboard. Supports log filtering by severity keyword or regex, line-count limiting, and pause/resume for reviewing bursts of output. Logs are also indexed and searchable for the duration of your plan's retention window.
Basic alerts. Create simple threshold alerts on CPU, memory, and restart-count metrics with email delivery. The foundation for the full alert engine shipped in v1.1.
REST API. A versioned REST API (v1) provides programmatic access to metrics, logs, and container metadata. API keys are generated per-account and scoped to read-only or read-write permissions.
KubeWatch Agent v1.0. The open-source Agent (Apache 2.0) is distributed as a Docker image and a Kubernetes Helm chart. Configuration is minimal, provide your API key and the Agent auto-discovers workloads and begins streaming telemetry within seconds.
All updates are deployed automatically to hosted accounts. Self-hosted customers can pull the latest Agent and dashboard images from ghcr.io/kubewatch.