{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Centralized Logging for AWS ECS in New Relic using FluentBit","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/b9604f89\"></iframe>","width":"100%","height":180,"duration":378,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/centralized-logging-for-aws-ecs-in-new-relic-using-fluentbit.\nIn this article, I share my experience setting up logging for our project. The main focus will be on configuring Fluent Bit, which we used for log forwarding.\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #logging, #fluent-bit, #aws, #aws-ecs, #new-relic, #aws-guide, #ecs-services, #aws-secrets-manager,  and more.\nThis story was written by: @kirillshershen. Learn more about this writer by checking @kirillshershen's about page,\n            and for more stories, please visit hackernoon.com.\nIn this article, I share my experience setting up logging for our project. We transitioned from using ELK to New Relic for log storage. I'll explain how we chose our log delivery method, the options we considered, and why we settled on our current solution. The main focus will be on configuring Fluent Bit, which we used for log forwarding.","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}