The latest News and Information on Monitoring for Websites, Applications, APIs, Infrastructure, and other technologies.
Continuous Integration (CI) and Continuous Delivery (CD) form the backbone of the product delivery lifecycle. A well tuned, fault tolerant and scalable CI/CD pipeline is very important to support modern Agile teams. Despite obvious business advantages, a rapid release approach combined with continuous change processes resulting from DevOps principles will in the long run generate new challenges. The entire process needs to be carefully examined and controlled.
Troubleshooting production issues in Lambda environments is often challenging. CloudWatch requires developers to comb through logs, search for relevant terms that they may not always know of and has hard-to-consume stack traces. For obvious reasons, we recommend using Sentry to instrument your Lambda Functions code in order to report error stack traces and associated debugging context. Here’s a walk through on how to instrument a Node function.
No matter the application or strengths of your Virtual Machine, it must rely on the resources you provide. In such a scenario, it is common to run into bottlenecks and performance issues that can undermine your operations’ productivity. Often, these bottlenecks present challenges to the team as frequent issues pose risks to the operation’s health.
The ability to detect and alert performance issues quickly is key to reducing the Mean Time to Resolve (MTTR). Proactive monitoring will catch incidents early on but triggering the right alerts and notifying the relevant incident management team is just as critical. Enterprises rely on multiple disparate tools to monitor different systems so there is a lot of data and noise generated which can render incident management inefficient.
When getting started using Icinga 2, it is often enough to use a single master instance. But if your monitoring is business critical, you don’t want to rely on a single master being online. This post will guide you through setting up Icinga 2 with two masters in HA mode.
Centreon is a solution for monitoring applications, systems and networks, based on Nagios source code. On 1st August, 2005 the company Merethis (now Centreon) was founded and began working on “their” Nagios version, calling it Oreon. In July 2007, the Oreon software changed its name to Centreon due to a name conflict with Orion (a component of the SolarWinds monitoring suite).
AWS DynamoDB changed the database game in Serverless and continues to do so, as its design repeatedly proves its huge value. This guide takes you through everything there is to know about DynamoDB so you can rest assured you’re using the service in its best way and reaping all of the benefits.
