Mingwei Samuel

So I believe we could get full ("record-level") `tracing`-support for provenance/lineage by carrying a `u64` `ID` alongside each item in the dataflow, in the hot path.[[src](https://docs.rs/tracing/0.1.41/src/tracing/span.rs.html#348-368)]. The user would want...

## Full Tracing I spent a few days studying how full record-level tracing/provenance/lineage could work in DFIR. This will cover my dive into how the `tracing` crate works and how...

Looking into how best to instrument execution of subgraphs. [`tokio-metrics` provides comprehensive general instrumentation of async tasks](https://docs.rs/tokio-metrics/latest/tokio_metrics/struct.TaskMetrics.html), but testing using it in DFIR shows 15% longer runtime on some microbenchmarks....

blocked by https://github.com/nico-abram/blondie/issues/68

My comments from tracking issue #2178 > Looking into how best to instrument execution of subgraphs. [`tokio-metrics` provides comprehensive general instrumentation of async tasks](https://docs.rs/tokio-metrics/latest/tokio_metrics/struct.TaskMetrics.html), but testing using it in DFIR...

I think we can start with a few important metrics per subgraph execution: * `total_poll_duration` - amount of time the subgraph is running * `total_poll_count` - how many times the...

Some Dfir-runtime level metrics would be external events received

TODO - make the metrics have interior mutability so we don't have to worry about &mut Dfir lifetime? TODO - change setup so handoff vs subgraph are recorded as dimensions...

Basically, convert `_counter()` to use the new metrics system created by #2178/#2228 Old name: > Offer operators to send custom metrics to OTel / Prometheus

Actually I guess we need to test against the local website build