Many companies in Asia Pacific (APAC) were caught in a digital tailspin when Covid-19 hit, sacrificing security practices in their hurry to adjust to the new reality of remote work. Two years on, hybrid work is still the norm as the pandemic continues and seems to be a new way of life moving forward. Catalyzed by the coronavirus, firms big and small are now adopting cloud technologies as we tread deeper into a new data age.
As product developers, our responsibility continues beyond shipping code. To keep our software running, we need to notice whether it’s working in production. To make our product smoother and more reliable, we need to understand how it’s working in production. We can do this by making the software tell us what we need to know. How can we notice when the software is running smoothly? Make it tell us!
Manual incident management is an enormous challenge facing today’s enterprises. It wastes time and money, and often results in unhappy customers who have to deal with unreliable services because of persistent, unresolved issues. Manual ticket generation can take 20 to 30 minutes, and routing another 90—assuming the ticket is delivered to the right team.
Keeping an eye on metrics is one of the essential things that every developer should do for their applications. Prometheus is a tool that has gained a lot of popularity in the field of metrics. When you start with Prometheus, you may not recognize its potential at first because it takes time to explore the entire tool. But once you become acquainted with the features, you will find it highly useful.
Our front-end JavaScript library has been updated with an easier way to add more metadata to front-end errors using the sendError and wrap helpers. Previously, sendError and wrap helpers only supported customizing tags and the namespace for the error. More information could be set on error spans if they were manually created, but now that type of information can be added to errors sent using these helpers.
For organizations that rely on their network to support their daily operations, how well the network operates can make or break their business. As a network admin, your core objective is to ensure that day-to-day business operations are carried out successfully. This involves optimizing the network for maximum performance and minimizing service disruptions.
As LogDNA has grown, many of our customers have too, meaning that they are bringing in more ingestion data sources and expanding their use cases for their logs. To help with managing more data, we’re excited to introduce the Control API suite. We’ve built 4 individual APIs that will help companies programmatically configure their data and how they want to ingest logs. Below, we’ll cover each new API in detail as well as why they are massively impactful for our customers.
It’s easy for us to cruise the net, not really thinking of anything other than exactly what we’re hoping to achieve whether it’s making a payment via online banking or buying a new laptop on Black Friday. But we forget that there’s a whole system working in the background of each and every website, keeping it online and making sure it works to the best of its ability.
