Operations | Monitoring | ITSM | DevOps | Cloud

So you’ve now finally finished putting all the pieces together – transitioned to Azure, deployed resources, deployed applications, got familiar with Azure Monitor and set up all the monitoring. You’re now collecting all the monitoring, application performance and security data for your Azure resources in Log Analytics workspaces, ready for analysis. (Head over to our Azure Monitor Learning Path if you're still figuring out how to do all that.) But is only the collection enough?

We’ve been doing some Ruby on Rails development lately, in preparation for PagerTree 4, and we wanted to put together a Ruby on Rails Cheat sheet. This is a quick reference guide to common ruby on rails commands and usage.

No matter your business, keeping customer data secure is critical toward keeping your customer’s trust. With the rise in data breaches (and subsequent security certifications), we don’t have to tell you why you should scrutinize every cloud service that you consider — including us. To that end, we believe in being explicit with our compliance. And that includes how we pursue independent certifications like ISO, HIPAA, and now, SOC 2 Type II.

Using the cloud reduces on-premises infrastructure costs and related maintenance. Instead of deploying more servers, storage, and networking components to your own datacenter, you are now deploying these as cloud resources. Using the cloud is supposed to reduce infrastructure and maintenance costs. However, deploying cloud resources also risks over-commissioning, under-usage, and keeping resources running that are not always needed or, even worse, no longer in use.

How do you handle deployment failures with a single-tenant database architecture? We’ve had a question come up from a couple of customers regarding an interesting use case with Redgate’s SQL Change Automation. In this scenario, customers say: A natural question that arises is what to do when a deployment fails against a single database. For example: One approach that seems simplest to folks is wrapping the entire multi-database deployment into a single transaction.

An IT project can introduce a variety of challenges during implementation. The IT team handling the project should constantly improvise and embrace mid-project adjustments to make sure everything is in place. This is especially true when dealing with a company-wide change that might come with varying levels of complexity, risk, and impact. Project management in ITSM ensures seamless implementation of complex IT projects within the stipulated deadline.

BizWho? Why do I even care about it? BizOps, or as the newbies call it Business Operations, is the foundation for scalability. If your goal is to take your company from a Palo Alto garage to unicorn status, good luck getting there in one piece without BizOps.

As an AWS Advanced Technology Partner with AWS Containers Competency, Tigera is thrilled to announce that Calico and Calico Enterprise are both now available as AWS Quick Starts. If you’re unfamiliar with the concept, an AWS Quick Start is a ready-to-use accelerator that fast-tracks deployments of key cloud workloads for AWS customers.

First off, what is synthetic monitoring? What if synthetic monitoring meant monitoring whether or not something is real or fake…watch out Kardashians! Jokes aside, no, synthetic monitoring doesn’t monitor celebrity plastic surgery decisions. Synthetic monitoring is a kind of website performance monitoring that simulates user interactions with a site. A great synthetic monitoring tool instantly alerts you when an issue is encountered.

Unpatched security vulnerabilities are utilized in the majority of data breaches and ransomware attacks. In fact, research shows that many CVEs go unfixed for long periods to time leaving companies open to unnecessary exposure. 60% of breaches involved vulnerabilities of which a patch was available but not yet applied. This is why vulnerability management is so important and not only having a plan but selecting the right tools to support your plan.