Operations | Monitoring | ITSM | DevOps | Cloud

One of the most notable advantages of the Cloud is the ability to scale resources to meet demand. We then scale out or up when the demand increases, and we scale in or down when the demand decreases. For the record, scaling out / in refers to increasing or decreasing the number of instances of a given resource, whereas scaling up / down refers to increasing or decreasing the capacity (CPU, Ram, Disk, I/O performance) or a given instance.

If you didn’t attend our recently concluded DevOps Cloud Days online conference, you missed a learning event that those who did called “fantastic” and “meaningful.” In written feedback, developers, operations staff, and security admins who attended described the presentations as “powerful,” “inspiring” and “excellent.” Fortunately, it wasn’t your last chance to share that fruitful experience with us.

It's something you know. Those who rely on or offer Software-as-a-Service (SaaS) solutions are under constant pressure to innovate. Often, this means quickly building new features and releasing them more frequently. Staying on budget and on time is also critical for staying competitive. Likewise, SaaS providers should also offer customers cost-effective solutions to their technology challenges. But that’s not all. You must also always release quality code that provides seamless user experiences.

As businesses accelerate digital transformations and cloud adoption to better serve customers and employees in the face of the global pandemic, operational complexity has also mounted. To untangle these complexities and enable executive visibility into IT ecosystem , business leaders are increasingly looking to observability solutions as a strategic investment.

As a software engineer, I admit I am not the best at networking. Can’t connect to your app for some reason, one going joke is to “always blame DNS” e.g the Domain Name System. My personal DNS experience is usually editing a few records for my personal blog and connecting a few tools and that is it. Thanks to distributed systems, had to learn all about SRV records and some more DNS concepts.

Securing modern-day production systems is expensive and complex. Teams often need to implement extensive measures, such as secure coding practices, security testing, periodic vulnerability scans and penetration tests, and protections at the network edge. Even when organizations have the resources to deploy these solutions, they still struggle to keep pace with software teams, especially as they accelerate their release cycles and migrate to distributed systems and microservices.

Recently we launched features to provide support for Log Analytics in Serverless360. Log Analytics workspaces are used by a lot of different features within the Azure Monitor stack and by providing the ability to link a Log Analytics Workspace to a Business Application in Serverless360 we see that it provides a way you can allow a support user the ability to view and run queries against your log data without needing to be an Azure Expert.

Make no mistake: You can’t overlook software distribution in DevOps. At risk are the reliability, security and speed of your software releases — and your business itself. This is especially true in enterprises that are releasing across numerous edge endpoints or IoT devices. As your releases’ cadence and payload grow, software distribution challenges multiply, particularly at the edge.

Last year, we released PagerDuty Rundeck Actions, a PagerDuty add-on product that connects responders to automated diagnostics and remediation for common problems directly in the PagerDuty incident response workflow. After working with our customers and listening to the community, we are excited to announce that PagerDuty Rundeck Actions now integrates with PagerDuty’s Slack integration.