The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.
IT spending remains solid, with a nod to Azure, AI, edge. January is the month to plan ahead which often means taking a closer look at budgets. Spiceworks surveyed more than 1,000 technology buyers in companies across North America and Europe, finding that 44% of businesses plan to increase tech spend in 2020, up from 38% in 2019; an equal number (44%) said that spending would stay the same.
AWS offers a variety of services to solve specific needs. There are some core services, like EC2 and VPC, that let you create an infrastructure for your applications that scales easily. But if you’re new to AWS and also new to infrastructure, you might need to invest some time reading before you deploy your application to AWS. I remember my first time using AWS; the sysadmin explained to me what systems we were using in AWS to run the company’s main application.
An extended period of website downtime is the stuff of nightmares for companies large and small. For a company such as Amazon, even one single minute of downtime can cost as much as $220,318.80 according to the latest calculations. For smaller companies, that figure will be minuscule in comparison, but it’s a number which can quickly snowball the longer your website is offline.
Whatever the nature of your business, whether you are a freelancer or an online retailer, the quality of your website is key to the success of your organisation. A well-run website serves as the online storefront of your organisation, acting as the destination point for people who are searching for the services you provide or the products you sell. Are you confident that you have all the main bases covered when it comes to the management of your website?
Amazon Managed Streaming for Apache Kafka (MSK) is a fully managed service that allows developers to build highly available and scalable applications on Kafka. In addition to enabling developers to migrate their existing Kafka applications to AWS, Amazon MSK handles the provisioning and maintenance of Kafka and ZooKeeper nodes and automatically replicates data across multiple availability zones for high availability.
In Part 1 we’ve described what container monitoring is and why you need it. Because each container typically runs a single process, has its own environment, utilizes virtual networks, or has various methods of managing storage. Traditional monitoring solutions take metrics from each server and the applications they run. These servers and applications running on them are typically very static, with very long uptimes.
Even though containers have been around for ages, it wasn’t until Docker showed up that containers really became widely adopted. Docker has made it easier, faster, and cheaper to deploy containerized applications. However, organizations that adopt container orchestration tools for application deployment face new maintenance challenges.
As the open-source monitoring system Prometheus grew, so did the need to grow its capacity in a way that is multi-tenant and horizontally-scalable, along with the ability to handle infinite amounts of long-term storage. So in 2016, Julius Volz and Tom Wilkie (who is now at Grafana Labs) started Project Frankenstein, which was eventually renamed Cortex.
In the latest article in our series focusing on the Amazon Builders’ Library, Yan Cui highlights the key insights from Avoiding insurmountable queue backlogs by AWS Principal Engineer David Yanacek.
(This is the first post by our new head of Customer Success, Irving.) Sampling is a must for applications at scale; it’s a technique for reducing the burden on your infrastructure and telemetry systems by only keeping data on a statistical sample of requests rather than 100% of requests. Large systems may produce large volumes of similar requests which can be de-duplicated.
