Some context in ENG-10393.
Those metrics are helpful for two reasons:
- get_total_memory - gives us insight into total memory allocated, spikes in this value mean that we might have a lot of promises running at once which allocated a lot of resources - I described this theory in ENG-10393#comment-b874b5ec.
- get_used_memory - if this value grows over time we're experiencing memory leaks (except for session creation on the web, see below).
For the web, we might expect used memory to grow when using the app because we're keeping sessions in memory, which means after starting a conversation with a new user used memory should grow, but only for the size of the Session object. The logs could help us discover whether the in-memory store isn't too big, and if so - refactor this to avoid keeping all sessions live at once.
Looking at the transform-remove-console config we exclude error so should be fine.
Depends on D14484