LogDNA Browser Logger allows developers to debug web applications more efficiently

LogDNA has launched a new browser logging feature, which makes it easier for full-stack and frontend developers to ingest frontend log data into LogDNA to debug web applications more efficiently.

Code running on end-user devices has become increasingly complex, increasing the need for front-end logging capabilities. While there are a host of observability tools and services for logging backend and server applications, there is a noticeable gap in visibility for client-side applications.

LogDNA’s new Browser Logger addresses this need by automatically capturing errors and logs occurring in the user’s browser and allowing development teams to centralize these errors with server-side logs.

Full-stack and frontend developers get valuable browser log data that can be used to effectively debug client-side errors.

“Customers find it difficult to extend their observability stack in their front-end web applications to monitor client-side errors and collect critical debugging information. This makes it difficult to identify when problems occur, and troubleshoot errors. become difficult and time-consuming,” said Peter Cho, vice president of product, LogDNA.

“LogDNA Browser Logger makes it quick and easy to find and resolve issues that span between frontend and backend applications so developers can spend less time debugging and more time on value-added tasks.”

With this new data, developers can see errors with stack traces and correlate those errors with a specific application version or browser version.

They can also record real-time performance metrics to find out how long a specific user interface (UI) feature is taking on a customer’s device. As a result, developers are empowered to take immediate action to improve the performance of their web applications to deliver the best possible user experiences.

Combined with the long list of ingest sources supported by LogDNA, this feature gives developers the information they need to better understand what is happening at every layer of their applications.

For example, Kubernetes stores can use Browser Logger to see front-end metrics, and the Kubernetes enrichment feature to see Kubernetes events and metrics.

Having visibility from the front-end application layer down to the container orchestration layer is critical for teams working with a DevOps mindset where the same group is in charge of building, deploying, and maintaining apps.

With a higher level of granularity in event tracking and a lower cost per event compared to alternatives, LogDNA’s Browser Logger allows developers to take immediate action to improve the performance of their web applications to deliver the best possible user experiences.