Welcome!

Microservices Expo Authors: Elizabeth White, Pat Romanski, Liz McMillan, Stefana Muller, Karthick Viswanathan

Related Topics: @CloudExpo, Microservices Expo, Containers Expo Blog, Agile Computing, @DXWorldExpo, SDN Journal

@CloudExpo: Article

Twitter Is Not a SaaS Monitoring Solution

The crowd can help IT, but only if the right information is shared

A few weeks ago I was trying to update some files I have stored on a cloud storage service (that will remain nameless). I had moved my files there a while back as a way to make it easier to access them from my various devices and to avoid losing them during the next inevitable hard drive failure. For the most part I've been happy with the service, but on this day, I was unable to access the site.

Not good, as I was rushing to make some changes and send the files to a colleague.

Frustrated by my situation, I asked a co-worker to see if he was also having problems. He was, so we did the next logical thing you would expect. We went to the service provider's status page to see what they had to say. According to it, the service was healthy and there were no current service or maintenance notices.

#nowwhat?
Twitter! Of course. Whenever services like YouTube or Hulu have outages, users light-up Twitter with comments and laments. Sure enough, a quick Twitter search showed that, yes, there was a widespread problem that had started only a few minutes prior, and already there was a trending hashtag.

This example shows what's great about Twitter. It is an immensely powerful platform for creating instant virtual communities sharing information and opinion around a topic of common interest. The Twitter community as a group was able to do a better job than the service provider itself of informing users that there was a problem with the service.  I and the other storage service users -- at least the ones also on Twitter -- had formed an impromptu global network of monitors, watching the service from hundreds of thousands of access points. Together could confirm for each other that there was a service-wide outage.

#problemsolved?
Well, not really. Yes, I could see a number of people on Twitter reporting that they couldn't access the service, but this was all anecdotal information (along with a fair amount of opinion). I had no idea who these other users were or where they were located. For all I knew we might all be customers of the same internet service provider and maybe the problem was there and not with the storage service itself. In addition, while I could go to Twitter to confirm that I wasn't the only one experiencing an outage -- even as the service provider's status dashboard said everything was okay -- I was still searching for evidence after the fact. There was no practical way for me to be notified proactively, nor was I able to reliably see service performance degrading prior to the outage.

Herein lies the problem for manufacturers, or any organization, looking to leverage SaaS applications -- particularly mission critical email, collaboration, and document storage -- as part of their IT infrastructure. While it may be okay for me to use Twitter to monitor Hulu, you obviously can't operate a business this way. Organizations need the same level of visibility and troubleshooting capability for SaaS apps that they've come to rely on for traditional on-premise applications. This includes:

  • Proactive issue detection and alerting
  • Quantitative data on application performance
  • Ability to accurately measure service level attainment v. target goals
  • Ability to identify problem sources so the time to isolate and fix is minimized

That last one is particularly tricky for SaaS since most of the datacenter and network infrastructure is outside organizations' IT perimeters. You can't directly see or touch the server or network equipment and neither can your traditional monitoring and management tools. It's not surprising, then, that we often hear from IT admins that they have had to resort to using Twitter because otherwise they are flying completely blind. It's not enough, but at least it's something.

#saasvisibility
Despite its shortcomings, there is a lot to be said for the "power of the crowd" that is so fundamental to Twitter. What if we could take that same model and use it to proactively monitor our SaaS applications?  First, it would require some type of active monitoring behind your firewall at the locations where users access their SaaS applications. These "sensors" could act like Twitter users, constantly running transactions against the service and collecting data on transaction and network node performance. They would also allow you to proactively detect and notify an IT Admin of any outages or performance anomalies BEFORE they impact your users.

Then, what if we could collect and share real-time performance data from those sensors (yours as well as other users' sensors) into a global database maintained as part of your cloud service. You'd then be able to access this data to gain visibility into the health of the complete service delivery chain between you and the SaaS provider. For example, you could:

  • View current status, alerts, network statistics, and performance trends for one or more of your own sensors to determine if you have service issues affecting a particular location or subnet, so you can point and fix faults in your own infrastructure and get users back online quickly
  • Analyze your sensor data with the rest of the crowd to determine whether service issues are systemic to the application provider or the result of downstream internet service provider problems; you may not be able to fix these directly, but with this information you would know which service provider to call and could provide them with details to speed their time to resolution
  • Confirm exactly what service levels you are getting from your application service providers, with detailed outage data needed both for internal reporting and for provider service level guaranty refund requests

The goal of every IT shop is to keep their application users online and happy. But with SaaS, that's more difficult to do because administrators do not have the same visibility that they do with on-premise applications. We, as a community, need to come up with ways to change that. Taking a cue from Twitter, and leveraging the crowd - seems like a great place to start.

More Stories By Patrick Carey

Patrick Carey is vice president of product management and marketing for Exoprise, a provider of cloud-based monitoring and enablement solutions for Software-as-a-Service (SaaS) applications. He spends his free time thinking about how companies can get to the cloud faster and stay there longer.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Microservices Articles
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...
The now mainstream platform changes stemming from the first Internet boom brought many changes but didn’t really change the basic relationship between servers and the applications running on them. In fact, that was sort of the point. In his session at 18th Cloud Expo, Gordon Haff, senior cloud strategy marketing and evangelism manager at Red Hat, will discuss how today’s workloads require a new model and a new platform for development and execution. The platform must handle a wide range of rec...
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound e...
If your cloud deployment is on AWS with predictable workloads, Reserved Instances (RIs) can provide your business substantial savings compared to pay-as-you-go, on-demand services alone. Continuous monitoring of cloud usage and active management of Elastic Compute Cloud (EC2), Relational Database Service (RDS) and ElastiCache through RIs will optimize performance. Learn how you can purchase and apply the right Reserved Instances for optimum utilization and increased ROI.
TCP (Transmission Control Protocol) is a common and reliable transmission protocol on the Internet. TCP was introduced in the 70s by Stanford University for US Defense to establish connectivity between distributed systems to maintain a backup of defense information. At the time, TCP was introduced to communicate amongst a selected set of devices for a smaller dataset over shorter distances. As the Internet evolved, however, the number of applications and users, and the types of data accessed and...
Consumer-driven contracts are an essential part of a mature microservice testing portfolio enabling independent service deployments. In this presentation we'll provide an overview of the tools, patterns and pain points we've seen when implementing contract testing in large development organizations.
In his session at 19th Cloud Expo, Claude Remillard, Principal Program Manager in Developer Division at Microsoft, contrasted how his team used config as code and immutable patterns for continuous delivery of microservices and apps to the cloud. He showed how the immutable patterns helps developers do away with most of the complexity of config as code-enabling scenarios such as rollback, zero downtime upgrades with far greater simplicity. He also demoed building immutable pipelines in the cloud ...
You have great SaaS business app ideas. You want to turn your idea quickly into a functional and engaging proof of concept. You need to be able to modify it to meet customers' needs, and you need to deliver a complete and secure SaaS application. How could you achieve all the above and yet avoid unforeseen IT requirements that add unnecessary cost and complexity? You also want your app to be responsive in any device at any time. In his session at 19th Cloud Expo, Mark Allen, General Manager of...