awesome-repositories.com
Blog
MCP
awesome-repositories.com

Descubre los mejores repositorios open-source con nuestra búsqueda potenciada por IA.

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoServidor MCPAcerca deCómo clasificamosPrensa
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
grafana avatar

grafana/tempo

0
View on GitHub↗
5,079 estrellas·661 forks·Go·agpl-3.0·13 vistasgrafana.com/oss/tempo↗

Tempo

Grafana Tempo is a high-scale distributed tracing backend and columnar trace database. It serves as an observability data store that persists and queries spans and traces using OpenTelemetry standards, allowing for the analysis of request flows across microservices.

The system distinguishes itself by using an object-store based backend with columnar Parquet storage. This architecture enables efficient attribute searching and large-scale data retrieval through dedicated attribute columnization and block-based data partitioning. It includes a specialized TraceQL query engine for filtering traces based on span relationships and attribute metadata.

The platform covers broad telemetry capabilities, including observability data correlation that links traces with logs and metrics. It provides service performance monitoring by generating request rates, error rates, and duration metrics from trace spans, while offering tools for sensitive trace redaction and tenant-isolated data sharding.

The system supports the retrieval of traces via hexadecimal identifiers and the execution of searches over specified time ranges using TraceQL.

Features

  • Trace Event Columnar Stores - Organizes trace data into columnar Parquet files to enable efficient attribute filtering and high-performance retrieval.
  • Distributed Tracing - Tracks requests across multiple services using unique identifiers to identify performance bottlenecks and transaction failures.
  • OpenTelemetry Compliance - Persists and queries spans and traces using OpenTelemetry standards and columnar formats.
  • Distributed Tracing Backends - Persists trace data from services to reconstruct and visualize request flows across a distributed system.
  • Trace Identifier Retrieval - Enables fetching a specific trace using its hexadecimal identifier to analyze a single request path.
  • Object Storage Persistence - Persists data blocks in cloud object storage to ensure scalability and durability of distributed trace records.
  • Dedicated Attribute Columnization - Promotes frequently queried attributes to their own storage columns to avoid scanning full data blocks.
  • Time-Based Segment Partitioning - Segments trace data into time-bounded blocks with associated index files for faster searching and deletion.
  • Observability Platforms - Serves as an observability data store that aggregates and correlates traces, logs, and metrics.
  • Metric and Performance Monitors - Generates request rates, error rates, and duration metrics from trace spans to monitor system health.
  • Trace-Derived Metric Aggregations - Calculates rates, counts, and quantiles over trace results to identify trends and performance issues.
  • Trace Data Producers - Enables emitting span information tied to a common trace ID to track requests across distributed systems.
  • Performance Tracing Platforms - Provides a high-scale platform for recording, storing, and analyzing distributed trace data to identify performance bottlenecks.
  • Telemetry Correlation - Links traces with logs and metrics to provide a unified view of system telemetry during root cause analysis.
  • Trace Querying - Supports searching for traces over a specified time range using the specialized TraceQL query language.
  • Block Storage - Lists block information, compaction summaries, and cache statistics for managing data at the block level.
  • Time-Series Block Storage Queries - Scans storage blocks within a time range for specific attribute key-value pairs.
  • Columnar Storage Engines - Persists trace data using a columnar storage format to ensure data remains portable for external analysis engines.
  • Attribute Filtering - Allows listing values for specific attributes and filtering results using a query language to isolate specific events.
  • Span Filters - Enables searching for traces based on names, durations, and status codes using boolean logic.
  • Trace Metric Aggregation - Processes trace spans through an aggregation pipeline to derive request rates, error rates, and duration metrics.
  • Block-Based Indexing - Generates index files for storage blocks to optimize the searching and retrieval of specific trace attributes.
  • Span-Level Query Optimization - Reduces retrieval latency and memory usage by processing individual data spans instead of full traces.
  • Aggregation Pipelines - Processes spans through pipelines to calculate counts, averages, and sums for trace analysis.
  • Multi-Tenant Isolation Layers - Separates storage blocks and configuration overrides by tenant identifiers to support multi-tenant environments.
  • Distributed Transaction Analysis - Tracks requests across service boundaries to identify the exact location of failures within complex distributed transactions.
  • Exemplar Queries - Identifies specific traces that contributed to a calculated metric value to provide context for performance spikes.
  • Trace Data Redaction - Rewrites storage blocks to remove specified trace identifiers to ensure data privacy and compliance.
  • Trace Linking - Associates specific trace identifiers with aggregated metric values to provide direct navigation from signals to traces.
  • Telemetry Lifecycle Management - Manages the lifecycle of trace data, including indexing attributes, migrating tenant data, and redacting sensitive information.
  • Relationship-Based Querying - Identifies traces where specific spans appear as children or descendants to map request flows between services.
  • Trace Visualization - Generates automatic visual representations of trace data to uncover related issues without manual querying.
  • Request Latency Sampling - Visualizes the path and duration of requests across multiple services to detect and analyze latency bottlenecks.
  • Monitoring Backends - High-volume, distributed tracing backend for application performance.
  • Monitoring and Alerting - Distributed tracing system.

