✕

Join us for a virtual meetup on Zoom at 8 PM, July 31 (PDT) about using One Time Series Database for Both Metrics and Logs 👉🏻 Register Now

✕
Skip to content
About Prometheus
Prometheus is a popular open-source monitoring and alerting toolkit designed for collecting and querying metrics, primarily in cloud-native environments. Developed as part of the CNCF ecosystem, Prometheus uses a pull-based model to scrape metrics from targets and stores them in its local time-series database. It's widely adopted for monitoring applications and infrastructure in DevOps settings, featuring a powerful query language (PromQL) and strong integration with Grafana for visualization.
GreptimeDB vs. Prometheus
Feature/AspectGreptimeDBPrometheus
Data ModelUnified Observability DatabaseTime-Series Database
Value ModelMulti-Value (supports complex data structures)Single-Value (metrics only)
Multi-model SupportMetrics, Logs & Traces in one databaseMetrics only (requires separate systems for logs/traces)
Ingestion ProtocolsSQL
gRPC
InfluxDB Line Protocol
Prometheus Remote Storage
OpenTelemetry
HTTP API
Pull-based Scraping
Push Gateway (HTTP)
Remote Write API
Query LanguagesSQL & PromQL (dual interface)PromQL only
Data RetentionFlexible TTL policies with tiered storageConfiguration-based retention (15 days default)
Continuous AggregationBuilt-in SQL aggregation, Pipeline ETL engine & Flow streaming computationRecording rules (limited aggregation)
Use CasesUnified observability, real-time analytics, IoT monitoring, edge computingApplication monitoring, infrastructure monitoring, alerting
ArchitectureCloud-native distributed architecture with compute-storage separationSingle-node with optional federation for scaling
Storage FormatApache Parquet (columnar, highly compressed)Custom TSDB format (optimized for time-series)
Storage ScalabilityObject storage integration (S3, GCS, etc.) with unlimited capacityLocal disk storage with limited retention
High AvailabilityNative clustering with automatic failoverRequires manual federation setup
LicenseApache 2.0Apache 2.0
Deployment OptionsSingle-node, cluster, Kubernetes-native, edge-to-cloud with unified APISingle binary, container, Kubernetes operator
Operational ComplexitySingle unified system with simplified Kubernetes operationsRequires additional components for full observability
Written LanguageRust (memory safety, performance)Go (simplicity, fast development)

Join our community

Get the latest updates and discuss with other users.