# Monitoring

> Overview of monitoring methods for GreptimeDB, including exporting metrics and tracing.

# Monitoring

Effective database administration relies heavily on monitoring. 
You can monitor GreptimeDB using the following methods:

- [Check GreptimeDB Status](check-db-status.md) — Check GreptimeDB health status, deployment status, and runtime metrics through HTTP endpoints.
- [Key Logs](key-logs.md) — Understand GreptimeDB's operational status and troubleshoot errors through key logs.
- [Prometheus-Monitoring GreptimeDB Cluster](monitor-cluster-with-prometheus.md) — Learn how to monitor a GreptimeDB cluster using an existing Prometheus instance in Kubernetes, including configuration steps and Grafana dashboard setup.
- [Runtime Information](runtime-info.md) — Provides access to system metadata through the INFORMATION_SCHEMA database, including cluster topology and table regions distribution. Examples of SQL queries to retrieve region IDs and distribution are included.
- [Self-Monitoring GreptimeDB Clusters](cluster-monitoring-deployment.md) — Complete guide to deploying self-monitoring for GreptimeDB clusters on Kubernetes, including Grafana dashboard setup and configuration options
- [Slow Query (Experimental)](slow-query.md) — Guide on configuring and using slow query logging in GreptimeDB for monitoring.
- [Standalone Monitoring](standalone-monitoring.md) — Guide to monitor GreptimeDB standalone instance using Prometheus metrics and Grafana.
- [Tracing](tracing.md) — Guide on using distributed tracing in GreptimeDB with Jaeger. Includes steps for deploying Jaeger, configuring GreptimeDB for tracing, obtaining trace information, and configuring tracing sampling rates.