SIOS SANless clusters

SIOS SANless clusters High-availability Machine Learning monitoring

APM Automation – The Missing Ingredient For Application Performance Monitoring Solutions

by Leave a Comment

Application Performance Monitoring Solutions

 

APM Automation – The Missing Ingredient For Application Performance Monitoring Solutions

Companies that move to the cloud to host their applications understand that while they have outsourced the hosting of their applications to third-party cloud vendors such as Amazon Web Services, they still need to monitor and manage those applications themselves, usually with an Application Performance Monitoring solutions or APM. With yesterday’s client-server computing applications, I.T. departments had almost complete control over the servers, the networks, and the end-user computing environments.  But today’s cloud environments are more complex, with many more moving parts often outside of your control.

Some companies have embarked on digital transformations, pushing customer interactions into critical, web-based applications.  It is now more important than ever to quickly respond to any application performance and downtime issues via an APM automation solution.

How To Select An APM Solution

Many companies turn to Application Performance Management solutions such as those from AppDynamics, Datadog, Dynatrace, or New Relic.  An APM solution should identify any performance bottlenecks in your code, and help you fix those issues before your users are impacted.

Good APM solutions will let you know what happened, why, and how to prevent it from happening in the future.  An APM solution will alert you when the application or systems being monitored meets a certain condition (load, response times, etc.).  Once you receive an alert you should be able to identify why the application is not performing properly.  Armed with this information you can provide your development team with very detailed diagnostics that will allow them to address the issue and prevent them from happening in the future.

But how do you select the right Application Performance Monitoring solutions solution?  A quick search on Google for “cloud APM solutions” returns 5,830,000 results!  That can be overwhelming to anyone unfamiliar with the space.  Thankfully another Google search will also provide you with a lot of advice and resources on how to select an APM solution that is right for you.  You should look for third-party, non-vendor advice to help you frame your requirements and develop a short-list of choices that meet those requirements.  Gartner has been watching this category for a while and publishes its APM Magic Quadrant every year.  It is a good resource when it comes to understanding how to evaluate Application Performance Monitoring solutions solutions and give a good overview of the top vendors.

Add APM automated to your remediation requirements list

Here at SIOS Technology Corporation, we are always working with customers who are migrating their applications to the cloud.  They often want to know how to protect their applications from unnecessary downtime and ask us for our advice.  The choice of how to protect their applications is a function of the criticality of those applications (more critical applications often require failover solutions, etc.).  But we also help them understand why their applications might be vulnerable.

It used to be that backup and data protection was a separate function (one that was needed only if the APM solution identified downtime).  But in today’s complex cloud environments we believe that organizations should look for a holistic approach when it comes to monitoring and managing their critical applications.  If a traditional APM solution identifies when something happens and lets you diagnose why it happened, then why doesn’t it prevent unnecessary downtime where possible?

We believe that automation is the missing ingredient from most cloud APM solutions.  Many of our customers tell us how they are being overwhelmed by receiving too many alerts from their APM solutions, each requiring them to stop and understand what happened and why.  They quickly understand what to ignore and what to pay attention to (and good APM solutions help them do this through machine learning).  And if and when their applications go down, the APM solution alerts them to the downtime and diagnoses why to help prevent it from happening again.  But the APM solution won’t reduce their immediate downtime.

That’s where SIOS AppKeeper comes in. AppKeeper monitors a customer’s applications running on Amazon EC2 and automatically restarts the services on EC2 or even reboots EC2 instances if and when downtime is detected.  Our average customer, with only 3 Amazon EC2 instances, experiences downtime at least once a month.  That is downtime when critical, often customer-facing, applications are unavailable, and when I.T. teams are having to drop everything and respond.

AppKeeper’s APM automation solution is letting customers automatically recover from over 85% of their Amazon EC2 downtime situations.  Here’s a link to a quick video if you would like to see AppKeeper in action.

Through AppKeeper’s API customers are programmatically extending the value of their APM solutions by having alerts from their APM solutions trigger AppKeeper to automatically restart effected Amazon EC2 services or reboot instances if necessary.

Application Performance Management solutions

Application Performance Monitoring and Automated Remediation.  Better than peanut butter and jelly?

In many cases, AppKeeper customers have easy to manage Amazon EC2 environments, with perhaps less than 8 Amazon EC2 instances.  For them, the native monitoring and automated remediation functionality of AppKeeper are enough to let them sleep soundly at night, knowing that they are proactively reducing downtime if and when it occurs.

