Welcome!

Microservices Expo Authors: Elizabeth White, Pat Romanski, Dalibor Siroky, Scott Davis, Stackify Blog

Related Topics: Microservices Expo, Java IoT, Microsoft Cloud, Machine Learning

Microservices Expo: Article

Establishing Enterprise Monitoring Baselines

Our technology dependent lives

Enterprise monitoring gets a great deal more air time these days than it ever did in the past. Perhaps it's because our technology dependent lives have become some so reliant on the availability of systems and infrastructural services. Have things improved? How would you know?

In reality, monitoring systems themselves are nothing particularly new. Consider the pressure valve on a steam boiler. At the most rudimentary level, the object of the valve is to release pressure. The way you decide whether or not to release pressure is to observe the gauge that indicates the boiler's pressure. Steam engines have been around for hundreds of years and gauges to monitor them, probably almost as long. The thermostat on your house heating system, the temperature gauge on your car's engine, the battery life monitor on your phone; they're all monitors, perhaps not "enterprisey" but you get the idea.

Most of us, no doubt will have seen one or more of the many Hollywood blockbuster movies that features some drama that involves gauges and monitors. Of course the recent unfortunate circumstances at the Fukushima Daiichi nuclear disaster were of particular importance globally because of the seriousness of the events and the fact that as the disaster unfolded the news was relayed across international networks following the Tsunami. More important here, is the need to consider that if there was not some sort of monitoring it would have been impossible to comment on the significance of the reactor temperatures and other factors until the fires and explosions had already occurred. The process of testing air quality, water and milk quality and the general radioactivity characteristics of the community all represented some level of monitoring also. But effective monitoring was only really measurable against some sort of yardstick - a baseline.

So I think we therefore can accept that monitoring is a worldwide ubiquitous phenomenon and one that not only mankind has embraced but also the plants and trees. Autumn and spring after-all are a factor of the length of the days and plants and trees react accordingly by shedding old foliage or generating shoots and foliage anew. So nature it seems perhaps has a baseline too.

Why bother with a baseline?
To be effective any monitoring activity however needs a base-line. Determining baselines is key to effective monitoring. In its most basic form, a performance baseline is quite simply a set of metrics used for the monitoring to define the normal working state of whatever it is that you are monitoring. Engineers typically use performance baselines for comparison to trap changes in state that could indicate a problem.

Setting an appropriate baseline also provides early indicators that usage or consumption or even throughput demands are pushing available capacity, thereby giving support and planning resources the opportunity to plan for upgrades. Aligning performance baselines with existing SLAs (Service Level Agreements) can help the organization stay within capacity parameters and identify problem areas that are falling out of compliance.

The challenge is in determining what constitutes a relevant and appropriate baseline. As you can image, for many things, there is no absolute answer with respect to baselines. Even mother nature sometimes gets it wrong, when trees start sprouting leaves at about the right time in the season and then an unexpected cold snap occurs and nips those shoots in the bud with a frost and effectively stunts or stalls plant growth for the season.

Establishing a baseline is key though for effective implementation of anything new. If for example, your plan is to replace your organization's paper forms processing technology with an electronic forms solution with workflow, based on a technology like that provided by Winshuttle, you need to understand some basic metrics about what you are trying to do and what your expectations should be around general performance and operational function.

There are no standard baselines
There are no generalized standards for baseline monitoring that you can unfortunately simply overlay on your organization. Just as every custom built boiler has its own baseline and every range of boilers differs from every other range, every automotive engine has a different optimal performance baseline, so too, every organization has its own baseline that is unique.

There are industry standards that can help, like CoBIT, ITIL etc, and some of these make monitoring tool recommendation also, but a lot of these constitute heavy lifting in terms of highly integration solutions and infrastructure that a given organization needs to have in place.

A different but effective approach that should be considered is one that involves determining your minimum expectations in terms of effectiveness. We will have no more than two orders waiting to be processed at any point in time, we will have no more than three process exceptions per 100 orders, we will not have order lines canceled due to lack of product availability etc.

