{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Debugging Intermittent Kong 503s When the Logs Showed Nothing but the Status Code","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/2a159223\"></iframe>","width":"100%","height":180,"duration":399,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/debugging-intermittent-kong-503s-when-the-logs-showed-nothing-but-the-status-code.\nInvestigating intermittent Kong 503 errors with quiet logs, tracing the failure to an NGINX worker restart caused by Kubernetes memory pressure.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #kong-gateway, #kong, #nginx, #nginx-worker-restart, #kubernetes-oom, #lua-vm-metrics, #api-gateway-debugging, #sre-incident-analysis,  and more.\nThis story was written by: @gudevamsikrishna. Learn more about this writer by checking @gudevamsikrishna's about page,\n            and for more stories, please visit hackernoon.com.\nWe investigated intermittent Kong 503 responses where the logs showed only the status code and an empty upstream address. Worker-level metrics and dmesg eventually showed that a cgroup OOM event had killed one of the two NGINX workers in the Kong pod.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}