How to Monitor the Health of Your Application and Infrastructure With the Same Solution

With an attractive total cost of ownership of cloud-based solutions versus on-premise solutions, a highly flexible nature and the ability to scale up rapidly, there has been a steady increase in companies moving infrastructure out of racks and into the cloud.

As more companies move their mission critical systems out of their physical control to these cloud-based solutions, it only makes sense that their application and machine generated logs are even more important than ever before.

With that in mind, we’ve been working closely with Amazon and Amazon Web Services (AWS) to deliver the tools that can help you manage your systems on these new, intangible servers. No longer can you go into a room, see all your servers, manually hook up and make sure that they are all running as expected…those days are gone. A new day needs a new solution.

There are 2 distinct items that a company needs to monitor when using a cloud-based solution

  1. The health of the application
    This is your general application lifecycle management, from when you start up your application on a instance to when you shut down your application. It involves monitoring how your application is behaving, ensuring that the code/application is functioning as expected ,and catching any errors or unexpected responses to be able to identify the bugs and resolve.
  2. The health of your infrastructure
    This, as the name infers, is monitoring the underlying systems that support your application. AWS provides this information through their CloudWatch system about the instances that you use to run your application. We capture and collate this information into a digestible log format.

As we all know, the health of one of these can have an effect on the other. Even with that known, though, it’s quite traditional for an operations person to look after the infrastructure and a developer to look after the application.

Application Infrastructure Health

By combining these information sources into a single tool, you can greatly increase a team’s ability to quickly identify issues and put resolutions in place, making it the ideal solution for companies either already on, or thinking of moving onto, AWS.

For quick instrumentation, we have the AWS Connector, our traditional log collection tool for AWS. This is used to quickly and automatically discover and collect all the logs from your Amazon instances, even as you scale your environment.

We’ve also recently released Logentries OpsStream into open Beta, which collects all the infrastructure information that Amazon CloudWatch exposes for your infrastructure.

By using these 2 data collection services from Logentries, we give you the ability to have all of your AWS machine generated data in one location. Beyond that, it’s all set up to be analzyed with our log management tools, including search, tags & alerts, graphs, and more, ensuring you can manage your system with the least effort.


You Might Also Like

Posted in AWS, Cloud, DevOps, Log Management, Logentries, Monitoring, Web

Leave a Reply

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



Subscribe to the Blog