But we recognize that many customers have more sophisticated cloud environments, and have already invested in APM solutions, such as those from New Relic, Datadog, Dynatrace, LogicMonitor, or Zabbix.  They have come to expect immediate alerts and the rich set of data to help them diagnose what happened and why.  For this set of customers, we think the addition of AppKeeper’s automated remediation functionality to their APM toolkit gives them the best of both worlds: control over the performance of their applications, and reduced downtime.

Over the course of the next few months, SIOS Technology will be working with several leading APM vendors to provide packaged and certified integration between their APM solutions and AppKeeper.  Using these integrations with AppKeeper, these users will now enjoy a closed-loop system, where they will be alerted to detected Amazon EC2 downtime and the remediation action that AppKeeper took.

So stay tuned for some exciting news.  Meanwhile, if you would like to try SIOS AppKeeper for yourself, please feel free to sign up for a free 14-day trial of AppKeeper. AppKeeper starts at only US$40 per instance per month.

Reproduced with permission from SIOS

Reducing downtime for WordPress sites hosted on Amazon EC2

by Leave a Comment

 

 

Reducing downtime for WordPress sites hosted on Amazon EC2

Going from ignorance to bliss with SIOS AppKeeper

WordPress is an open-source content management system (CMS) used by millions of companies to create websites, blogs, or apps.  According to estimates, there are over 75 million websites today that use WordPress and many companies are beginning to host their WordPress instances on Amazon EC2. Users love WordPress for its flexibility and the ease with which you can create and modify layouts.  If you are using WordPress for your website, then you are in good company.

With so many users relying on WordPress to power their websites, you can imagine that there is a rich set of third-party tools (plugins and services) designed to meet the needs of those users.  Some of these plugins are to add security functionality, such as scanners to probe for vulnerabilities.  Because more plugins can lead to more vulnerabilities.

Trust, but verify.  Why monitoring WordPress uptime matters.

Deploying a website or application running on WordPress without monitoring it properly would be like leaving your car running outside with the keys in it.  You’ll want to protect your investment.  For companies managing WordPress sites (or any applications, for that matter), there are three primary reasons to monitor:

  1. To understand the visitors and optimize their experience;
  2. To monitor the speed of the site and ensure that it meets expected service level agreements (SLAs); and
  3. To ensure that you maximize uptime.  Downtime can mean (serious) lost revenue for any e-commerce sites running on WordPress.

You believe your WordPress site is working properly, but you really want to know what is going on.  The goal of monitoring should be to know quickly what is going on and why, allowing you to respond quickly to any issues.

There is a wide range of tools available to help WordPress users monitor their sites.  Some are very focused on WordPress, such as ManageWP and JetPack, while others are industry-standard solutions that apply to many different CMSs and applications.  Some go “deep” and are focused on one element of monitoring, such as Google Analytics and its focus on visitor analytics, while others try to go “broad” and address all three key aspects of monitoring.  What you decide to use depends on your budget, your requirements, and your technical capabilities.

Here at SIOS, we believe that the best of breed approach makes sense.  We focus on monitoring applications and ensuring that our customers’ experience as little downtime as possible with those applications.  Many of our customers are using SIOS AppKeeper today to monitor and protect their WordPress sites running on Amazon EC2.

SIOS AppKeeper – simple but powerful monitoring and automated remediation for WordPress sites

Many WordPress monitoring solutions (from free plugins to low-cost freemium services) will tell you when your WordPress site is down.  And depending on the sophistication (and cost) of your monitoring solution, it may tell you why your WordPress site is down.  But will it help you reduce downtime and automatically restart your services or reboot your instances when downtime is experienced?

Many companies host their WordPress sites on Amazon EC2 using either Apache or NGINX webservers.  SIOS AppKeeper is a SaaS service that can be configured to automatically discover WordPress sites or applications running on Amazon EC2 instances and their services, and then automatically take any number of actions if and when downtime is experienced.  So instead of only getting alerts that something is wrong, you get notified that something happened and was automatically addressed.

Downtime matters.  If you are running an e-commerce site using WordPress, then downtime will result in lost revenue.  How much revenue?  Simply divide your annual revenues by 365 days and 24 hours (Annual revenue/365/24) to understand your revenue per hour.  In 2013 Google experienced a 5-minute outage that cost them $545,000 in revenue. Now, you may not be Google, but you certainly do want to eliminate downtime wherever possible.

Now imagine what happens when you receive an alert that your WordPress site is down.  Are you ready to respond immediately?  Do you know what should be addressed to get your WordPress site back up and running?  According to our customer research, the average customer using only three Amazon EC2 instances experiences downtime at least once a month.

