Operations | Monitoring | ITSM | DevOps | Cloud

Today I will talk about naming convention because I think this is so critical to implement from day one, and people tend to forget. We earlier addressed the importance of providing a good naming convention to your Logic App name and actions inside your business process. Today we will speak about the Connectors (or API Connections) naming convention.

Amazon Web Services (AWS) provides three types of Elastic Compute Cloud (EC2) instances; On-Demand Instances, Reserved Instances (RIs), and Spot Instances. EC2 On-Demand instances are the default and most expensive instances. RIs and Spot instances offer discounts of up to 72% and 90% on On-Demand instances, respectively. The Reserved Instances are long-term commitments that guarantee you compute power for a year or three. Spot instances fluctuate in price and availability constantly.

I recently published a couple of blog posts about what happens when you invest in a thoughtful incident management strategy and three first steps to take to do so. What I’m getting at in these posts is that we need a shift toward proactivity in the software operators community. I’d wager most of the world is responding to incidents as they happen, and nothing more.

Imagine having the ability to instantly know when a Kubernetes compliance or security violation occurs. Now you can with Shipa Insights. Coupling Shipa Insights with the robust notification and alerting capabilities of PagerDuty makes this very possible. Shipa has the capability of sending fine-grained events externally e.g to PagerDuty. Now with the power of Shipa Insights, you have the capabilities to alert on policy violations. Let’s take a look at gettings started.