Por el momento, esta página sólo está disponible en inglés.

From cars to computers, boats to blazers or all of the above, letgo makes selling second-hand goods quick and simple with its mobile app. With over 100 million downloads and hundreds of millions of listings, letgo makes it easy for users to buy and sell locally. As letgo scales, the increase in app traffic means that solving errors quickly becomes an important priority. Not only does it deliver an exceptional customer experience and reduce the economic impact of downtime, but faster error resolution keeps developers focused on building innovative new features.

Prior to using New Relic logs, letgo leveraged an ELK Stack. The product team found that using multiple logging tools became difficult to manage due to realities inherent in tool sprawl like screen hopping and lack of shared context. This created several challenges when it came to identifying and resolving errors in part because their logging data, like their stack, was distributed.

The product team eventually migrated from EC2 to Kubernetes and, in the process, decided to standardize on an observability strategy that leveraged New Relic One. With New Relic One, letgo was able to streamline its error resolution process. Product teams went from bouncing between three to four Kibana screens to view their logs, undergoing multiple iterations, and needing hours to reconcile between multiple data sources to navigating quickly from a high-level view of their Kubernetes clusters down to a specific transaction within a single app. The result? Faster, simpler troubleshooting in just a few clicks.

To learn more about how letgo engineers use New Relic One to focus on developing and scaling their software instead of managing external systems, check out our fireside chat with Marcelo Bartsch, a Senior DevOps Engineer at letgo.