SIOS AppKeeper monitors Amazon EC2 and alerts you to any downtime AND takes action to remediate the situation, by either restarting your Amazon EC2 services or rebooting your instances.

AppKeeper addresses over 85% of our customers’ Amazon EC2 downtime issues automatically.  This means that you get notified that a failure was identified and addressed, without you having to drop everything or lose any significant revenue.

Today hundreds of companies rely on AppKeeper to keep their cloud environments running. We invite you to check out the video below see how easy it is to install and use AppKeeper.

Video: Installing AppKeeper and recovering from AWS EC2 failures Demo

And if you like what you see, please feel free to sign up for a free 14-day trial of AppKeeper. AppKeeper starts at only US$40 per instance per month.

Reproduced with permission from SIOS

Migrating to the cloud? Here’s how your DevOps priorities should change when you move to Amazon EC2

by Leave a Comment

 

 

Migrating to the cloud? Here’s how your DevOps priorities should change when you move to Amazon EC2

A majority of companies migrating to the cloud, or creating “cloud-native” applications, are doing so with Amazon Web Services (AWS).  AWS offers a lot of cost and functionality advantages.  Companies who have adopted industry-standard developer operations (“DevOps”) best practices for monitoring and managing their on-premise environments often ask themselves how they adapt to their new cloud environments and applications.

How will DevOps priorities change when you move from on-premise applications to Amazon EC2?  Here’s an explanation of the differences between the two and what you should keep in mind.

DevOps priorities in the cloud?  The same. But different.

We often hear customers say that operations will be easier when they move to AWS. We caution them that moving to the cloud (or even AWS) does not mean that they no longer need to monitor and manage their applications.

Companies moving to Amazon AWS can take advantage of lower costs and manpower resources when it comes to hardware procurement, provisioning, and maintenance.  But you need to take into account that when you decide to host applications on Amazon EC2 that anything above the Operating System layer is your responsibility.

When it comes to backup/availability guarantee/security measures, etc. for your Amazon EC2 environments, the priorities are the same as if they were on-premise applications. And Amazon provides some native tools and functionality.  But you need to decide if they are the right fit for requirements.

Security, Backup… What do you need to know when managing Amazon AWS environments?

So what are some of the AWS-specific considerations you need to keep in mind as you move to Amazon EC2?  And what are the right tools for you?  The time you invest upfront in designing your applications and how you will deploy and manage them will pay off.

Your first consideration should be how you will secure your Amazon EC2 applications.  Network design, such as “which ports to open” and “from where to allow access” must be considered in the same way as for your on-premise applications.  These can be configured in AWS using security groups and network ACLs (access control lists).

You can use the AWS Trusted Advisor functionality*, which automatically examines your AWS environment and points out whether or not it is set to the recommended settings, making it possible to check your company’s AWS environment for security issues.  We recommend checking with the AWS Trusted Advisor both at the time of implementation and periodically.

Another essential aspect of security is the management of authentication and access privileges.  AWS consolidates all of these into AWS Identity and Access Management (AWS IAM).  In addition to controlling who can access which EC2 instances, you can also use AWS IAM to set up access permissions from EC2 instances to other resources (such as DBs), etc.  Once you have migrated to AWS, the first thing you need to do is to set up the accounts and access restrictions properly in AWS IAM.

The next consideration is “how will I backup my applications on Amazon EC2?”  Amazon EC2 provides the ability to take snapshots, which allows you to do so.  In addition, using “Amazon Data Lifecycle Manager” makes it easy to set up periodic snapshots, as well as incremental backups.  Snapshot files are stored on the Amazon S3 storage service.  You are charged according to their capacity, so you need to be aware of the amount of data you have and set up such settings as “reduce the capacity by incremental backups” and “delete from old data.”

“Availability” needs to be considered in advance. The key is to operate the system in accordance with the priority level of the system.

The last consideration is availability.  With Amazon EC2 applications, as well as those that are on-premise, you should consider the level of availability required based on cost and system importance. However, if you use Amazon’s Multi-AZ deployment functionality, you can specify a redundant configuration between different data centers.  However, using Multi-AZ costs more than using a single-AZ configuration (although not as much as if you had redundant on-premise systems).  When designing your applications you need to consider whether Multi-AZ is required and how much you should invest in availability.

