Guance Container Monitoring

Overview

Guance Container Monitoring is an observability product for container and Kubernetes workloads, best suited to teams that need to investigate changing workloads alongside their telemetry. Its strongest case is the link between lifecycle changes and health signals; the Free Plan’s 10-host ceiling and non-migratable data make a low-risk start less straightforward.

Key features

Workload changes and health

Guance detects container creation, termination, restarts, and workload changes as they happen. Kubernetes views run from cluster and node through namespace, workload, pod, and container, while resource signals cover CPU, memory, network and disk, restart count, exit state, resource requests and limits, replica health, and node pressure. Changes to Deployments, DaemonSets, Services, CronJobs, StatefulSets, and other workload objects sit alongside health and performance signals. This is useful when teams need to tell whether a change coincided with a workload problem, rather than inspect those clues separately.

Correlated telemetry and alerts

Container metrics, logs, traces, and network data share context. Monitors can cover node, pod, container, workload, and service conditions, with alerts routed alongside links to related telemetry and events. That breadth supports investigation across several layers, though it does not remove the need to configure the relevant monitors and collection.

Collection and adjacent capabilities

Guance documents AWS Fargate collection for container metrics, logs, and traces, with coverage depending on environment and collector configuration. Listed integrations include Kubernetes, AWS, Tencent Cloud, Huawei Cloud, Alibaba Cloud, Azure Monitor, and OpenTelemetry. Container metrics, resource alerts, image monitoring, runtime events, and container log collection are supported. The broader platform also names Java, Python, Go, and C/C++ support; CPU, memory, I/O, locks, allocations, queries, and function-call profiling; query profiling, wait and lock analysis, and execution plans; and application and mobile monitoring capabilities. These make the product relevant beyond container health alone, but teams choosing solely for container monitoring should weigh only the collection and investigation features they need.

Pricing

The Free Plan costs nothing and supports up to 10 hosts, 10,000 metric series per day, 10 million log records per day, and seven-day rolling retention. It is a useful fit for a small environment or initial evaluation, but the host and daily-volume ceilings constrain larger deployments. Data collected in the Free Plan cannot be migrated to a Commercial Plan workspace, an important restriction for teams expecting to grow in place.

The Commercial Plan is pay-as-you-go, with charges based on actual usage across infrastructure metrics, logs, data forwarding, Triggers, RUM page views, APM traces, synthetic tests, and notifications. It suits teams that want usage-based billing across those services, but should be budgeted against actual collection and product use. Teams needing an enterprise arrangement should contact sales rather than assume the Free Plan’s limits carry over.

Platforms

The container offering supports Linux, Windows, macOS, Docker, and Kubernetes, and the deployment model is hybrid. The wider platform lists Android, iOS, API, Linux, macOS, self-hosted, web, and Windows. Security commitments include encryption in transit and at rest, and Guance says it does not access customer data without authorization. Its trust page lists Level 3 information security protection and ISO 9001, ISO 27001, and ISO 20000 certifications. Support channels include documentation, release notes, a status page, phone support, and sales email.

Who it's for

Guance is a strong candidate for teams running Kubernetes or other container workloads that need lifecycle events, resource signals, and related telemetry in one investigation path. Its documented Fargate scenarios may also suit teams collecting container signals in AWS, provided their environment and collector configuration support the desired coverage. It is less compelling for a growing deployment that needs a seamless path from free evaluation to paid use, because Free Plan data cannot move into a Commercial workspace.

Pros and cons

Pro: Lifecycle changes appear beside health and performance signals, helping teams investigate transient workloads in context.

Pro: The Kubernetes drill-down and shared context across metrics, logs, traces, and network data span both infrastructure and telemetry.

Pro: The Free Plan includes container and Kubernetes collection with stated daily quotas, making its scope easier to assess for a small deployment.

Con: Free use stops at 10 hosts and seven-day rolling retention, which can be restrictive for larger fleets or longer investigations.

Con: Free Plan data cannot be migrated to a Commercial Plan workspace, so teams should account for a separate paid-workspace transition.

Con: Enterprise pricing and limits are custom, while Commercial charges vary with usage across multiple services; cost planning requires care.

Alternatives

Consider Coroot if a self-hosted community edition under Apache 2.0 or per-monitored-CPU pricing better suits your deployment and billing preferences. Metoro Kubernetes Profiling is a more focused alternative when Kubernetes profiling is the priority; its Hobby plan states one cluster, one user, two nodes, and 28-day retention. For a broader free usage allowance, Middleware offers a Free Forever plan with up to 100GB of data, 1,000 RUM sessions, and 20,000 synthetic checks, among other limits.

Elastic Observability is a paid alternative with a free plan and usage-based serverless pricing. Grafana Cloud Application Observability offers a free tier and a Pro plan. Sentry Continuous Profiling has a free plan. FusionReactor and Dynatrace Continuous CPU Profiling are paid alternatives with free trials. For browsing by category, see Container Monitoring, Continuous Profiling Tools, Database Monitoring, and Mobile App Monitoring.

Verdict

Choose Guance Container Monitoring if your team needs to connect container lifecycle changes with Kubernetes health signals and correlated telemetry. Its breadth and defined free quotas make it worth considering for small deployments, but the 10-host cap and non-migratable Free Plan data are serious reasons to look elsewhere if you expect to scale an evaluation into a Commercial workspace.