Operations | Monitoring | ITSM | DevOps | Cloud

Azure Service Health continuously notifies you of issues that may affect the availability of your environment, such as service incidents, planned maintenance periods, or regional outages. We’ve recently enhanced our Azure integration to include additional support for monitoring Service Health issues, enabling you to keep tabs on the health of your Azure environment and take proactive measures to mitigate downtime.

Today, we’ll cover some of the ways you might find quite useful in your everyday work. We’ll go through some of the logging best practices in AWS Lambda, and we will explain how and why these ways will simplify your AWS Lambda logging. For more information about similar topics, be sure to visit our blog. Let’s start with the basics (and if you have the basics covered, feel free to skip ahead): How does logging work with AWS Lambda?

Your company, your infrastructure, and probably your whole business rely more and more on cloud services to provide services to your clients and your cloud infrastructure is probably a critical asset for your company. At FlashDrive our mission is to offer a simple and reliable way to deploy apps while we take care of the infrastructure and make sure your apps and services are always online and ready to scale on demand.

Lightrun, the continuous debugging and observability company, today announced the release of a free, self-service version of its popular debugging solution for developers. Lightrun Cloud is not only the most powerful debugger a developer can use to troubleshoot production applications live from within the IntelliJ IDE – but also the easiest to set-up, with a complete self-service experience that gets developers up and running in less than five minutes.

If your business is among the more than one million organizations that use Amazon Web Services (AWS) to host applications and data, there is a good chance that you struggle to monitor AWS. After all, although AWS makes it easy to deploy cloud services, collecting and analyzing data about those services in an efficient, centralized way can be a real challenge.

The promise of running a business on the cloud is that — in theory, at least — you should be able to scale your infrastructure up and down with your customer utilization. This should lead, again in theory, to less maintenance and more opportunity for innovation.

Defining and managing your AWS resources using an Infrastructure-as-Code (IaC) approach implemented with CloudFormation templates makes a lot of sense. While implementing IaC is a widely accepted best practice, it does come with challenges. Managing your infrastructure from lines of code and text-file templates, in the case of AWS CloudFormation, can quickly become overwhelming. We built stack.new to ease that pain.

During the past twenty years, so much has changed in the IT office. Two decades ago, we were still using dial-up modems. Now, the entire world wide web is at our fingertips, and our world of IT is more efficient but complicated too. A few significant IT trends have also developed during this time. One of the most important is the cloud that has also become a common buzzword in business. Like many buzzwords, there is a lot of excitement and confusion surrounding the term.