note that the team managing vespamgr is only coordinating. Actual user stories to be created against components that actually generate statistics.

First item (managed as own Epic) for platform stats could be RIC-30.

We also considered:

RIC-69-A: E2M also keep statistics on how many reconnects for a particular gNB (just a cumulative counter). This could be some additional statistics collected by RIC.

RIC-69-B: Subscription manager generating per E2 connection statistics on subscription latencies (subscription request up to subscription response). This is based on artificial messages. Probably no existing messages fit well. We did not like the idea of using illegal RAN function ID to get back a failure. So further thinking needed.

RIC-69-C: Simple number of messages by gNB connections (The E2 termination-measured latencies item (RIC-30) already lists this as backup plan)

ideas:

RMR statistics in some container (e.g. E2M)

Routing manager statistics related to routes