We might also drive such a RMR-to-prometheus adpater as a component that can be changed to RMR-to-direct-VES events component. 

I marked this as crossteam as it might be another team that picks this up, e.g., a team that needs this functionality and can't use existing REST libraries fro C++ or Golang that support the Prometheus-ways out of the box.

Note that this is mapped to VESPA manager, but an implementation probably needs a new component.

2020-05-26: Originally this was planned to be used by E2T, but E2T directly exposes Prometheus interface now. I.e., RIC-30 and RIC-358 do not depend on this anymore. By now, we are thinking this might still come as requirement from xApps so that xApps send RMR messages to some adapter (not yet implemented) instead of directly exposing Prometheus stats (implemented on framework side).

Note that RIC-420 is a different approach as RIC-420 bypasses prometheus.