m3
by
m3db

Description: M3 monorepo - Distributed TSDB, Aggregator and Query Engine, Prometheus Sidecar, Graphite Compatible, Metrics Platform

View on GitHub ↗

Summary Information

Updated 1 hour ago
Added to GitGenius on March 6th, 2022
Created on June 14th, 2016
Open Issues & Pull Requests: 218 (+0)
Number of forks: 465
Total Stargazers: 4,892 (+0)
Total Subscribers: 108 (+0)

Issue Activity (beta)

Open issues: 60
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,505 days
Stale 30+ days: 60
Stale 90+ days: 59

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • area:db (122)
  • P: Medium (36)
  • area:documentation (25)
  • area:coordinator (24)
  • P: Low (22)
  • area:query (20)
  • T: Bug (19)
  • T: Beginner (17)

Most active issues this week

No issue events were indexed in the last 7 days.

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 402.8 days
90th percentile: 1168.3 days
Tracked items: 10

Most active contributors

Detailed Description

M3 is a comprehensive metrics platform distributed as a monorepo written in Go. The project provides a distributed time series database (TSDB), a query engine, a Prometheus sidecar, a metrics aggregator, and Graphite-compatible storage and query capabilities. The platform is designed to handle large-scale metrics collection, storage, and querying across distributed systems.

The core components of M3 address different aspects of the metrics pipeline. The distributed TSDB serves as the primary storage layer for time series data, while the query engine enables efficient retrieval and analysis of metrics. The Prometheus sidecar allows M3 to integrate directly with Prometheus deployments, facilitating metrics ingestion from existing Prometheus infrastructure. The metrics aggregator component handles real-time aggregation of metrics streams, and the Graphite compatibility layer ensures that organizations using Graphite can leverage M3's capabilities without significant migration overhead.

According to GitGenius activity tracking, the repository shows a median issue and pull request response latency of 0.0 hours across sampled items, indicating rapid engagement with community contributions. However, the mean response latency of 9666.6 hours suggests occasional delays on some items, reflecting the variable nature of open source maintenance. The most active contributors tracked by GitGenius include kentzeng12 with 12 recorded events, andrewmains12 with 3 events, and arnav-chakraborty with 2 events. The project maintains overlapping contributors with golang/go, perses/perses, and clickhouse/clickhouse, indicating cross-pollination with other significant open source projects in the observability and database ecosystems.

The repository is classified across multiple domains reflecting its broad scope: distributed systems, time series database, metrics storage, high availability, scalability, cloud-native architecture, aggregation, query engines, and observability. These classifications underscore M3's positioning as a production-grade platform designed for organizations requiring reliable, scalable metrics infrastructure.

M3 provides multiple pathways for users to get started, with Docker-based quickstart options prominently featured in the documentation. The project maintains comprehensive documentation at m3db.io, community engagement through Slack channels and Google Groups forums, and regular community meetings with recorded sessions available on Vimeo. The contribution process is formalized through a contributing guide, and the project welcomes pull requests and community feedback through GitHub issues, Slack, and the public forum. The codebase is released under the Apache License, Version 2.0, making it freely available for both commercial and open source use.

m3
by
m3dbm3db/m3

Repository Details

Fetching additional details & charts...