If you aren’t investing in failover, then you should at least be monitoring your applications and planning how to recover them when downtime is experienced.  You can use Amazon CloudWatch to easily monitor general items such as CPU, memory, and disks, and you can also program the Amazon EC2 Auto Recovery function to automatically recover instances when an error occurs in the EC2.

If your application is mission-critical, then you will want to invest more in its availability.  You should consider many of the excellent third-party solutions that offer valuable functionality to the AWS community.  One choice is SIOS AppKeeper, an easy to configure and use solution that monitors your Amazon EC2 instances and automatically restarts services or reboots instances if they experience system failures.  Here’s a quick video of how AppKeeper works

While moving to the cloud for your applications makes a lot of sense, you cannot abandon DevOps best practices.  Amazon AWS provides you with a rich set of functionalities and tools, but you still need to take primary responsibility for the security, backup and availability of your applications.  How you do this depends on your skills and the importance of the applications themselves.

We invite you to join the hundreds of customers who have been taking advantage of AppKeeper to reduce their Amazon EC2 downtime by signing up for a free 14-day trial of the service.

* Note:  To use AWS Trusted Advisor, a contract for business support or higher is required.

Reproduced with permission from SIOS

Why is AWS EC2 Application Monitoring So Hard?

by Leave a Comment

Why is AWS EC2 Application Monitoring So Hard?

Why is AWS EC2 Application Monitoring So Hard?

Congratulations! You’ve migrated your core applications to the AWS cloud.  Or, you are developing new “cloud-native” applications and hosting them in the cloud.  Perhaps you are taking advantage of Amazon EC2’s scalability and its elastic architecture.  Either way, you now want to ensure that those applications stay up and running, or that you are alerted quickly if and when something happens.

Because something will happen.  Our customer data shows that companies using only three EC2 instances experience downtime at least once a month.  That means unhappy users unable to access their applications. You need a monitoring solution to tell you what’s going on.

How to narrow down EC2 application monitoring solutions

The first step in your search for the perfect EC2 monitoring solution should be to understand your requirements and your own technical capabilities.  Monitoring solutions are not all alike.

Are you interested in a feature-rich solution that monitors a wide array of systems?  Or one that focuses on a core set of systems, such as your EC2 environment?

What do you want to do with the output from your application monitoring solution?  Do you want as much information as possible to help your developers’ troubleshoot issues?  Or are you looking for quick alerts and assistance in remediating from any failures?

And what is your technical appetite to install and manage another application?  Do you love scripting?  Or do you want something that is “set-it-and-forget-it”?

A search for “application performance monitoring solutions” on Google returns 1,170,000,000 results!  Jump into the Amazon AWS Marketplace and you’ll find 453 products listed in the DevOps – Monitoring category.  Having a clear sense of your requirements and your own technical capabilities will help you narrow down your search.

Monitoring applications running on Amazon EC2 with Amazon CloudWatch or other APM solutions

If you are hosting your applications on Amazon EC2, then you might consider using Amazon CloudWatch.   How familiar are you with standard and custom metrics?  You should know that you need quite a lot of technical expertise to run Amazon CloudWatch properly. Amazon CloudWatch is a great solution for users who need data and actionable insights to respond to system-wide performance changes, optimize resources and a unified view of their operational health.  But this all comes at a price in terms of the knowledge and experience needed to configure and manage Amazon CloudWatch properly.

Another choice is for you to evaluate and acquire one of the many commercially available application performance monitoring (“APM”) solutions on the market, such as from AppDynamics, Datadog, Dynatrace, or New Relic.  But keep in mind your requirements.  How broadly do you need to monitor?  And what do you intend to do with that information?  Are you ready to be overwhelmed with alerts?  And be aware that many APM solutions do nothing to help you recover beyond pinpointing the issue.  You still have to drop everything to manually restart services or reboot your instances.

Monitor applications running on Amazon EC2 using SIOS AppKeeper

But there is another way.  SIOS AppKeeper is a SaaS service that can be configured to automatically discover any EC2 instances and their services. It then automatically take any number of actions if and when downtime is experienced.  So instead of getting alerts that something is wrong, you get notified that something happened and was automatically addressed.
Why-App_monitoring-hard-2-1024x470

SIOS AppKeeper starts at only US $40 per instance per month. We invite you to view this short video to see how easy it is to install and use AppKeeper.

Why is AWS EC2 Application Monitoring So Hard?

One of our customers, Hobby Japan, a publishing company in Tokyo, was initially using Amazon CloudWatch but their understaffed IT team couldn’t respond fast enough to alerts. They wanted to leverage automation and moved to SIOS AppKeeper.  Since moving to AppKeeper they haven’t experienced any issues or unexpected downtime with their EC2 instance. Here’s a link to a case study on Hobby Japan.

