At New Relic, we love learning about new patterns and technologies. We also think it is important to give back by sharing our own best practices and patterns. Therefore we are rolling out a new blog series called “Expert Observability” where we will be sharing our observability best practices. We are passionate experts about the observability space and believe that observability should be incorporated into all stages of the development lifecycle. In fact, we collect over 1 million log payloads, 1 million event payloads, and 400k metric payloads of our own monitoring each minute.
The goal of this publication is to help engineers around the world leverage observability to improve their business. We have seen that the correct monitoring and alerts can not only help reduce incident duration but it can also be used to drive and improve business outcomes. We have witnessed Service Level Indicators (SLIs) prevent incidents and reduce on-call pager load. We have tuned monitoring to drive auto-scaling and other fail-over mechanisms. We look forward to sharing these best practices and more with you.
We will be publishing one blog in the series each month which will be written by a New Relic engineer. These engineers are observability experts, using monitoring data daily in unique ways to solve problems. I encourage you to read the monthly series and bring the same best practices back to your own company.
이 블로그에 표현된 견해는 저자의 견해이며 반드시 New Relic의 견해를 반영하는 것은 아닙니다. 저자가 제공하는 모든 솔루션은 환경에 따라 다르며 New Relic에서 제공하는 상용 솔루션이나 지원의 일부가 아닙니다. 이 블로그 게시물과 관련된 질문 및 지원이 필요한 경우 Explorers Hub(discuss.newrelic.com)에서만 참여하십시오. 이 블로그에는 타사 사이트의 콘텐츠에 대한 링크가 포함될 수 있습니다. 이러한 링크를 제공함으로써 New Relic은 해당 사이트에서 사용할 수 있는 정보, 보기 또는 제품을 채택, 보증, 승인 또는 보증하지 않습니다.