Hello.
As of today, when SBA shows the details of an instance, it has to do N+1 calls to the server to:
- fetch the list of available metrics (1)
- fetch each single metric value (N)
The improvement requested here is to aggregate all the metrics in a single DTO and publish that one instead, ideally through event subscription like it already happens with the journal, so that the UI shouldn't have to manually poll them every time.
Of course, there will still be N+1 network calls, but now only between SBA server and the target application instance and not, as of today, N+1 between SBA UI and SBA server and N+1 between SBA server and target instance.
Moreover, for the monitored services, they will always be N+1 and not M(N+1) where M is the number of SBA UIs open.
The same can then simply be reused in the metrics view of an instance by picking/filtering only the metrics of interest (the ones selected).
Hello.
As of today, when SBA shows the details of an instance, it has to do N+1 calls to the server to:
The improvement requested here is to aggregate all the metrics in a single DTO and publish that one instead, ideally through event subscription like it already happens with the journal, so that the UI shouldn't have to manually poll them every time.
Of course, there will still be N+1 network calls, but now only between SBA server and the target application instance and not, as of today, N+1 between SBA UI and SBA server and N+1 between SBA server and target instance.
Moreover, for the monitored services, they will always be N+1 and not M(N+1) where M is the number of SBA UIs open.
The same can then simply be reused in the metrics view of an instance by picking/filtering only the metrics of interest (the ones selected).