APMdigest asked experts from across the IT industry for their opinions on what IT departments should be monitoring to ensure digital performance. Part 3 covers the development side.
Code-level issues are a common cause of application slowness and have fueled the need for distributed transaction tracing, which can help isolate the exact line of code with errors. This type of monitoring can also be effectively applied in both pre- and post-production environments, enabling us to prevent performance issues before they impact end users as well as help isolate them when they do occur.
When this type of application monitoring is done in context of infrastructure dependencies, it helps distinguish if there are other issues affecting application code processing, such as a bottleneck in the application server, long-running database queries, slow third-party calls, or other issues that may be associated with the application ecosystem. Applications are the heart of IT workloads, and application performance monitoring is critical to effectively ensure the performance of digital services.
Director, Product Marketing, eG Innovations
Digital performance is complex and can be measured in many ways, but one critical consideration is how well does the application do what it is supposed to do? Is it meeting a functional performance metric for customer expectations? To ensure this, organizations need to look at the "fingerprint" of each error in code to discern its importance as well as look at the number of critical errors per release. This dictates the overall functional reliability of the code. It also requires you to be code-aware, monitoring from inside the application at runtime, not surrounding it or listening to the exhaust.
CTO and Co-Founder, OverOps
Most people already know to monitor the obvious things, like total latency to response. But my favorite monitor comes from Anatoly Mikhaylov's talk at DASH this year. He spoke about finding massive infrastructure costs hidden in error codes. Adding APM monitoring to the errors in your endpoints can show costs you wouldn't otherwise see.
APM Developer Advocate, Datadog
When automating you application release, it's important to remember what you need to monitor. This will allow you to go as fast as possible, but also make sure you are doing it efficiently. Monitor your lead time, success vs failure rate and mean time to recovery will ensure you focus on value rather than on effort.
Co-Founder and CTO, DBmaestro
One key area to make sure you monitor: API calls. There aren't many applications I come across these days that do not include some 3rd-party API, be it for authentication, analytics, storage, or customer relationship management. Such API calls can so greatly impact digital performance that not monitoring them to identify things such as performance slowdowns and dependencies is a prescription for pain.
Senior Consultant and Founder of RootPerformance
Cloud, containers and microservices are creating increasingly ephemeral, modular and volatile IT environments. In these dynamic environments, traditional monitoring approaches fail. A modern monitoring approach is required to provide complete visibility into the applications, containers, host and underlying supporting infrastructure. This includes having visibility into the performance of and data returning from APIs which have become a key component to any microservices architecture. A modern monitoring approach includes the analytics and intelligence to understand how changes might impact the overall user experience and flexible monitoring techniques that don't overload the containerized application environment.
Director, Product Marketing, CA Technologies
Finding a tool that fits seamlessly into your workflows, setting performance benchmarks, validating payloads, and getting visibility into the performance of API transactions is critical to help teams get rapidly identify and fix issues in production so that the delivered digital experience matches the vision for end-users.
VP of Product, AlertSite UXM, SmartBear
APIs are the fundamental building block of modern software. While engineering teams have built extensive monitoring systems to check the health of code execution paths, they have little visibility into what's going on with APIs. An API failure can bring down systems and without proper monitoring in place, it can be very hard to debug what's going on.
The nature of development means systems are going to spring into existence and then back out again often, and that this rapid change is OK, which means your monitoring needs to be OK with it. The ability to monitor containers, ephemeral services, and the like, is a must.
Head Geek, SolarWinds
Let's go to the extreme and say you could only monitor one thing — that one thing would be microservice response time. In this brave new world, it's actually quite difficult to understand how well your revenue-critical application is performing. While traditional metrics still matter (CPU, memory, disk, etc), your response time on a microservice-by-microservice basis is the thing that matters the most. This single metric will tell you more about the customer experience than anything else. It will indicate downtime or more subtle performance problems in your application. While this metric alone will not tell you "why" something is going on, it will tell you "what" is happening and allow you to quickly isolate a problem to a handful of services or some set of underlying infrastructure.
As you evolve and enhance your company's hybrid data center infrastructure to keep pace with your industry, understanding your unique workload I/O DNA is paramount to success. Real-time monitoring of the I/O path – from the virtual server to the storage array – is essential to ensuring digital performance. For mission-critical applications, understanding the performance of each and every transaction is the cornerstone of customer satisfaction and revenue assurance.
CMO, Virtual Instruments
Read Len Rosenthal's new blog on APMdigest: Infrastructure Monitoring for Digital Performance Assurance.
Read What You Should Be Monitoring to Ensure Digital Performance - Part 4, covering the infrastructure, including the cloud and the network.
As enterprises work to implement or improve their observability practices, tool sprawl is a very real phenomenon ... Tool sprawl can and does happen all across the organization. In this post, though, we'll focus specifically on how and why observability efforts often result in tool sprawl, some of the possible negative consequences of that sprawl, and we'll offer some advice on how to reduce or even avoid sprawl ...
As companies generate more data across their network footprints, they need network observability tools to help find meaning in that data for better decision-making and problem solving. It seems many companies believe that adding more tools leads to better and faster insights ... And yet, observability tools aren't meeting many companies' needs. In fact, adding more tools introduces new challenges ...
Driven by the need to create scalable, faster, and more agile systems, businesses are adopting cloud native approaches. But cloud native environments also come with an explosion of data and complexity that makes it harder for businesses to detect and remediate issues before everything comes to a screeching halt. Observability, if done right, can make it easier to mitigate these challenges and remediate incidents before they become major customer-impacting problems ...
The spiraling cost of energy is forcing public cloud providers to raise their prices significantly. A recent report by Canalys predicted that public cloud prices will jump by around 20% in the US and more than 30% in Europe in 2023. These steep price increases will test the conventional wisdom that moving to the cloud is a cheap computing alternative ...
Despite strong interest over the past decade, the actual investment in DX has been recent. While 100% of enterprises are now engaged with DX in some way, most (77%) have begun their DX journey within the past two years. And most are early stage, with a fourth (24%) at the discussion stage and half (49%) currently transforming. Only 27% say they have finished their DX efforts ...
While most thought that distraction and motivation would be the main contributors to low productivity in a work-from-home environment, many organizations discovered that it was gaps in their IT systems that created some of the most significant challenges ...
APMdigest and leading IT research firm Enterprise Management Associates (EMA) are teaming up on the EMA-APMdigest Podcast, a new podcast focused on the latest technologies impacting IT Operations. In Episode 1, Dan Twing, President and COO of EMA, discusses Observability and Automation with Will Schoeppner, Research Director covering Application Performance Management and Business Intelligence at EMA ...
APMdigest is following up our list of 2023 Application Performance Management Predictions with predictions from industry experts about how the cloud will evolve in 2023 ...
As demand for digital services increases and distributed systems become more complex, organizations must collect and process a growing amount of observability data (logs, metrics, and traces). Site reliability engineers (SREs), developers, and security engineers use observability data to learn how their applications and environments are performing so they can successfully respond to issues and mitigate risk ...