chore: added API boundary nodes metrics

[nikolay-komarevskiy]

No description provided.

[blind-oracle]

I've looked and I think maybe we can just plug this functionality into MetricsRunner that already exists. It is already doing similar stuff like record memory statistics etc. WDYT?

[nikolay-komarevskiy]

I've looked and I think maybe we can just plug this functionality into MetricsRunner that already exists. It is already doing similar stuff like record memory statistics etc. WDYT?

My personal preference is to have a separate task with a dedicated responsibility. That's also why Run trait is there. Separation brings more clarity and makes maintenance easier IMO. But if You feel strong about putting it into MetricsRunner, I can change it.

[blind-oracle]

From my perspective more entities make it instead hard to maintain, MetricsRunner was added to solve exactly this purpose - run stuff periodically and record the results as metrics (and to generate the cache). Adding another thing that does the same... well, a lot of boilerplate for two lines of actual code I think. But, up to you