Guance Container Monitoring

Overview

Guance Container Monitoring is an observability tool for containerized infrastructure, with Kubernetes views that follow workloads down to individual containers. It is best suited to teams that need to connect workload changes with metrics, logs, traces, and network signals; its main trade-off is the Free Plan’s small host cap and inability to move its data into a Commercial Plan workspace.

Rather than treating containers as static inventory, the product detects their creation, termination, restarts, and other workload changes as they occur. That makes it a practical fit for investigating short-lived workloads, where health signals alone may not explain what changed.

Key features

Kubernetes drill-down and change context

Users can investigate from cluster and node through namespace, workload, pod, and container. Resource signals include CPU, memory, network and disk activity, restart count, exit state, resource requests and limits, replica health, and node pressure. Guance also places changes to Deployments, DaemonSets, Services, CronJobs, StatefulSets, and other workload objects beside health and performance signals. That combination is useful when a team needs to distinguish a rollout or configuration change from a resource problem.

Correlated telemetry and alerting

Container metrics, logs, traces, and network data share context, and monitors can cover node, pod, container, workload, and service conditions. Alerts can link to related telemetry and events, reducing the gap between notification and investigation. The breadth is valuable for teams using several signal types, though it is less compelling if the need is limited to a single metric feed.

Collection, integrations, and safeguards

Guance documents AWS Fargate collection for container metrics, logs, and traces, with coverage dependent on the environment and collector configuration. Its integrations include Kubernetes, AWS, Tencent Cloud, Huawei Cloud, Alibaba Cloud, Azure Monitor, and OpenTelemetry. It states that data is encrypted in transit and at rest and is not accessed without authorization; its trust page lists Level 3 information security protection and ISO 9001, ISO 27001, and ISO 20000 certifications. Documentation, release notes, a status page, phone support, and sales email contact are also listed.

Pricing

Guance uses a freemium model and offers a free trial. The Free Plan costs free and allows up to 10 hosts, 10,000 metric series per day, 10 million log records per day, and seven-day rolling retention. It supports host, container, and Kubernetes collection, making it a reasonable starting point for a small environment or evaluation. The host ceiling and short retention limit its usefulness for larger estates or investigations that depend on older data. More importantly, Free Plan data cannot be migrated to a Commercial Plan workspace, so starting free creates a data-separation cost if the team later upgrades.

The Commercial Plan has custom pricing and 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. That structure can suit teams whose consumption varies, but budgeting depends on usage across several product areas. It is the option to discuss with sales when an enterprise arrangement is needed, rather than a plan with a clear published allowance to compare against the free tier.

Platforms

Supported platforms include Linux, Windows, macOS, Docker, and Kubernetes. The broader platform list also includes Android, iOS, API, web, and self-hosted. Guance describes a hybrid deployment model. Container log collection, container metrics, resource alerts, image monitoring, and runtime events are supported.

Who it's for

This is a strong fit for platform and operations teams managing Kubernetes or mixed container environments that need workload-level context, change evidence, and multiple telemetry types in one investigation path. Fargate users may also find it relevant, provided their environment and collector configuration match the documented scenarios. The Free Plan is best for a small pilot that can tolerate its 10-host ceiling, daily quotas, seven-day retention, and separate workspace data. Teams needing long retention or a clean upgrade path should assess a paid plan before putting important history into the free workspace.

Pros and cons

• Pros: Kubernetes drill-down reaches from cluster to container, while workload changes sit beside resource and health signals; this gives teams useful operational context for transient workloads.
• Pros: Metrics, logs, traces, and network data are correlated, with alerting across nodes, pods, containers, workloads, and services.
• Pros: The Free Plan has no charge and includes container and Kubernetes collection, but remains capped at 10 hosts and seven-day rolling retention.
• Cons: Free Plan data cannot be migrated to a Commercial Plan workspace, which complicates a later move from evaluation to paid operation.

Alternatives

For database-specific needs, MySQL is a freemium option with a free plan and trial, while DBmarlin is another database-monitoring choice with a free plan but no free trial. Percona Monitoring and Management is worth considering when free, open-source database monitoring and management is the priority, though installation infrastructure may have separate costs. For broader application observability, Grafana Cloud Application Observability has an always-free tier with 2,232 host hours and a Pro plan priced at $0.03 a month with a $19 monthly platform fee and pay-as-you-go usage above its allowance. Teams focused on Kubernetes and wanting a stated annual commitment can compare New Relic Kubernetes Monitoring, whose Pro plan is $349 a year and includes unlimited full platform users and 100 GB of free data ingest, with additional ingest at $0.40/GB. For other monitoring categories, browse Database Monitoring, Container Monitoring, Mobile App Monitoring, and Continuous Profiling Tools.

Verdict

Choose Guance Container Monitoring if your team needs to trace changing container workloads through Kubernetes hierarchy and correlate their health with logs, traces, and network data. Its strongest case is the combination of workload-change context and cross-signal investigation. Look elsewhere if a free deployment must scale beyond 10 hosts, retain data longer than seven days, or transition its history into a paid workspace; for those needs, the plan boundary is a material drawback.