google/mtail

extract internal monitoring data from application logs for collection in a timeseries database

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 17th, 2026
Created on May 27th, 2014
Open Issues & Pull Requests: 58 (+0)
GitHub issues: Enabled
Number of forks: 393
Total Stargazers: 4,031 (+0)
Total Subscribers: 63 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.0 hours
Mean response time: 46.7 days
90th percentile: 304.8 days
Tracked items: 17

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 747 days
Stale 30+ days: 15
Stale 90+ days: 15

Recent activity

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

Top labels

  • bug (5)
  • mtail-Language/VM (4)
  • enhancement (2)
  • help wanted (2)
  • mtail-Operating (2)
  • #noideadog (1)
  • mtail-Log Tailing (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

mtail is a log-based metrics extraction tool that parses application logs in real time to generate monitoring data for timeseries databases.

The tool solves the problem of extracting structured metrics from unstructured log output without modifying application code. mtail works by reading logs as they are written, applying pattern-matching rules defined in a custom language, and emitting metrics that can be collected by monitoring systems. It uses a compiler and virtual machine approach to execute these extraction programs efficiently, allowing operators to define what data should be extracted through declarative mtail program files rather than requiring application changes.

mtail suits environments where applications already produce detailed logs but lack native instrumentation, or where adding instrumentation would require code changes. It works well for legacy applications, third-party software, or situations where log parsing is preferable to modifying application behavior. The tool integrates with Prometheus and other timeseries databases through standard collection mechanisms, making it useful in observability pipelines that already depend on those systems.

Development on the project shows consistent activity across multiple areas. The codebase receives regular updates to the core extraction and compilation logic. Work continues on the mtail program language itself, including its syntax and semantics. The test suite is actively maintained with new test cases being added. Documentation receives ongoing attention with updates to guides and examples. The project maintains a pattern of addressing issues and incorporating feedback from users running mtail in production environments.