Operations | Monitoring | ITSM | DevOps | Cloud

Last October, I published a blog post describing the efforts we've committed to on the Bitbucket Cloud engineering team to achieve world-class reliability. A lot has happened in the past year (understatement of the year)! What the team has accomplished is tremendous, but we've also learned a thing or two that we can work further to improve.

Log monitoring can be a tedious process. When you have logs, you generate numerous log files in the log database that you need to track. Though a log file parser can help you search through multiple or large logs easily, it’s typically one of those processes which we only look at once it stops working. The windows system logs contain operating system logs as well as logs from applications such as Internet Information Services (IIS) and SQL server.

Let’s talk through a scenario: You have a Linux-based VM running on DigitalOcean (aka a Droplet), and you install Netdata on it using our recommended kickstart script. As the installation process winds down, the Droplet starts up the Netdata Agent’s web server and serves the local Agent web dashboard on port 19999.

If you require a way to download your Azure Virtual Machine to either your on premise VMware or Hyper-V environment, perhaps because the cost of running that Azure VM is too high, or even for some compliance reason this blog will show you how to quickly download your Azure VM easily with Carbon. No need to download your Azure VM via powershell, or even downloading the VHD from the Azure portal. Carbon will download and convert your Azure VM to your hypervisor of choice with just a few clicks.

Serverless architectures remove the need to provision and maintain infrastructure components like servers and containers, so developers can focus on writing and deploying code. However, serverless architectures also introduce new challenges to monitoring and observability. Teams building serverless applications can iterate quickly and deploy frequent code and configuration changes, making it difficult to track what impact these changes have on your applications.

If you’re a SaaS business — especially B2B — you know that your profitability can vary significantly from customer to customer. We all have a sense of our “expensive customers,” who use the product heavily and push things to the limit. That also means there are more profitable customers. Who are they? And how do they use the product?

It takes a large team to manage enterprise DevOps, and it can take a large team of binary repository managers, too. It’s vital to get all team members going the same way, and quickly. A growing developer organization will have many instances of Artifactory to help them scale, on multiple nodes for high availability and multi-site repository replication. Configuring them all precisely, with the same set of repositories, users, and permissions, can’t be done effectively one at a time.

Infrastructure monitoring is often equated to infrastructure management, which can blur the line between two very distinct jobs. While they are different, it’s safe to say that both infrastructure monitoring and management have the same end goals, i.e., to maintain the integrity of the network, secure the server, and optimize performance. Infrastructure management (IM) has many use cases, and one of those uses cases is infrastructure monitoring.