AWS Lambda enables you to run serverless functions in the AWS cloud, by manually triggering functions or by creating trigger events. To ensure your Lambda functions are running smoothly, you can monitor metrics that measure performance, invocations, and concurrencies. However, even if you continuously monitor, once in a while you are going to run into what’s termed a Lamba cold start. There are various ways to prevent AWS Lambda cold starts.

As companies move towards a flexible, remote work environment, the demand for VPN services has increased considerably. This need to ramp up VPN infrastructures in such a short time comes with its fair share of operational problems and security concerns. Over purchasing VPN capacity would put a dent in the IT budget while under purchasing would result in loss of productivity.

To our SCOM Community – thank you for making the first worldwide virtual SCOM event such a huge success! As co-hosts of SCOMathon 2020 that took place last week, we are happy to have provided a platform for the SCOM community to get together, learn and connect.

If you are anything like us here at Sematext, you are likely always trying to automate any tedious, repetitive tasks. Repetitio est mater… boringdorum. Setting up monitoring falls in that category. You either do it manually every time you provision a new piece of infrastructure or service, or you automate it. Note that by “service” I mean either an instance of your own application or something like Nginx or Elasticsearch or MySQL or …

Some, maybe. But not most. Look, I have this theory. I also have data. And as with most stories in my life, it all starts with a trip to Las Vegas. In 2017, I attended my first AWS re:Invent in Las Vegas. For a while I heard how re:Invent was either a “cloud” or a “developer” event. I now believe neither to be true. Most people I met at re:Invent were operations folks. They were there to learn about monitoring and managing applications running in AWS.

You have management software that you’ve used for your Linux or Windows servers. Can’t you just deploy a Linux agent and monitor a VMware vSphere/ESX server, or a Windows agent to monitor a Microsoft Hyper-V server? This is a very common question that comes up in any discussion on VMware monitoring and virtualization management. After all, when a VMware ESX server boots, the administrator gets to a Linux login prompt and can login to a Linux operating system.

When thinking about serverless applications, one thing that comes to mind immediately is efficiency. Running code that gets the job done as swiftly and efficiently as possible means you spend less money, which means good coding practices suddenly directly impact your bottom line. How does logging play into this, though? Every logging action your application takes is within the scope of that same performance evaluation.

Two years ago we introduced Splunk Insights for AWS Cloud Monitoring and Splunk Insights for Infrastructure on the AWS Marketplace as a Pay-As-You-Go Amazon Machine Image, where you could initiate an instance and pay hourly to use these products after a 15-day trial. Assessing our portfolio, we are discontinuing these offerings to focus on differentiating capabilities, namely the ability to search and apply machine learning to your data in addition to visualizing insights.

People throw the terms “availability” and “uptime” around a lot, but depending on what you’re monitoring, the definition of these terms may change. In this article we use the narrow definition, accessible, to explore the various options Uptrends has for checking availability on websites, APIs, and servers.