<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1678611822423757&amp;ev=PageView&amp;noscript=1">
Defrag This

| Read. Reflect. Reboot.

How Application Performance Monitoring Keeps the Cloud on Track

Ipswitch Blog| December 16 2015

| monitoring

Application monitoring can help troubleshoot bandwidth bandits and other disruptions (credit: Jerry John | Flickr)

Cloud computing is a ready-made revolution for SMBs. Forget about server downtime; elastic computing and API-driven development is perfect for smaller organizations with project funding in the mere thousands of dollars.

All that agility is allowing information architects to think big — smartphone connectivity, IoT, lambda architecture — with existing app performance monitoring standards becoming more Web and socially aware.

Perfect world, right? Well, maybe a "perfectable" world. While developers are doing the elastic, agile thing — leveraging the power of pre-built tools through IFTTT or Zapier and getting Big Data tools from GitHub — they're making assumptions about available bandwidth. They may even add Twilio to the mix so the company can SMS you in the middle of the night when their app hangs.

App Performance: 'It's Spinning and Spinning'

"I can't do anything. It's just keeps spinning," you're thinking. Classic Ajax loader. Users from a different era prefer freezing metaphors, but those are just as obvious, and don't encompass today's issues: "My email won't send," "My daily sales dashboard won't load" and, now, "the whole neighborhood's smart meters are offline."

A new set of network demands are rounding the corner, foreshadowing a greater need for application performance monitoring: SIEM, Big Data, IoT, compliance and consumer privacy audits. It is the slow death of offline archiving. And for each, file sizes are on the rise and apps are increasingly server-enabled — often with heavy WAN demands.

Open Source, DIY and Buy-a-Bigger-Toolbox

Presented with bandwidth concerns, some support specialists (or DIY-minded developers, as that is often the SMB way) will turn to open-source tools like Cacti to see what they can learn. And they may learn a lot, but often the problem lies deeper inside an app's environment. As one support specialist explained (known as "crankysysadmin" on Reddit), "It isn't that easy. There are so many factors that affect performance. It gets even more tricky in a virtualized environment with shared storage and multiple operating systems and complex networking."

Another admin in the Reddit thread agreed: In terms of app performance monitoring, he responded, "there's no one-size-fits-all answer. What type of application are we talking? Database? SAP? Exchange? XenApp? Is it a specific workflow that is 'slow'? What do you consider 'fast' for that same workflow?"

Event-Driven Heads-Up for App Hangs and Headaches

App usage spikes have many possible causes, which is precisely why a commercial app monitoring tool that is easy to use when you need it in a pinch can ultimately pay for itself. Depending on site-dependent update policies, types of applications support, regulatory environment, SLAs and cloud vendor resources, you'll sooner or later be faced with:

  • Massive updates pushed or pulled unexpectedly.
  • Surprise bandwidth-sucking desktop apps.
  • Developer runaway apps.
  • App developer design patterns tilted toward real-time event processing.
  • Movement toward the more elastic management of in-house resources.
  • Management of bandwidth usage by cloud service providers.
  • A need to integrate configuration management with monitoring.
  • Increased support of operational intelligence, allowing for real-time event monitoring as described by Information Age.
  • Monitoring to develop application-dependent situation awareness.

The last of these, situation awareness, deserves an emphasis. Consider the impact of moving monthly reports to hourly, or a BI dashboard suddenly rolled out to distributor-reps. Situational awareness at the app level can ward off resource spikes and sags or even server downtime.

Identify What's Mission-Critical

Whether the monitoring answer is open source or commercial depends partly on whether your apps are considered mission-critical. For some, VoIP and Exchange have been those applications. The SLA expectation for telephony, for example, is driven by the high reliability for legacy on-premises phone systems that rarely failed. SLAs for VoIP are often held to the same standard.

And what's mission-critical is probably critical for job security. If the CEO relies on a deck hosted in Sharepoint for briefing at a major conference, and he can't connect at the right moment — well, you may wish you had a bigger IT staff to hide behind.

Related articles:

Are Your Mission-Critical Applications Starving for Bandwidth?

Noble Truth #5: Network and Application Performance Defines Your Reputation

[cf]skyword_tracking_tag[/cf]

Topics: monitoring

Leave a Reply

Your email address will not be published. Required fields are marked *

THIS POST WAS WRITTEN BY Ipswitch Blog

Free Trials

Getting started has never been easier. Download a trial today.

Download Free Trials

Contact Us

Let us know how we can help you. Focus on what matters. 

Send us a note

Subscribe to our Blog

Let’s stay in touch! Register to receive our blog updates.