Operations | Monitoring | ITSM | DevOps | Cloud

This is the second in a two part series on how we built our workflow engine, and continues from Building workflows (part 1). Having covered core workflow concepts and a deep-dive into the Workflow Builder in part one, this post describes the workflow executor, and concludes the series with an evaluation of the project against our goals.

Over the years we’ve received requests from our customers for a feature that can enable their customers and their end users to create/ report incidents directly on Squadcast. To our valued customers - we heard you! We are excited to introduce Webforms to do exactly that. In the past, we’ve addressed the challenges pertaining to On-call processes and best practices that teams can implement.

Almost every organization is going through digital transformation. According to IDC, direct digital transformation investment is growing globally at a compound annual growth rate of 15.5% and is expected to approach $6.8 trillion by 2023. Customers quickly embrace the benefits of a customer experience reshaped by technology. However, they have little patience when that technology doesn’t work as expected.

Hey folks! We’re excited to announce that we’ve vastly expanded the capabilities of our Terraform provider. Previously, our Terraform provider was limited to creating and managing services as a resource. We have now covered the entire spectrum of resources available on Squadcast right from creating and managing users, escalation policies and also managing SLO’s via our Terraform provider. What does that mean for you?

We are thrilled to announce that Grafana Incident is now generally available to all Grafana Cloud users, including our generous free tier. (You can sign up for a free Grafana Cloud account now.)

If you’re familiar with PagerDuty, you probably associate it with alerts about technical services behaving in ways they shouldn’t. Maybe you yourself have been notified at some point that a service wasn’t available, was responding slowly, or was returning incorrect information. That’s the common use of a service in the PagerDuty platform.