We’ll be using the K8s360 dashboard to track the Recommendation service issue
Due to the nature of this feature flag, it will take several minutes until we can clearly see the impact.
Open the K8s360 app in your Logz.io account.
Let’s filter for the astronomy namespace using the filters on the left side:
If we expore these tabs one by one:
We’ll notice that astronomy-shop-recommendationservice appears first in the Memory and Restarts tabs.
Memory
Restarts
Click on the astronomy-shop-recommendationservice card and select the Metrics tab, you’ll see spikes in memory usage
Go back to the Pods tab, click on your pod and open the Memory tab there, you’ll see spikes in memory and container restarts
We’ve found the memory leak issue in the Recommendation service, please review your application’s code!