269 posts categorized "Application Performance" Feed

Which is Better for Troubleshooting SaaS Performance Issues: Packet or Number Crunching? (by Will Moonen)

  • Which is Better for Troubleshooting SaaS Performance Issues: Packet or Number Crunching?

 Most enterprise IT professionals and network performance management (NPM) tool vendors consider it mandatory to have the original packets for analysis when solving difficult network and application degradation issues. That’s because visibility into network, TCP transport, and application performance is essential, especially when web, SaaS applications, and hybrid cloud infrastructure are involved.

While there are certainly cases where you need the original packets,  there may be cases where sifting through large volumes of packets would impair rapid problem isolation and resolution time.

That is why it is our contention, and based on real customer scenarios, that insights offered by automated “number crunching” wire-data analytics trumps terabytes of stored packets.

Let’s examine further. Figure 1: FastestMTTR-01
Achieving fast MTTR in complex IT environments: Number vs. packet crunching?

 Handling slow cloud applications - 

Here’s a situation we encountered at one client that had a large number of branch offices.  Users at many branch offices reported slow application performance, mostly around three cloud applications.  From initial analysis, we discovered that the performance degradations occurred between 7 and 11 AM  and every three to five working days.

 

Continue reading "Which is Better for Troubleshooting SaaS Performance Issues: Packet or Number Crunching? (by Will Moonen)" »


LMTV LIVE | Guarantee Application Performance with Network Emulation (with Joe Zeto)

EVENT START TIME: 9:30 AM - Wednesday, June 20th, 2018

This week we will be talking with Joe Zeto, VP of Product Management from Apposite Technologies, about the importance of network emulation in guaranteeing application performance.

We all know that networks are imperfect—so the question is how will a specific application perform in the real world over various network types with varying degrees network of quality? Or how do you get the most realistic understanding of your app’s quality in a geographically distributed environment?

We’ll touch upon a spectrum of different landscapes, cloud object storage, cloud migration, video streaming services, devops, the internet of things, and even satellite communications.

Some key thoughts we will discuss during the event:

  • How network performance impacts application quality
  • Why it’s critical to evaluate performance in development, QA, and system test before going live
  • Easy steps you can take to bring the wide area network to your local lab

Troubleshooting a Cloud Problem with Wireshark (by Paul Offord)

The slowly growing interest in Cloud Computing that started ten or so years ago is turning into a stampede.  Most of our customers at Advance7 have strategic plans to migrate many systems to a cloud platform, and many have already started the journey.

Cloud application topology

In fact, we too have migrated all of our systems into AWS and Azure, containerising many of them in the process. But here's a concern we shared with our customers:

"Will we have enough visibility to troubleshoot performance and stability problems once we have migrated our systems?"

It's a good question.  We don't want to discover that the whole environment is opaque, just when we need to troubleshoot a serious problem.  We satisfied ourselves that we could get the data we needed to maintain our systems.  We found that we could get a lot of information from the Application Load Balancers, and we configured continuous packet captures to record traffic between the tiers of our systems.  Just as well as a couple of months ago we hit a performance problem with the TribeLab Community website.

I managed to record the actions of our Performance & Stability Engineers as they used AWS CloudWatch and Wireshark to investigate the problem.  I pulled together screenshots, video clips and other information to produce a short video case study …

Continue reading "Troubleshooting a Cloud Problem with Wireshark (by Paul Offord)" »


LMTV LIVE | How To Diffuse The IT Blame Game (with Keith Bromley and Scott Peerbolte)

 

 

LIVE EVENT START TIME : 9:30 AM PST, Wednesday, June 27th, 2018

6a00e008d95770883401b8d2e041f0970c-800wiThis week we will be talking with Keith Bromley (from Keysight Technologies, formerly Ixia) and Scott Peerbolte (of Corvil) about how you can help break down silos and reduce the blame game that are common for most IT departments. 

For instance, how well do your IT departments communicate with each other?  

Enterprises typically contain four or more IT sub-departments (Security, Network Operations, Virtual DC, Capacity Planning, Service Desk, Compliance, etc.) and it’s quite common for them to be at odds with each other, even in good times. For instance, there’s often contention over capital budgets, sharing resources, and headcount. But let’s be generous. Let’s say that in normal operations things are usually good between departments. What happens if there’s a breach though, even a minor one? Then things can change quickly. Especially if there are problems with acquiring accurate monitoring data for security and troubleshooting areas. Finger pointing can quickly result. 

So, what can you do? One answer is to create complete network visibility (at a moment’s notice) for network security and network monitoring/troubleshooting activities. Join us on this podcast to learn how.

Some key thoughts we will discuss during the event:

 

Continue reading "LMTV LIVE | How To Diffuse The IT Blame Game (with Keith Bromley and Scott Peerbolte)" »


LMTV LIVE | Resilience Within A Security Architecture (with Keith Bromley and Steve McGregory)

LIVE EVENT START TIME : Wednesday, May 30, 2018 - 9:30 AM PST

NetworkVis_Ad_TroubleshootIT_170x200Keith Bromley and Steve McGregory from Keysight Technologies (formerly Ixia) will be talking about a security architecture concept called Network Security Resilience. While this concept is not new, it has received as much attention as typical defensive strategies have. This may change with the new NIST Framework for Improving Critical Infrastructure Cybersecurity that places more effort on breach recovery and mitigation.

Basically, it’s not a question of IF your network will be breached, but WHEN. News broadcasts for the last several years have shown that most enterprise networks will be hacked at some point. In addition, the time it takes for most IT departments to notice the intrusion usually takes months—over six months according to the Ponemon Institute. This gives hackers plenty of time to find what they want and exfiltrate whatever information they want. What if you could reduce that time to 1 month, i.e. cut it to 1/6 of the time? Or maybe reduce it further to one week, or maybe to just one day? What if you could go further? Would that be of interest to you? 

Continue reading "LMTV LIVE | Resilience Within A Security Architecture (with Keith Bromley and Steve McGregory)" »