Skip to content

refactor!: use new iroh-metrics version, no more global tracking #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
May 7, 2025

Conversation

Frando
Copy link
Member

@Frando Frando commented Apr 9, 2025

Description

Adapts iroh-metrics for n0-computer/iroh-metrics#15 and n0-computer/iroh#3262

Depends on n0-computer/iroh#3262

Breaking Changes

  • metrics::Metrics now implements MetricsGroup from the ì[email protected]`
  • Metrics are no longer tracked into the static_core from iroh-metrics, but instead are tracked per Gossip and exposed via Gossip::metrics
  • proto::state::State::handle now takes Option<&Metrics> as new 4th parameter

Notes & open questions

Change checklist

  • Self-review.
  • Documentation updates following the style guide, if relevant.
  • Tests if relevant.
  • All breaking changes documented.

@Frando Frando force-pushed the refactor/metrics branch from 3ab53fe to b2106d3 Compare April 9, 2025 13:02
Copy link

github-actions bot commented Apr 9, 2025

Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh-gossip/pr/58/docs/iroh_gossip/

Last updated: 2025-05-06T21:41:21Z

@n0bot n0bot bot added this to iroh Apr 9, 2025
@github-project-automation github-project-automation bot moved this to 🏗 In progress in iroh Apr 9, 2025
@Frando Frando marked this pull request as ready for review April 30, 2025 08:42
@Frando Frando added this to the v0.35.0 milestone May 5, 2025
github-merge-queue bot pushed a commit to n0-computer/iroh that referenced this pull request May 5, 2025
## Description

Depends on n0-computer/net-tools#20

Until now, we were using a superglobal static `iroh_metrics::core::Core`
struct to collect metrics into. This allowed us to use macros to track
metrics from anywhere in the codebase. However, this also made it
impossible to collect metrics *per endpoint*, which is what you want
usually as soon as you have more than one endpoint in your app.

This PR builds on n0-computer/iroh-metrics#15,
n0-computer/iroh-metrics#22, and n0-computer/iroh-metrics#23. It removes
the global metrics collection from all crates in the iroh repository.
Instead, we now create and pass metrics collector structs to all places
where we need to collect metrics.

This PR disables the `static_core` feature from iroh-metrics, which
means the macros for superglobal metrics collection are not available
anymore. This is good, because otherwise we could easily miss metrics
not tracked onto the proper metrics collector.

This PR also updates iroh-dns-server and iroh-relay to use manual
metrics collection.

While this means that we have to pass our metrics structs to more
places, it also makes metrics collection more visible, and we can now
also split the metrics structs further easily if we want to separate
concerns more.

This PR should not change anything apart from metrics collection. Most
places are straightforward conversions from the macros to methods on the
metrics collectors. At a few places, logic was changed slightly to move
metrics collection a layer up to save a few clones.

## Breaking Changes

* All metrics structs (`iroh::metrics::{MagicsockMetrics,
PortmapMetrics, NetReportMetrics}`) now implement `MetricsGroup` from
the new version `0.34` of `iroh-metrics` and no longer implement traits
from `[email protected]`.
* Metrics are no longer registered onto the static superglobal `Core`.
`iroh` does not use `static_core` feature of `iroh-metrics`. Metrics are
now exposed from the subsystems that track them, see e.g.
`Endpoint::metrics`.

Several methods now take a `Metrics` argument. You can always pass
`Default::default` if you don't want to unify metrics tracking with
other sections.

#### `iroh`

* `iroh::metrics::{MagicsockMetrics, NetReportMetrics, PortmapMetrics}`
all are now marked `non_exhaustive`, and implement
`iroh_metrics::MetricsGroup` from `[email protected]` and no longer
implement `iroh_metrics::Metric` from `[email protected]`. They also no
longer implement `Clone` (put them into an `Arc` for cloning instead).

* `iroh::net_report::Client::new` now takes
`iroh::net_report::metrics::Metrics` as forth argument

#### `iroh-dns-server`
* `iroh_dns_server::server::Server::spawn` now takes `Metrics` as third
argument
* `iroh_dns_server::ZoneStore::persistent` now takes `Metrics` as third
argument
* `iroh_dns_server::ZoneStore::in_memory` now takes `Metrics` as third
argument
* `iroh_dns_server::ZoneStore::new` now takes `Metrics` as third
argument
* `iroh_dns_server::state::AppState` now has a public `metrics: Metrics`
field
* `iroh_dns_server::dns::DnsHandler::new` now takes `Metrics` as third
argument
* function `iroh_dns_server::metrics::init_metrics` is removed

#### `iroh-relay`

* `iroh_relay::metrics::{StunMetrics, Metrics}` all are now marked
`non_exhaustive`, and implement `iroh_metrics::MetricsGroup` from
`[email protected]` and no longer implement `iroh_metrics::Metric` from
`[email protected]`. They also no longer implement `Clone` (put them
into an `Arc` for cloning instead).

## Notes & open questions

<!-- Any notes, remarks or open questions you have to make about the PR.
-->

## Change checklist
<!-- Remove any that are not relevant. -->
- [x] Self-review.
- [x] Documentation updates following the [style
guide](https://rust-lang.github.io/rfcs/1574-more-api-documentation-conventions.html#appendix-a-full-conventions-text),
if relevant.
- [x] Tests if relevant.
- [x] All breaking changes documented.
- [x] List all breaking changes in the above "Breaking Changes" section.
- [x] Open an issue or PR on any number0 repos that are affected by this
breaking change. Give guidance on how the updates should be handled or
do the actual updates themselves.
    - [x] [`iroh-gossip`](https://github.com/n0-computer/iroh-gossip)
      - n0-computer/iroh-gossip#58
    - [x] [`iroh-blobs`](https://github.com/n0-computer/iroh-blobs)
      - n0-computer/iroh-blobs#85
    - [x] [`iroh-docs`](https://github.com/n0-computer/iroh-docs)
      - n0-computer/iroh-docs#41

---------

Co-authored-by: dignifiedquire <[email protected]>
@Frando Frando changed the title refactor: use new iroh-metrics version, no more global tracking refactor!: use new iroh-metrics version, no more global tracking May 7, 2025
@Frando Frando merged commit 2a37214 into main May 7, 2025
26 of 27 checks passed
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in iroh May 7, 2025
ramfox pushed a commit to n0-computer/iroh-docs that referenced this pull request May 12, 2025
## Description

Updates metrics tracking to the new non-global tracking.

Metrics are tracked per sync actor.

We previously tracked a few metrics within the replica, this is removed
and instead tracked from the sync actor now.

Depends on n0-computer/iroh#3262
Depends on n0-computer/iroh-blobs#85
Depends on n0-computer/iroh-gossip#58

## Breaking Changes

* `metrics::Metrics` now implements `MetricsGroup` from the recent
ìroh-metrics` release (TODO: fill in version after release)
* Metrics are no longer tracked into the `static_core` from
`iroh-metrics`, but instead are tracked per `Engine` and exposed via
`Engine::metrics`

## Notes & open questions

<!-- Any notes, remarks or open questions you have to make about the PR.
-->

## Change checklist

- [x] Self-review.
- [x] Documentation updates following the [style
guide](https://rust-lang.github.io/rfcs/1574-more-api-documentation-conventions.html#appendix-a-full-conventions-text),
if relevant.
- [x] Tests if relevant.
- [x] All breaking changes documented.
@Frando Frando deleted the refactor/metrics branch May 13, 2025 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

2 participants