---
# System prepended metadata

title: EPF Cohort 6 – Week 20 Update

---

# EPF Cohort 6 – Week 20 Update 

## News:

- **[first version of tracing](https://github.com/grandinetech/grandine/commit/384378e40cfc15fc7b51edc10e7ced298d07d734)** from now **on Grandine pre-release**!
![Screenshot from 2025-11-01 17-51-43](https://hackmd.io/_uploads/Skm9i3XyZx.png)

- PR: **[Two-Layer Tracing Subscriber Design with Dedicated Exception Log File and Local Timezone Support + Developer Controls + Tests #432](https://github.com/grandinetech/grandine/pull/432)** completed, tested and **merged** on grandine main branch

- PR: [logging format: introduce AlignedFormatter for aligned log output with optional ANSI colors #447](https://github.com/grandinetech/grandine/pull/447) on hold, if Grandine ever decide to go with full customized output

- **new important PR**: **[rotate exception.log when it exceeds 1GB #456](https://github.com/grandinetech/grandine/pull/456)** implemented, tested and verified *(waiting for review)* 

- master **exams cracked now** (and now **101% focus** into **ethereum**)

---
## Next

As discussed in **[issue #451](https://github.com/grandinetech/grandine/issues/451)** am currently researching metrics.
Also Argentina is close enough and **hype is real :D** ! So I should start writing my final report and preparing my presentation!
This cohort was fantastic! I grew with you guys, learned a lot, and I am better and faster day by day. I love the community, I love discussions at the office hours, even when I didn’t understand something at that particular moment, they gave me a great direction for research in this deep blockchain sea.

I also can’t wait to witness the launch of **Fusaka** (in the P2P Grandine submodule I’ve been merging all my tracing changes into the **peerdas branch**. I can see the community hype, and it feels like it’s really close, so let’s see what happens!

And now back to the tracing:

In the next few days, I’ll try to find a more direct way to connect metrics after the tracing integration.
Right now, I’m learning how they are collected in Grandine. I see that Grandine uses a Prometheus server, which hits Grandine’s endpoints and pulls prepared information (Grandine’s setup keeps them cached for when Prometheus calls for them).

However, tracing doesn’t natively provide numerical aggregates like Prometheus does. When I instrument code, I can export data to tracing backends such as Jaeger or Tempo (Tempo was mentioned as a recommendation in one of the previous office hours), but that wouldn’t help me with system-level stats.

So I am thinking about some kind of hybrid approach where I’d keep metrics for system data, but use tracing for beacon chain operations or something similar.
I’m also sure I’ll get some new ideas after attending the [Tempo webinar](https://grafana.com/go/webinar/getting-started-with-tracing-and-grafana-tempo/?pg=oss-tempo&plcmt=quick-links).

## Resources

- **[Grandinetech](https://github.com/grandinetech)**
- [Tempo](https://grafana.com/oss/tempo/)
- [Jaeger](https://grafana.com/docs/grafana/latest/datasources/jaeger/)
- [fs-err](https://crates.io/crates/fs-err)
