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
Feature/Aspect | GreptimeDB | Prometheus |
---|---|---|
Data Model | Time-Series Database | Time-Series Database |
Value model | Multi-Value | Single-Value |
Multi-model | Metrics, Logs & Events | Metrics |
Ingestion Protocols | SQL gRPC InfluxDB Line Protocol Prometheus Remote Storage OpenTelemetry | Pull-based Scraping Push gateway(HTTP) |
Query Languages | SQL & PromQL | PromQL |
Continuous Aggregation | Yes (in SQL) | NO |
Use cases | Monitoring, observability, IoT data analysis, real-time analytics | Monitoring, observability |
Architecture | Cloud-native and flexible architecture, scaled from Edge to Cloud. | Stores time series data in a custom, efficient, local storage format. It can be deployed as a single binary on a server or on a container platform like Kubernetes. |
Storage Format | Apache Parquet | Prometheus TSDB storage |
License | Apache 2.0 | Apache 2.0 |
Scalability | Opensource both single-node and cluster versions.By leveraging Object Storage (S3, and others), separating compute and storage will lead to scaling stateless compute nodes arbitrarily. | Scale vertically (single node with increased resources) or through federation (hierarchical setup where Prometheus servers scrape metrics from other Prometheus servers) |
Written Language | Rust | Golang |