Control charts cached/previous data size

[calvellido]

In a typical usecase of the Freestyle Opscenter, you will be changing from different microservices specific charts... We need to set the behaviour we'd like to have on this, specifically:

• What amount of data should still be on the chart when we get back to it after a comeback? In theory we can leave the connection open in the background so when we go back we still have all data available, but to what would be our limit? We have to consider that if we navigate some amount of them, memory and app performance could be taking a hit. Maybe to have settled responses we should only show data starting on the moment we navigate there.

• Will all charts start listening on the moment we navigate to a specific section on the page, or are we going to wait for a confirmation on the user side?

[raulraja]

The data that is shown is irrelevant in the frontend because the frontend would just connect to a service with an offset and the backend will be responsible from starting streaming on each connection given that offset. As you move through the charts you are fine destroying their object and recreating their state if needed because the client will reconnect with the server and request streaming since it's last position.