Monitoring your cloud applications shouldn’t be a full-time job.  You want a monitoring solution that is easy to install and use, doesn’t overwhelm you with alerts, and hopefully takes care of systems impairments automatically.  We encourage you to try a 14-day free trial of SIOS AppKeeper by signing up here.

Article reproduced with permission from SIOS

What is Amazon CloudWatch?

by Leave a Comment

What is Amazon CloudWatch

 

What is Amazon CloudWatch?

What you can do with CloudWatch and some hurdles to consider

With AWS boasting a dominant share of the cloud market, many companies are migrating their on-premises systems to the cloud with Amazon AWS.  So, how should a system running in the AWS environment be managed?

In this blog post, we will introduce the features of Amazon CloudWatch, a monitoring service provided by AWS, as well as the challenges of implementing it and how to solve them.

Using Amazon CloudWatch to closely monitor your AWS environment

To ensure that you have a stable cloud environment, it is important to detect anomalies (“system impairments”) quickly and respond in a timely manner.  Monitoring becomes an important and necessary task for any organization moving to the cloud.  This is no different than if you were managing on-premises applications and infrastructure. So, how should you monitor in an AWS environment?  One choice is to use Amazon CloudWatch, which monitors CPU, memory, and disk usage and notifies you when a predetermined threshold is exceeded.  Plus, you can set up your own metrics to monitor various items such as application logs.

The best part about Amazon CloudWatch is that it’s a service provided by AWS itself.  It has a high affinity with Amazon EC2 and other AWS services, so it can quickly respond to frequent functional extensions and specification changes, and can easily support AWS Auto Scaling, which automatically increases or decreases resources according to the load.  Amazon CloudWatch provides precise monitoring tailored to each environment’s unique circumstances.

Amazon CloudWatch implementation challenges

While Amazon CloudWatch is an ideal fit for organizations with experienced cloud engineers and DevOps teams, there are some things the average users should be aware of.

Amazon CloudWatch is effective for monitoring an organization’s AWS environment, but it requires a certain level of skill and knowledge to configure and deploy.  Especially when you set your own metrics, are setting up alerts, or taking into account Auto Scaling, the complexity increases. For example, If you’re setting up monitoring, it’s easy, but if you’re setting up email, rebooting, AutoScaling, etc., depending on the resource situation, it can be difficult.

If you want to automate the recovery process with instructions such as “restart the server when an error occurs”, you must first create a recovery scenario with an AWS Lambda script that provides a detailed description of the conditions and actions to be taken.  How familiar is your team with AWS Lambda?

The principal advantage of Amazon CloudWatch is that you can monitor your environment closely, but in order to do that, you must properly design in advance for each system what items to monitor and when, threshold values, etc.  These design tasks can take a lot of time.  Of course, your mission-critical systems need to be closely monitored in this way, but this level of detail and sophistication is not appropriate for all systems. For some, such as internal websites or WordPress servers, you will want to minimize your operating and labor costs. In such cases, we would like to suggest you consider a tool that can be more easily operated and managed.

SIOS AppKeeper for monitoring operating systems and application services running on AWS

For non-mission critical applications, we would like to recommend SIOS AppKeeper from SIOS Technology.  AppKeeper is easy to install and configure and monitors the services (processes) of the application running on the EC2 instances.  AppKeeper automatically restarts the service when an error is detected and reboots the instance if necessary.   Even users moving to the cloud for the first time can set up AppKeeper to monitor their EC2 instances and recover automatically, without needing to have sophisticated scripting skills.

With AppKeeper, there is no need to select individual services to be monitored. You simply start by selecting the EC2 instances to be monitored and what actions you would like to be taken automatically.  You can always get more specific about which services to monitor and how, but AppKeeper is designed to be easy to configure out of the box.  When an error is detected or automatically restored from, a log of the failure is recorded and stored so that the cause of the failure can be investigated later.

AWS EC2 Monitoring with AppKeeper

Rather than using Amazon CloudWatch to closely monitor everything in your AWS environment, we recommend that you take inventory of your environment based on your SLAs and recovery requirements, and use SIOS AppKeeper to monitor systems and applications where you want to reduce your operational overhead.

Stay tuned for a future blog post where we will go into greater detail comparing how to set up CloudWatch and AppKeeper to perform the same functions.

Learn more about SIOS AppKeeper

Sign up for a Free Trial of SIOS AppKeeper