The choice to build infrastructure that pushes and pulls data from your ERP system, whether it be from Microsoft Excel or an InfoPath form has been made based on the fundamental assumption that the existing approaches will improve by some measure. What are those improvements?

Data processing may improve in quality, speed or process rigor and all of these can be measured. As a part of the capital investment process there is usually the requirement of some sort of justification for the project, and this can be a great starting point for your baseline - this usually indicates some sort of yield or return on investment metrics. Part of your baseline activity is also the assessment of how long the current approaches achieve their objective, or fail.

Taking an inventory of all the things you believe are important is therefore your starting point.

Priority and measurability
The next step is determining a priority for those items, which are the most important ones and which ones can be reasonably measured. Having a baseline that state, "our users will be happier" may seem to be an odd, one, however it is a reasonable one, if reworked and considered as a response to a periodic survey with a measurable success criteria such as: 95% of all new users surveyed agree that they prefer the new form. While this is not necessarily an enterprise monitorable response, it is something that you could build into your process at the close out of the form, and have a window appear that asks whether the form process was easy or hard and whether they would be likely to use it again in the future. Storing every response in a database can then become part of your monitoring metrics.

At the end of many SKYPE VoIP calls for example, a call quality poll is presented to help in assessing the quality of the encoding algorithms and application performance.

The last factor to consider is how long should you baseline for? The answer to this is not very categorical, however it is important to remember that if continuous improvement is your objective a protracted baseline gives you the best data. Usually this is at least something that has a high number of samples with enough diversity that you have outliers that would skew the process if looked at all inclusively. The important thing about the baseline that should be considered though, is that over time, the characteristics and parameters of the baseline are likely to change. The starting baseline for example may move, after the new system or approach has been adopted, and in fact the new approach itself may become the baseline for future enhancements and improvements.

When talking forms design, some thoughts to consider on form and workflow performance are the following:

  • Form generation time: how long does the form take to render on launch - with paper, it's how long does it take you to find the form...
  • Form completion time: how long on average does it take to complete the form - this assumes that the person completing the form has all the information that they need, to hand.
  • Form routing time: how long does it take to close out the process and pass control to the next person in the chain
  • Notification time: how long does it take for the submitter to be informed that their form is en route and how long does it take for the next person in the chain to be notified also - failures or protracted delays here, may speak to a number of factors, but you should define the expectation that you have for these.

Softer metrics like those previously cited, like non-conformance, number of forms rejected due to data quality etc, are a little harder to put system monitors around, but you should try to monitor them anyway. With so many of the form and workflow activities now being stored in openly accessible relational databases like SQLServer there are a great many more ways that the data can be evaluated than ever before.

If you have some interesting baseline variables you'd like to share then please do let me know, I would love to hear about them.

Further Reading:

More Stories By Clinton Jones

Clinton Jones is a Product Manager at Winshuttle. He is experienced in international technology and business process with a focus on integrated business technologies. Clinton also services a technical consultant on technology and quality management as it relates to data and process management and governance. Before coming to Winshuttle, Clinton served as a Technical Quality Manager at SAP. Twitter @winshuttle

@MicroservicesExpo Stories
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
It has never been a better time to be a developer! Thanks to cloud computing, deploying our applications is much easier than it used to be. How we deploy our apps continues to evolve thanks to cloud hosting, Platform-as-a-Service (PaaS), and now Function-as-a-Service. FaaS is the concept of serverless computing via serverless architectures. Software developers can leverage this to deploy an individual "function", action, or piece of business logic. They are expected to start within milliseconds...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
"As we've gone out into the public cloud we've seen that over time we may have lost a few things - we've lost control, we've given up cost to a certain extent, and then security, flexibility," explained Steve Conner, VP of Sales at Cloudistics,in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Cloud4U builds software services that help people build DevOps platforms for cloud-based software and using our platform people can draw a picture of the system, network, software," explained Kihyeon Kim, CEO and Head of R&D at Cloud4U, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
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...