[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5628":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":25,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":46,"readmeContent":47,"aiSummary":48,"trendingCount":16,"starSnapshotCount":16,"syncStatus":49,"lastSyncTime":50,"discoverSource":51},5628,"greptimedb","GreptimeTeam\u002Fgreptimedb","GreptimeTeam","The open-source Observability 2.0 database. One engine for metrics, logs, and traces — replacing Prometheus, Loki & ES.","https:\u002F\u002Fgreptime.com\u002F",null,"Rust",6346,495,54,168,0,1,22,98,10,39.09,"Apache License 2.0",false,"main",true,[27,28,29,30,31,5,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"ai-observability","analytics","cloud-native","database","distributed","llm-monitoring","logs","metrics","monitoring","object-storage","observability","observability-database","observability-datalake","opentelemetry","prometheus","promql","rust","sql","traces","2026-06-12 02:01:13","\u003Cp align=\"center\">\n  \u003Cpicture>\n    \u003Csource media=\"(prefers-color-scheme: light)\" srcset=\"https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FGreptimeTeam\u002Fgreptimedb@main\u002Fdocs\u002Flogo-text-padding.png\">\n    \u003Csource media=\"(prefers-color-scheme: dark)\" srcset=\"https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FGreptimeTeam\u002Fgreptimedb@main\u002Fdocs\u002Flogo-text-padding-dark.png\">\n    \u003Cimg alt=\"GreptimeDB Logo\" src=\"https:\u002F\u002Fcdn.jsdelivr.net\u002Fgh\u002FGreptimeTeam\u002Fgreptimedb@main\u002Fdocs\u002Flogo-text-padding.png\" width=\"400px\">\n  \u003C\u002Fpicture>\n\u003C\u002Fp>\n\n\u003Ch2 align=\"center\">One database for metrics, logs, and traces\u003Cbr\u002F>\nreplacing Prometheus, Loki, and Elasticsearch\u003C\u002Fh2>\n\n>  The unified OpenTelemetry backend — with SQL + PromQL on object storage.\n\n\u003Cdiv align=\"center\">\n\u003Ch3 align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Foverview\u002F\">User Guide\u003C\u002Fa> |\n  \u003Ca href=\"https:\u002F\u002Fgreptimedb.rs\u002F\">API Docs\u003C\u002Fa> |\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Fissues\u002F7685\">Roadmap 2026\u003C\u002Fa>\n\u003C\u002Fh3>\n\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Freleases\u002Flatest\">\n\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fv\u002Frelease\u002FGreptimeTeam\u002Fgreptimedb.svg\" alt=\"Version\"\u002F>\n\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Freleases\u002Flatest\">\n\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Frelease-date\u002FGreptimeTeam\u002Fgreptimedb.svg\" alt=\"Releases\"\u002F>\n\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fhub.docker.com\u002Fr\u002Fgreptime\u002Fgreptimedb\u002F\">\n\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fdocker\u002Fpulls\u002Fgreptime\u002Fgreptimedb.svg\" alt=\"Docker Pulls\"\u002F>\n\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Factions\u002Fworkflows\u002Fdevelop.yml\">\n\u003Cimg src=\"https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Factions\u002Fworkflows\u002Fdevelop.yml\u002Fbadge.svg\" alt=\"GitHub Actions\"\u002F>\n\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fcodecov.io\u002Fgh\u002FGrepTimeTeam\u002Fgreptimedb\">\n\u003Cimg src=\"https:\u002F\u002Fcodecov.io\u002Fgh\u002FGrepTimeTeam\u002Fgreptimedb\u002Fbranch\u002Fmain\u002Fgraph\u002Fbadge.svg?token=FITFDI3J3C\" alt=\"Codecov\"\u002F>\n\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FgreptimeTeam\u002Fgreptimedb\u002Fblob\u002Fmain\u002FLICENSE\">\n\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Flicense\u002FgreptimeTeam\u002Fgreptimedb\" alt=\"License\"\u002F>\n\u003C\u002Fa>\n\n\u003Cbr\u002F>\n\n\u003Ca href=\"https:\u002F\u002Fgreptime.com\u002Fslack\">\n\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fslack-GreptimeDB-0abd59?logo=slack&style=for-the-badge\" alt=\"Slack\"\u002F>\n\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fgreptime\">\n\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Ftwitter-follow_us-1d9bf0.svg?style=for-the-badge\" alt=\"Twitter\"\u002F>\n\u003C\u002Fa>\n\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fgreptime\u002F\">\n\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flinkedin-connect_with_us-0a66c2.svg?style=for-the-badge\" alt=\"LinkedIn\"\u002F>\n\u003C\u002Fa>\n\u003C\u002Fdiv>\n\n- [Introduction](#introduction)\n- [⭐ Key Features](#features)\n- [How GreptimeDB Compares](#how-greptimedb-compares)\n- [Architecture](#architecture)\n- [Try GreptimeDB](#try-greptimedb)\n- [Getting Started](#getting-started)\n- [Build From Source](#build-from-source)\n- [Tools & Extensions](#tools--extensions)\n- [Project Status](#project-status)\n- [Community](#community)\n- [License](#license)\n- [Commercial Support](#commercial-support)\n- [Contributing](#contributing)\n- [Acknowledgement](#acknowledgement)\n\n## Introduction\n\n**GreptimeDB** is an open-source observability database built for [Observability 2.0](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fconcepts\u002Fobservability-2\u002F) — treating metrics, logs, and traces as one unified data model (wide events) instead of three separate pillars.\n\nUse it as the single OpenTelemetry backend — replacing Prometheus, Loki, and Elasticsearch with one database built on object storage. Query with SQL and PromQL, scale without pain, cut costs up to 50x.\n\n## Features\n\n|   Feature  | Description |\n| --------- | ----------- |\n| Drop-in replacement | [PromQL](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fquery-data\u002Fpromql\u002F), [Prometheus remote write](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fingest-data\u002Ffor-observability\u002Fprometheus\u002F), [Jaeger](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fquery-data\u002Fjaeger\u002F), and [OpenTelemetry](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fingest-data\u002Ffor-observability\u002Fopentelemetry\u002F) native. Use as your single backend for all three signals, or migrate one at a time.|\n| 50x lower cost | Object storage (S3, GCS, Azure Blob etc.) as [primary storage](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fdeployments-administration\u002Fconfiguration\u002F#storage-options). Compute-storage separation scales without pain.|\n| SQL + PromQL | Monitor with [PromQL](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fquery-data\u002Fpromql), analyze with [SQL](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fquery-data\u002Fsql). One database replaces Prometheus + your data warehouse.|\n| Sub-second at PB-EB scale | Columnar engine with [fulltext, inverted, and skipping indexes](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fmanage-data\u002Fdata-index). Written in Rust.|\n\n  ✅ **Perfect for:**\n  * Replacing Prometheus + Loki + Elasticsearch with one database\n  * Scaling past Prometheus — high cardinality, long-term storage, no Thanos\u002FMimir overhead\n  * Cutting observability costs with object storage (up to 50x savings on traces, 30% on logs)\n  * AI\u002FLLM observability — store and analyze high-volume conversation data, agent traces, and token metrics via [OpenTelemetry GenAI conventions](https:\u002F\u002Fopentelemetry.io\u002Fdocs\u002Fspecs\u002Fsemconv\u002Fgen-ai\u002F)\n  * Edge-to-cloud observability with unified APIs on resource-constrained devices\n\n> **Why Observability 2.0?** The three-pillar model (separate databases for metrics, logs, traces) creates data silos and operational complexity. GreptimeDB treats all observability data as timestamped wide events in a single columnar engine — enabling cross-signal SQL JOINs, eliminating redundant infrastructure, and naturally supporting emerging workloads like AI agent observability. Read more: [Observability 2.0 and the Database for It](https:\u002F\u002Fgreptime.com\u002Fblogs\u002F2025-04-25-greptimedb-observability2-new-database).\n\nLearn more in [Why GreptimeDB](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fconcepts\u002Fwhy-greptimedb).\n\n## How GreptimeDB Compares\n\n| Feature | GreptimeDB | Prometheus \u002F Thanos \u002F Mimir | Grafana Loki | Elasticsearch |\n|---|---|---|---|---|\n| Data types | Metrics, logs, traces | Metrics only | Logs only | Logs, traces |\n| Query language | SQL + PromQL | PromQL | LogQL | Query DSL |\n| Storage | Native object storage (S3, etc.) | Local disk + object storage (Thanos\u002FMimir) | Object storage (chunks) | Local disk |\n| Scaling | Compute-storage separation, stateless nodes | Federation \u002F Thanos \u002F Mimir — multi-component, ops heavy | Stateless + object storage | Shard-based, ops heavy |\n| Cost efficiency | Up to 50x lower storage | High at scale | Moderate | High (inverted index overhead) |\n| OpenTelemetry | Native (metrics + logs + traces) | Partial (metrics only) | Partial (logs only) | Via instrumentation |\n\n**Benchmarks:**\n* [GreptimeDB tops JSONBench's billion-record cold run test](https:\u002F\u002Fgreptime.com\u002Fblogs\u002F2025-03-18-jsonbench-greptimedb-performance)\n* [TSBS Benchmark](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Ftree\u002Fmain\u002Fdocs\u002Fbenchmarks\u002Ftsbs)\n* [More benchmark reports](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Fconcepts\u002Ffeatures-that-you-concern#how-is-greptimedbs-performance-compared-to-other-solutions)\n\n## Architecture\n\nGreptimeDB can run in two modes:\n* **Standalone Mode** - Single binary for development and small deployments\n* **Distributed Mode** - Separate components for production scale:\n  - Frontend: Query processing and protocol handling\n  - Datanode: Data storage and retrieval\n  - Metasrv: Metadata management and coordination\n  \nRead the [architecture](https:\u002F\u002Fdocs.greptime.com\u002Fcontributor-guide\u002Foverview\u002F#architecture) document. [DeepWiki](https:\u002F\u002Fdeepwiki.com\u002FGreptimeTeam\u002Fgreptimedb\u002F1-overview) provides an in-depth look at GreptimeDB:\n  \u003Cimg alt=\"GreptimeDB System Overview\" src=\"docs\u002Farchitecture.png\">\n\n## Try GreptimeDB\n\n```shell\ndocker pull greptime\u002Fgreptimedb\n```\n\n```shell\ndocker run -p 127.0.0.1:4000-4003:4000-4003 \\\n  -v \"$(pwd)\u002Fgreptimedb_data:\u002Fgreptimedb_data\" \\\n  --name greptime --rm \\\n  greptime\u002Fgreptimedb:latest standalone start \\\n  --http-addr 0.0.0.0:4000 \\\n  --grpc-bind-addr 0.0.0.0:4001 \\\n  --mysql-addr 0.0.0.0:4002 \\\n  --postgres-addr 0.0.0.0:4003\n```\nDashboard: [http:\u002F\u002Flocalhost:4000\u002Fdashboard](http:\u002F\u002Flocalhost:4000\u002Fdashboard)\n\nRead more in the [full Install Guide](https:\u002F\u002Fdocs.greptime.com\u002Fgetting-started\u002Finstallation\u002Foverview).\n\n**Troubleshooting:**\n* Cannot connect to the database? Ensure that ports `4000`, `4001`, `4002`, and `4003` are not blocked by a firewall or used by other services.\n* Failed to start? Check the container logs with `docker logs greptime` for further details.\n\n## Getting Started\n\n- [Quickstart](https:\u002F\u002Fdocs.greptime.com\u002Fgetting-started\u002Fquick-start)\n- [User Guide](https:\u002F\u002Fdocs.greptime.com\u002Fuser-guide\u002Foverview)\n- [Demo Scenes](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fdemo-scene)\n- [FAQ](https:\u002F\u002Fdocs.greptime.com\u002Ffaq-and-others\u002Ffaq)\n\n## Build From Source\n\n**Prerequisites:**\n* [Rust toolchain](https:\u002F\u002Fwww.rust-lang.org\u002Ftools\u002Finstall) (nightly)\n* [Protobuf compiler](https:\u002F\u002Fgrpc.io\u002Fdocs\u002Fprotoc-installation\u002F) (>= 3.15)\n* C\u002FC++ building essentials, including `gcc`\u002F`g++`\u002F`autoconf` and glibc library (eg. `libc6-dev` on Ubuntu and `glibc-devel` on Fedora)\n* Python toolchain (optional): Required only if using some test scripts.\n\n**Build and Run:**\n```bash\nmake\ncargo run -- standalone start\n```\n\n## Tools & Extensions\n\n- **Kubernetes**: [GreptimeDB Operator](https:\u002F\u002Fgithub.com\u002FGrepTimeTeam\u002Fgreptimedb-operator)\n- **Helm Charts**: [Greptime Helm Charts](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fhelm-charts)\n- **Dashboard**: [Web UI](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fdashboard)\n- **gRPC Ingester**: [Go](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb-ingester-go), [Java](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb-ingester-java), [C++](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb-ingester-cpp), [Erlang](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb-ingester-erl), [Rust](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb-ingester-rust), [.NET](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb-ingester-dotnet)\n- **Grafana Data Source**: [GreptimeDB Grafana data source plugin](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb-grafana-datasource)\n- **Grafana Dashboard**: [Official Dashboard for monitoring](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Fblob\u002Fmain\u002Fgrafana\u002FREADME.md)\n\n## Project Status\n\n> **Status:** [v1.0 GA](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Freleases\u002Ftag\u002Fv1.0.0) — generally available and production-ready! 🎉\n\n- Deployed in production handling billions of data points daily\n- Stable APIs, actively maintained, with regular releases ([version info](https:\u002F\u002Fdocs.greptime.com\u002Fnightly\u002Freference\u002Fabout-greptimedb-version))\n\nGreptimeDB v1.0 marks a major milestone — stable APIs, production readiness, and proven performance at scale.\n\n**Learn more:** [v1.0 highlights](https:\u002F\u002Fgreptime.com\u002Fblogs\u002F2025-11-05-greptimedb-v1-highlights) and [2026 roadmap](https:\u002F\u002Fgreptime.com\u002Fblogs\u002F2026-02-11-greptimedb-roadmap-2026).\n\nFor production use, we recommend v1.0 or later.\n\nIf you find this project useful, a ⭐ would mean a lot to us!\n\n[![Star History Chart](https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=GreptimeTeam\u002FGreptimeDB&type=Date)](https:\u002F\u002Fwww.star-history.com\u002F#GreptimeTeam\u002FGreptimeDB&Date)\n\n\u003Cimg alt=\"Known Users\" src=\"https:\u002F\u002Fgreptime.com\u002Flogo\u002Fimg\u002Fusers.png\"\u002F>\n\n## Community\n\nWe invite you to engage and contribute!\n\n- [Slack](https:\u002F\u002Fgreptime.com\u002Fslack)\n- [Discussions](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Fdiscussions)\n- [Official Website](https:\u002F\u002Fgreptime.com\u002F)\n- [Blog](https:\u002F\u002Fgreptime.com\u002Fblogs\u002F)\n- [LinkedIn](https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fgreptime\u002F)\n- [X (Twitter)](https:\u002F\u002FX.com\u002Fgreptime)\n- [YouTube](https:\u002F\u002Fwww.youtube.com\u002F@greptime)\n\n## License\n\nGreptimeDB is licensed under the [Apache License 2.0](https:\u002F\u002Fapache.org\u002Flicenses\u002FLICENSE-2.0.txt).\n\n## Commercial Support\n\nRunning GreptimeDB in your organization?\nWe offer enterprise add-ons, services, training, and consulting.\n[Contact us](https:\u002F\u002Fgreptime.com\u002Fcontactus) for details.\n\n## Contributing\n\n- Read our [Contribution Guidelines](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Fblob\u002Fmain\u002FCONTRIBUTING.md).\n- Explore [Internal Concepts](https:\u002F\u002Fdocs.greptime.com\u002Fcontributor-guide\u002Foverview.html) and [DeepWiki](https:\u002F\u002Fdeepwiki.com\u002FGreptimeTeam\u002Fgreptimedb).\n- Pick up a [good first issue](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Fissues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) and join the #contributors [Slack](https:\u002F\u002Fgreptime.com\u002Fslack) channel.\n\n## Acknowledgement\n\nSpecial thanks to all contributors! See [AUTHORS.md](https:\u002F\u002Fgithub.com\u002FGreptimeTeam\u002Fgreptimedb\u002Fblob\u002Fmain\u002FAUTHOR.md).\n\n- Uses [Apache Arrow™](https:\u002F\u002Farrow.apache.org\u002F) (memory model)\n- [Apache Parquet™](https:\u002F\u002Fparquet.apache.org\u002F) (file storage)\n- [Apache DataFusion™](https:\u002F\u002Farrow.apache.org\u002Fdatafusion\u002F) (query engine)\n- [Apache OpenDAL™](https:\u002F\u002Fopendal.apache.org\u002F) (data access abstraction)\n","GreptimeDB 是一个开源的可观测性2.0数据库，集成了指标、日志和追踪数据的处理能力，旨在替代Prometheus、Loki及Elasticsearch。它使用Rust语言编写，支持SQL与PromQL查询，并能够利用对象存储来实现高效的数据管理。该项目具有云原生特性，支持分布式部署，适用于需要统一监控和分析解决方案的场景，比如微服务架构下的应用性能管理和故障排查。此外，GreptimeDB还兼容OpenTelemetry标准，方便集成到现有的可观测性生态系统中。",2,"2026-06-11 03:04:24","top_language"]