Agent, memory handling and preserving result messages

[bondskin]

Hi,

I define CPU and memory limits on my containers and I did the same for the NO Agent.
There was no issue with the limit of 256M RAM but since yesterday it hits the limit.

Buffered backlog: 67481 result message(s) (~39596 KB) will flush once the tunnel connects
Tunnel error: Status(StatusCode="Cancelled", Detail="Bad gRPC response. Invalid content-type value: text/html")
Heartbeat error: Exception of type 'System.OutOfMemoryException' was thrown.
Buffered backlog: 67481 result message(s) (~39596 KB) will flush once the tunnel connects
Tunnel error: Status(StatusCode="Cancelled", Detail="Bad gRPC response. Invalid content-type value: text/html")
Heartbeat error: Exception of type 'System.OutOfMemoryException' was thrown.
Buffered backlog: 67481 result message(s) (~39596 KB) will flush once the tunnel connects
Tunnel error: Status(StatusCode="Cancelled", Detail="Bad gRPC response. Invalid content-type value: text/html")
Heartbeat error: Exception of type 'System.OutOfMemoryException' was thrown.
Buffered backlog: 67481 result message(s) (~39596 KB) will flush once the tunnel connects

While the root cause is entirely with me, I recognised that the result messages are not stored as a file but obviously only in RAM within the container.
Wouldn't it make sense to store the data in a file so that the gathered data surives a container restart/new compose?
Or is the RAM as storage a security consideration?

PS. please ignore the gRPC, I am still fine-tuning Crowdsec with the new bot-challenge feature