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?

Auvik and Cherwell recently co-hosted an information-packed webinar to answer some important network integration questions facing network managers: How do we get ahead of our workload and how do we know where to start? Let’s look at some of the key takeaways from the webinar (you can watch here) on how to move from a proactive to a reactive network operation model, how network integration solutions can help put out fires faster, and when to incorporate tools to automate processes.

We often get requests from our customers on how to monitor a Windows server or workstation with StatusCake. So today I wanted to take you through a great method of doing this that you should be able to set up in just a few minutes on a Windows 10 workstation, or Windows server. We provide this coverage using the PUSH variant of our uptime monitoring – a type of reverse monitoring that requires the device to contact us in order to demonstrate downtime.

Google has made page speed a ranking factor in mobile searches for quite sometime now. Thus measuring performance has become a key part of any web development project. Performance, accessibility and general SEO best practices are major factors in search engine rankings. Your site's performance can have a big impact on how it is perceived. It can be stated as how fast a website is, or how good the user experience is with the site.

Monitis, once a stand alone monitoring solution, has become Teamviewer Web Monitoring. If you don’t like or don’t need the changes offered you may be looking for alternatives to Monitis. Monitoring is integral to your growing suite of web and application monitoring, and it can be difficult to find a replacement that will do everything you need in one software.

In my first post in the Kubernetes Logging Simplified blog series, I touched on some of the ‘need to know’ concepts and architectures to effectively manage your application logs in Kubernetes – providing steps on how to implement a Cluster-level logging solution to debug and analyze your application workloads. In my second post, I’m going to touch on another signal to keep an eye on: Kubernetes events.