You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently every time the cache is updated the entire data structure is dumped to the log file. This is setup to log at info level which is the production default. As the cache grows this will make the log harder and harder to parse. It will also lead to the log file growing in size rapidly. The billing data alone can grow to over 720 separate entries. This means a single dump of cache could be > 50kb of data. With a k8s max log file size of 10mb we probably want to log the most critical data only. For cache or csp-config updates possibly only the values that are changing.
This data could be helpful for debug though.
The text was updated successfully, but these errors were encountered:
Currently every time the cache is updated the entire data structure is dumped to the log file. This is setup to log at info level which is the production default. As the cache grows this will make the log harder and harder to parse. It will also lead to the log file growing in size rapidly. The billing data alone can grow to over 720 separate entries. This means a single dump of cache could be > 50kb of data. With a k8s max log file size of 10mb we probably want to log the most critical data only. For cache or csp-config updates possibly only the values that are changing.
This data could be helpful for debug though.
The text was updated successfully, but these errors were encountered: