Operations | Monitoring | ITSM | DevOps | Cloud

Teams switching from a monolithic application architecture to microservices often face a jarring realization: their time-tested troubleshooting techniques don’t work as effectively. A microservice consists of many independent, distributed, and ephemeral services with varying capabilities for monitoring and logging. Techniques such as stack traces are effective troubleshooting tools in monoliths, but only paint a small portion of the big picture in a microservice-based application.

Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. In the first Five worthy reads of this year, we’ll explore data democratization in detail, from its definition to its pros and cons, and provide some ways to use it for data empowerment.

Ever walk into a corner market, push on the door and find it won’t open? You look down at the handle and are reminded by a sign on the door that you have to “pull” to open it? The LogicMonitor platform uses an agentless collector to pull metrics from thousands of devices and resources into a unified monitoring view (no agents required). We currently offer more than 2,000 LogicModules out-of-the-box that gather metrics from all kinds of systems using many different protocols.

We recently received a notification from a concerned user, because he had found a “vulnerability” in Pandora FMS. Besides, not just any vulnerability but one that seemed to give root access to the system. Next, this user called k4m1ll0 wrote a post in Medium warning the community about this vulnerability. If you want to read the original post, click here.

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.