Operations | Monitoring | ITSM | DevOps | Cloud

You probably can’t believe I’m asking that question. It’s like showing up to a party and immediately asking about the afterparty. Is it really time to look for the exit? No…but yes. We used to deploy apps on systems in data centers. Then we moved the systems to the cloud. Then we moved the apps to containers. Then we wrapped it all in Kubernetes for orchestration, and here we are. Each advance in technology unlocks doors we couldn’t reach before.

Large portions of software development budgets are dedicated for testing code. A new component may take weeks to thoroughly test, and even then mistakes happen. If you consider software defects as security issues then the concern goes well beyond an application temporarily crashing. Although even minor bugs can cost companies a lot of time to locate the bug, resolve it, retest it in lower environments, then deploy it back to production.

In our previous post, we discussed the recent security incident at Codecov and the following investigation at Mattermost. As a follow-up to that we wanted to share some of the basic design principles as well as a handful of more technical tips and tricks around CI/CD pipeline security that helped Mattermost come out of the incident unscathed.

Dokku can be a cost-effective, convenient way to deploy apps to DigitalOcean. SolarWinds® Papertrail™ can make monitoring the logs of those apps simple and frustration-free. Combine these two technologies and you have an effective deployment process and log management system. Let’s look at Dokku first. Dokku is an open-source platform-as-a-service (PaaS). If you’re familiar with Heroku, you can consider Dokku a private Heroku that you manage.

Finding the perfect flow for your business can take time and patience. Like almost anything else in life, a business must go through stages of maturity before it reaches its final form and only requires regular maintenance. In this five-part series, we’ll dive into Capability Maturity Model Integration (CMMI) and what phases businesses and their DBAs must go through to successfully manage IT as a business.

In previous installments of my “Securing Azure SQL Database” series, I covered Azure SQL Database firewall rules and private endpoints—the first of which is a way to help reduce the public exposure of your database endpoint and the second being a means to remove all public access if necessary. Each option has unique benefits, and some scenarios might call for a mix of the two options.

The Domain Name System (DNS) is at the core of the engine that keeps the internet running. We have explained how DNS works and why it is critical to the functioning of the internet in our Synthetic Monitoring Guide. The DNS resolution relies on various components, such as the DNS resolvers, name servers, authoritative servers, and zone files, to function properly and the process typically takes milliseconds to complete.

Gartner jumps right into it, describing a reorientation of a tool that has previously focused on IT service management and automation. AIOps is now also enabling a variety of new observability use cases for DevOps and Site Reliability Engineering (SRE) teams. This blog presents the guide’s major findings and a link so you can read the report for more details. About the AIOps Platform Market

We're excited to announce the release of two new features this month: customizable Slack incident modals and Incident Tags. Keep reading to more about how they can help your teams manage incidents better!

How do you execute an effective web application availability monitoring? All stakeholders should monitor to ensure that web app’s availability is not compromised. Great design and excellent user experience are put to waste if your web app is not accessible. Let’s establish first how web application monitoring works.