Operations | Monitoring | ITSM | DevOps | Cloud

Nowadays, microservice architecture is a pattern that helps to innovate quicker by enabling easier scalability, giving language flexibility, improving fault isolation, etc. Systems built this way also bring some downsides. Moving parts, concurrent invocations, and different retries policies can make operating and troubleshooting such systems challenging. Without proper tools, correlating logs with metrics may be difficult. To overcome these challenges, you need observability.

Migrating your DNS to a cloud provider like Amazon’s Route53 service can be a daunting task. Thankfully, with dns-tools you can test your DNS records before and after the migration to ensure that everything made it across in one-piece. This is the three steps we follow when migrating to Route 53: Follow along below and in just 10 minutes you’ll know if everything will migrate smoothly for you.

Who’s faking it? Data-driven decision-making (and ensuring related investment is delivering on its promises) has been elevated in importance. Every enterprise is replacing opinion with data-driven decision-making, correct? A brand new research report from EMA (Enterprise Management Associates) titled, “A Data-Driven Enterprise” looks behind the curtain to separate facts and reality from fiction and aspiration. Here are some of the findings from the latest research on enterprises.

What kind of log information should be reported up the chain? At a certain point during log examination analysts start to ask, “What information is important enough to share with my supervisor?” This post covers useful categories of information to monitor and report that indicate potential security issues. And remember: reporting up doesn’t mean going directly to senior management. Most issues can be reported directly to an immediate supervisor.