Historial de estrellas

Gráfico del historial de estrellas de grafana/tempoGráfico del historial de estrellas de grafana/tempo

Búsqueda con IA

Explora más repositorios increíbles

Describe lo que necesitas en lenguaje sencillo: la IA clasifica miles de proyectos open-source curados por relevancia.

Start searching with AI

Alternativas open-source a Tempo

Proyectos open-source similares, clasificados según cuántas características comparten con Tempo.
  • uptrace/uptraceAvatar de uptrace

    uptrace/uptrace

    4,098Ver en GitHub↗

    Uptrace is an OpenTelemetry-based observability platform designed to collect, store, and analyze distributed traces, metrics, and logs. It functions as a centralized logging backend, a distributed tracing system, and a metrics engine to monitor application performance and system health. The platform is distinguished by AI-powered operational capabilities, allowing users to query telemetry data and manage monitoring dashboards using natural language. It specifically includes specialized monitoring for generative AI pipelines, tracking token usage and response quality for LLM interactions and r

    Goapmapplication-monitoringclickhouse
    Ver en GitHub↗4,098
  • victoriametrics/victoriametricsAvatar de VictoriaMetrics

    VictoriaMetrics/VictoriaMetrics

    16,343Ver en GitHub↗

    VictoriaMetrics is a high-performance, scalable time series database and observability platform designed for long-term storage and analysis of metric, log, and trace data. It functions as a unified backend for monitoring ecosystems, offering full compatibility with industry-standard protocols and query languages. The system is built to handle massive data volumes through a distributed architecture that supports horizontal scaling and efficient data lifecycle management. The platform distinguishes itself through a storage engine that utilizes consistent hashing for data sharding and log-struct

    Godatabasegrafanagraphite
    Ver en GitHub↗16,343
  • jaegertracing/jaegerAvatar de jaegertracing

    jaegertracing/jaeger

    22,890Ver en GitHub↗

    Jaeger is a distributed tracing platform used for collecting, storing, and visualizing request flows across microservices. It identifies performance bottlenecks and errors by tracking requests as they move through multiple service boundaries. The system includes telemetry collectors, a multi-tenant backend, and a trace visualizer. The platform provides a multi-tenant tracing infrastructure that isolates data and queries by tenant to support shared environments. It supports standardized telemetry ingestion via the OpenTelemetry Protocol over gRPC and HTTP. To manage storage costs and overhead,

    Gocncfdistributed-tracinghacktoberfest
    Ver en GitHub↗22,890
  • google/perfettoAvatar de google

    google/perfetto

    5,558Ver en GitHub↗

    Perfetto is a platform for system-level performance tracing and analysis on Linux and Android. It combines a high-throughput trace recorder, a SQL-based query engine, and a browser-based visualizer into a single toolchain. The platform covers CPU scheduling and call-stack profiling, native and Java heap memory allocation tracking, GPU and graphics events, and system-wide counters such as CPU frequency and power consumption. The architecture decouples trace recording from offline analysis, using a compact protobuf format for event encoding and columnar storage for efficient SQL queries. The we

    C++
    Ver en GitHub↗5,558
Ver las 30 alternativas a Tempo→

Preguntas frecuentes

¿Qué hace grafana/tempo?

Grafana Tempo is a high-scale distributed tracing backend and columnar trace database. It serves as an observability data store that persists and queries spans and traces using OpenTelemetry standards, allowing for the analysis of request flows across microservices.

¿Cuáles son las características principales de grafana/tempo?

Las características principales de grafana/tempo son: Trace Event Columnar Stores, Distributed Tracing, OpenTelemetry Compliance, Distributed Tracing Backends, Trace Identifier Retrieval, Object Storage Persistence, Dedicated Attribute Columnization, Time-Based Segment Partitioning.

¿Qué alternativas de código abierto existen para grafana/tempo?

Las alternativas de código abierto para grafana/tempo incluyen: uptrace/uptrace — Uptrace is an OpenTelemetry-based observability platform designed to collect, store, and analyze distributed traces,… victoriametrics/victoriametrics — VictoriaMetrics is a high-performance, scalable time series database and observability platform designed for long-term… jaegertracing/jaeger — Jaeger is a distributed tracing platform used for collecting, storing, and visualizing request flows across… google/perfetto — Perfetto is a platform for system-level performance tracing and analysis on Linux and Android. It combines a… coroot/coroot — Coroot is an observability platform and Kubernetes performance monitor that utilizes eBPF to automatically collect… openobserve/openobserve — OpenObserve is a unified observability data platform designed to ingest, store, and analyze logs, metrics, and traces.…