[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-94602":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":9,"totalLinesOfCode":9,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":9,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":16,"stars30d":17,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":18,"rankGlobal":9,"rankLanguage":9,"license":9,"archived":19,"fork":19,"defaultBranch":20,"hasWiki":19,"hasPages":19,"topics":9,"createdAt":9,"pushedAt":9,"updatedAt":21,"readmeContent":22,"aiSummary":23,"trendingCount":16,"starSnapshotCount":16,"syncStatus":24,"lastSyncTime":25,"discoverSource":26},94602,"tempo","grafana\u002Ftempo","grafana","Grafana Tempo is a high volume, minimal dependency distributed tracing backend.",null,"https:\u002F\u002Fgithub.com\u002Fgrafana\u002Ftempo","Go",5430,742,172,91,0,1,61.71,false,"main","2026-08-24 04:01:22","\u003Cp align=\"center\">\u003Cimg src=\"docs\u002Fsources\u002Ftempo\u002Flogo_and_name.png\" alt=\"Tempo Logo\">\u003C\u002Fp>\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fgrafana\u002Ftempo\u002Freleases\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fv\u002Frelease\u002Fgrafana\u002Ftempo?display_name=tag&sort=semver\" alt=\"Latest Release\"\u002F>\u003C\u002Fa>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Flicense\u002Fgrafana\u002Ftempo\" alt=\"License\" \u002F>\n  \u003Ca href=\"https:\u002F\u002Fhub.docker.com\u002Fr\u002Fgrafana\u002Ftempo\u002Ftags\">\u003Cimage src=\"https:\u002F\u002Fimg.shields.io\u002Fdocker\u002Fpulls\u002Fgrafana\u002Ftempo\" alt=\"Docker Pulls\"\u002F>\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fgrafana.slack.com\u002Farchives\u002FC01D981PEE5\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fjoin%20slack-%23tempo-brightgreen.svg\" alt=\"Slack\" \u002F>\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fcommunity.grafana.com\u002Fc\u002Fgrafana-tempo\u002F40\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fdiscuss-tempo%20forum-orange.svg\" alt=\"Community Forum\" \u002F>\u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fgoreportcard.com\u002Freport\u002Fgithub.com\u002Fgrafana\u002Ftempo\">\u003Cimg src=\"https:\u002F\u002Fgoreportcard.com\u002Fbadge\u002Fgithub.com\u002Fgrafana\u002Ftempo\" alt=\"Go Report Card\" \u002F>\u003C\u002Fa>\n\u003C\u002Fp>\n\nGrafana Tempo is an open source, easy-to-use, and high-scale distributed tracing backend. Tempo is cost-efficient, requiring only object storage to operate, and is deeply integrated with Grafana, Prometheus, and Loki.\n\n\n## Business value of distributed tracing\n\nDistributed tracing helps teams quickly pinpoint performance issues and understand the flow of requests across services. The Traces Drilldown UI simplifies this process by offering a user-friendly interface to view and analyze trace data, making it easier to identify and resolve issues without needing to write complex queries.\n\nRefer to [Use traces to find solutions](https:\u002F\u002Fgrafana.com\u002Fdocs\u002Ftempo\u002Flatest\u002Fintroduction\u002Fsolutions-with-traces\u002F) to learn more about how you can use distributed tracing to investigate and solve issues.\n\n## Traces Drilldown UI: A better way to get value from your tracing data\nWe are excited to introduce the [Traces Drilldown](https:\u002F\u002Fgithub.com\u002Fgrafana\u002Ftraces-drilldown) (formerly Explore Traces) app as part of the Grafana Explore suite. This app provides a queryless and intuitive experience for analyzing tracing data, allowing teams to quickly identify performance issues, latency bottlenecks, and errors without needing to write complex queries or use TraceQL.\n\nKey Features:\n- **Intuitive Trace Analysis**: Spot slow or error-prone traces with easy, point-and-click interactions.\n- **RED Metrics Overview**: Use Rate, Errors, and Duration metrics to highlight performance issues.\n- **Automated Comparison**: Identify problematic attributes with automatic trace comparison.\n- **Simplified Visualizations**: Access rich visual data without needing to construct TraceQL queries.\n\n![image](https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002F991205df-1b27-489f-8ef0-1a05ee158996)\n\nTo learn more see the following links:\n- [Traces Drilldown repo](https:\u002F\u002Fgithub.com\u002Fgrafana\u002Ftraces-drilldown)\n- [Traces Drilldown documentation](https:\u002F\u002Fgrafana.com\u002Fdocs\u002Fgrafana\u002Flatest\u002Fexplore\u002Fsimplified-exploration\u002Ftraces\u002F)\n- [Demo video](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=a3uB1C2oHA4)\n\n## TraceQL\n\nTempo implements [TraceQL](https:\u002F\u002Fgrafana.com\u002Fdocs\u002Ftempo\u002Flatest\u002Ftraceql\u002F), a traces-first query language inspired by LogQL and PromQL, which enables targeted queries or rich UI-driven analyses.\n\n### TraceQL metrics\n\n[TraceQL metrics](https:\u002F\u002Fgrafana.com\u002Fdocs\u002Ftempo\u002Flatest\u002Ftraceql\u002Fmetrics-queries\u002F) is an experimental feature in Grafana Tempo that creates metrics from traces. Metric queries extend trace queries by applying a function to trace query results. This powerful feature allows for ad hoc aggregation of any existing TraceQL query by any dimension available in your traces, much in the same way that LogQL metric queries create metrics from logs.\n\nTempo is Jaeger, Zipkin, Kafka and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it's robust, cheap, and easy to operate.\n\n## Getting started with Tempo\n\n- [Get started documentation](https:\u002F\u002Fgrafana.com\u002Fdocs\u002Ftempo\u002Flatest\u002Fgetting-started\u002F)\n- [Deployment Examples](.\u002Fexample)\n  - [Docker Compose](.\u002Fexample\u002Fdocker-compose)\n  - [Helm](.\u002Fexample\u002Fhelm)\n  - [Jsonnet](.\u002Fexample\u002Ftk)\n\n## Further reading\n\nTo learn more about Tempo, consult the following documents & talks:\n\n- [How to get started with Tempo with Joe Elliott (video)](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=zDrA7Ly3ovU)\n- [Grafana blog posts about Tempo](https:\u002F\u002Fgrafana.com\u002Ftags\u002Ftempo\u002F)\n- [New in Grafana Tempo 2.0: Apache Parquet as the default storage format, support for TraceQL][tempo_20_announce]\n- [Get to know TraceQL: A powerful new query language for distributed tracing][traceql-post]\n\n[tempo_20_announce]: https:\u002F\u002Fgrafana.com\u002Fblog\u002F2023\u002F02\u002F01\u002Fnew-in-grafana-tempo-2.0-apache-parquet-as-the-default-storage-format-support-for-traceql\u002F\n[traceql-post]: https:\u002F\u002Fgrafana.com\u002Fblog\u002F2023\u002F02\u002F07\u002Fget-to-know-traceql-a-powerful-new-query-language-for-distributed-tracing\u002F\n\n## Getting help\n\nIf you have any questions or feedback regarding Tempo:\n\n- Grafana Labs hosts a [forum](https:\u002F\u002Fcommunity.grafana.com\u002Fc\u002Fgrafana-tempo\u002F40) for Tempo. This is a great place to post questions and search for answers.\n- Ask a question on the [Tempo Slack channel](https:\u002F\u002Fgrafana.slack.com\u002Farchives\u002FC01D981PEE5).\n- [File an issue](https:\u002F\u002Fgithub.com\u002Fgrafana\u002Ftempo\u002Fissues\u002Fnew\u002Fchoose) for bugs, issues and feature suggestions.\n- UI issues should be filed with [Grafana](https:\u002F\u002Fgithub.com\u002Fgrafana\u002Fgrafana\u002Fissues\u002Fnew\u002Fchoose).\n\n## OpenTelemetry\n\nTempo's receiver layer, wire format and storage format are all based directly on [standards](https:\u002F\u002Fgithub.com\u002Fopen-telemetry\u002Fopentelemetry-proto) and [code](https:\u002F\u002Fgithub.com\u002Fopen-telemetry\u002Fopentelemetry-collector) established by [OpenTelemetry](https:\u002F\u002Fopentelemetry.io\u002F).  We support open standards at Grafana!\n\nCheck out the [Integration Guides](https:\u002F\u002Fgrafana.com\u002Fdocs\u002Ftempo\u002Flatest\u002Fguides\u002Finstrumentation\u002F) to see examples of OpenTelemetry instrumentation with Tempo.\n\n## Other components\n\n### tempo-vulture\n[tempo-vulture](https:\u002F\u002Fgithub.com\u002Fgrafana\u002Ftempo\u002Ftree\u002Fmain\u002Fcmd\u002Ftempo-vulture) is Tempo's bird themed consistency checking tool.  It writes traces to Tempo and then queries them back in a variety of ways.\n\n### tempo-cli\n[tempo-cli](https:\u002F\u002Fgithub.com\u002Fgrafana\u002Ftempo\u002Ftree\u002Fmain\u002Fcmd\u002Ftempo-cli) is the place to put any utility functionality related to Tempo. See [Documentation](https:\u002F\u002Fgrafana.com\u002Fdocs\u002Ftempo\u002Flatest\u002Foperations\u002Ftempo_cli\u002F) for more info.\n\n## License\n\nGrafana Tempo is distributed under [AGPL-3.0-only](LICENSE). For Apache-2.0 exceptions, see [LICENSING.md](LICENSING.md).\n","Grafana Tempo 是一个高吞吐、低依赖的开源分布式追踪后端，专为大规模微服务环境设计。它仅依赖对象存储（如 S3、GCS），无需依赖数据库或消息队列，具备轻量部署与低成本扩展特性；深度集成 Grafana 生态（支持与 Prometheus、Loki 联合查询），并提供无需 TraceQL 的可视化分析界面（Traces Drilldown），支持 RED 指标概览、自动对比与点击式溯源。适用于云原生可观测性体系建设、微服务性能瓶颈定位、SRE 故障快速诊断等场景。",2,"2026-08-12 02:30:13","trending"]