code of conduct

NOTE: All conversations and contributions to this project shall adhere to the Code of Conduct.

what's it all about?

Running applications in production can be hard when you don't have insight into what the application is doing. We're lucky to have so many good system monitoring programs and services to show us how our servers are performing, but we still have to do the work of instrumenting our applications to gain deep insight into their behavior and performance.

metrics makes it easy to instrument your application to provide real-time insight into what's happening. It provides a number of practical features that make it easy for library and application authors to start collecting and exporting metrics from their codebase.

why would I collect metrics?

Some of the most common scenarios for collecting metrics from an application:

• see how many times a codepath was hit
• track the time it takes for a piece of code to execute
• expose internal counters and values in a standardized way

Importantly, this works for both library authors and application authors. If the libraries you use are instrumented, you unlock the power of being able to collect those metrics in your application for free, without any extra configuration. Everyone wins, and learns more about their application performance at the end of the day.

project layout

The Metrics project provides a number of crates for both library and application authors.

If you're a library author, you'll only care about using metrics to instrument your library. If you're an application author, you'll likely also want to instrument your application, but you'll care about "exporters" as a means to take those metrics and ship them somewhere for analysis.

Overall, this repository is home to the following crates:

• metrics: A lightweight metrics facade, similar to log.
• metrics-tracing-context: Allow capturing tracing span fields as metric labels.
• metrics-exporter-tcp: A metrics-compatible exporter for serving metrics over TCP.
• metrics-exporter-prometheus: A metrics-compatible exporter for serving a Prometheus scrape endpoint.
• metrics-util: Helper types/functions used by the metrics ecosystem.

community integrations and learning resources

As well, there are also some community-maintained exporters and other integrations:

• metrics-exporter-statsd: A metrics-compatible exporter for sending metrics via StatsD.
• metrics-exporter-newrelic: A metrics-compatible exporter for sending metrics to New Relic.
• metrics-exporter-sentry: A metrics-compatible exporter for sending metrics to Sentry.
• opinionated_metrics: Opinionated interface to emitting metrics for CLI/server applications, based on metrics.
• metrics-dashboard: A dashboard for visualizing metrics from metrics.

Additionally, here are some learning resource(s) to help you get started:

• Rust Telemetry Workshop from MainMatter (includes more than just metrics, as well).

MSRV and MSRV policy

Minimum supported Rust version (MSRV) is currently 1.71.1, enforced by CI.

metrics will always support at least the latest four versions of stable Rust, based on minor version releases, and excluding patch versions. Overall, we strive to support older versions where possible, which means that we generally try to avoid staying up-to-date with every single dependency (except for security/correctness reasons) and avoid bumping the MSRV just to get access to new helper methods in the standard library, and so on.

contributing

To those of you who have already contributed to metrics in some way, shape, or form: a big, and continued, "thank you!" ❤️

To everyone else that we haven't had the pleasure of interacting with: we're always looking for thoughts on how to make metrics better, or users with interesting use cases. Of course, we're also happy to accept code contributions for outstanding feature requests directly. 😀

We'd love to chat about any of the above, or anything else related to metrics. Don't hesitate to file an issue on the repository, or come and chat with us over on Discord.