Metrics

Capture metrics about code execution in a vendor agnostic way. As the author of many libraries which would benefit from metrics, there are few key priorities: (1) zero overhead if metrics are disabled, minimal overhead if enabled, and (2) a small and opinionated interface with standardised semantics.

• Zero-overhead if tracing is disabled and minimal overhead if enabled.
• Small opinionated interface with standardised semantics.

Please see the project documentation for more details.

• Getting Started - This guide explains how to use metrics for capturing run-time metrics.

• Capture - This guide explains how to use metrics for exporting metric definitions from your application.

• Testing - This guide explains how to write assertions in your test suite to validate metrics are being emitted correctly.

Please see the project releases for all releases.

• Introduce Metrics::Config to Expose prepare Hook

We welcome contributions to this project.

1. Fork it.
2. Create your feature branch (git checkout -b my-new-feature).
3. Commit your changes (git commit -am 'Add some feature').
4. Push to the branch (git push origin my-new-feature).
5. Create new Pull Request.

In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.

This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.

• metrics-backend-datadog — A Metrics backend for Datadog.
• traces — A code tracing interface which follows a similar pattern.