Tencent Cloud Monitoring

Monitor Tencent Cloud resources with application context

Bring documented Tencent Cloud resource metrics, events, logs, and billing data into Guance, then correlate them with hosts, TKE, traces, and user experience. Each service still requires its documented collector, permissions, regions, and collection settings.

立即开始 预约演示

Why teams add shared observability to Tencent Cloud monitoring

01Keep resource identity visible

Organise telemetry by account, region, service, resource, environment, and owner.

02Follow impact beyond the cloud console

Continue from a Tencent Cloud resource signal into TKE, application traces, logs, and user experience.

03Use one operating vocabulary

Apply common tags and investigation steps across cloud, Kubernetes, applications, and teams.

04Review spend with operating context

Read supported billing data beside resource utilisation and service demand before changing capacity.

05Make collection boundaries explicit

Record the collector, permission scope, region, interval, latency, and cost for every enabled integration.

Tencent Cloud investigation workflow

Move from a cloud symptom to a tested explanation

Start with the affected service, narrow the resource scope, correlate application evidence, and verify recovery with the same filters.

  1. Confirm impact

    Identify the affected account, region, service, users, and time window.

  2. Narrow resources

    Filter resource metrics, events, and alerts by service, identifier, tags, and owner.

  3. Correlate telemetry

    Compare TKE, host, trace, log, release, and user signals where those data paths are configured.

  4. Verify recovery

    Recheck resource health, service latency, errors, alerts, and user impact after the change.

Connect the documented Tencent Cloud services you actually run

Use the Guance integration catalogue to confirm collection support for CVM, TKE, CDB, CLB, COS, and Redis. Enable only the required services, then document credentials, permissions, regions, namespaces, collection intervals, and known delays for each path.
预约演示
Connect the documented Tencent Cloud services you actually run
Treat TKE and workload telemetry as a separate data path

Treat TKE and workload telemetry as a separate data path

A cloud-account integration does not automatically instrument Kubernetes workloads or application code. Configure the documented cluster, DataKit, SDK, or OpenTelemetry path needed for pod, log, trace, and runtime evidence.
预约演示

Trace a resource symptom into application behaviour

Compare resource pressure and provider events with service latency, errors, dependencies, logs, releases, and real-user signals. Shared service and environment tags keep the investigation connected.
预约演示
Trace a resource symptom into application behaviour
Operate multiple accounts and regions with consistent context

Operate multiple accounts and regions with consistent context

Normalise provider, account, region, environment, team, and service tags so dashboards, monitors, and incident workflows can be reused without erasing ownership boundaries.
预约演示

Evaluate cost and capacity with the limits in view

Combine supported billing data with utilisation and service demand, while accounting for provider-side API charges, collection latency, retention, currency, and the permissions needed to retrieve cost data.
预约演示
Evaluate cost and capacity with the limits in view

Connected Observability

把 Kubernetes 现场接回完整运行上下文

按当前问题继续进入对应能力，不必从产品目录重新寻找入口。

Cloud monitoringExplore cloud resources, objects, metrics, events, and common tags. Kubernetes monitoringInspect TKE clusters, workloads, pods, containers, and Kubernetes events. Application Performance MonitoringTrace slow and failed requests through services and dependencies. Log monitoring and analyticsSearch cloud, platform, and application logs with shared context.

Compare cloud monitoring paths

AWS monitoring

AWS monitoring

 Alibaba Cloud monitoring

Alibaba Cloud monitoring

 Huawei Cloud monitoring

Huawei Cloud monitoring

 Azure monitoring

Azure monitoring

 Kubernetes monitoring

Kubernetes monitoring

常见问题

Which Tencent Cloud services can Guance monitor?

Coverage is service-specific and changes as integrations evolve. Use the current Guance integration catalogue and each service page as the source of truth for supported metrics, objects, logs, setup, permissions, and limitations.

Does Guance replace Tencent Cloud's native monitoring tools?

No blanket replacement is implied. Native services remain the source for provider-specific telemetry and controls. Guance adds a shared investigation layer across configured cloud resources, Kubernetes, applications, logs, user experience, and other environments.

Does connecting a cloud account automatically collect traces and application logs?

No. Account integrations, TKE monitoring, host collection, application tracing, log collection, and RUM use distinct setup paths. Configure and validate each signal you need.

Can the same workspace monitor several cloud providers?

Yes, for providers and services with documented integrations. Define common provider, account, region, environment, service, and owner tags, then validate collection scope and permissions for every provider separately.

Map your Tencent Cloud services, collection paths, and failure scenarios before rollout

预约演示

你或许想

立即开始 > 查看文档 > 查看价格 >