add our metrics effort to the short-term roadmap (#403)

* add our metrics effort to the short-term roadmap

* remove resource manager metrics

Co-authored-by: Max Inden <mail@max-inden.de>

Co-authored-by: Max Inden <mail@max-inden.de>

ROADMAP.md

@@ -21,6 +21,7 @@ third-party ownership of data.
         - [🤖 libp2p as a WASM library](#🤖-libp2p-as-a-wasm-library)
     - [Evolve](#evolve)
         - [🕸 Unprecedented global connectivity](#🕸-unprecedented-global-connectivity)
+        - [⏱ Full Observability)(#⏱-full-observability)
         - [🧪 Automated compatibility testing](#🧪-automated-compatibility-testing)
         - [🤝 Low latency, efficient connection handshake](#🤝-low-latency-efficient-connection-handshake)
         - [🛣️ Peer Routing Records](#🛣️-peer-routing-records)
@@ -248,6 +249,23 @@ rest of the system.
 
 - [NAT traversal tracking issue](https://github.com/libp2p/specs/issues/312).
 
+
+### ⏱ Full Observability
+
+**What?** libp2p should expose a wide set of metrics, making it easy to
+monitor the system.
+
+Metrics should include:
+- Transport metrics (TCP, QUIC, security protocols, stream multiplexers)
+- Swarm metrics
+- other subsystems (AutoNAT, AutoRelay, Hole Punching)
+
+**Why?** A system that cannot be monitored will misbehave - sooner or later.
+
+**Links:**
+
+- [go-libp2p discussion](https://github.com/libp2p/go-libp2p/issues/1356)
+
 ### 🧪 Automated compatibility testing
 
 **What?** There are more than 6 implementations of the [libp2p specification] in