Operations | Monitoring | ITSM | DevOps | Cloud

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.

When you’re investing in automation solutions, ultimately, tangible results need to follow quickly. Getting a return on investment (ROI) out of an automation project after two years is something that would have been OK in the not-so-distant past but is no longer acceptable nowadays. With the current speed of change, where new technologies come and go and existing ones evolve at lightning speed, IT teams require much faster time to value on automation investments.

You are not the only one asking this seemingly popular question! Several companies are torn between the rise in appeal of open-source databases and the undeniable challenges inherent to their adoption. Let’s explore the trends, the drivers and the challenges related to open-source database adoption.

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.

At incident.io, we’re building tools to help people respond to incidents, often by automating their organisations’ process. Much of this is powered by our Workflows product, which customers can use to achieve things like: Workflows as a product feature are incredibly powerful, and we’re proud of the value they provide to our customers. Behind-the-scenes, though, building something like workflows can be difficult.

Curious about Microsoft Azure and the best ways to connect? Azure is a hybrid Cloud Service Provider (CSP) with customized, scalable, cloud-based packages. These encompass Software as a Service (SaaS), based on subscription-based software licensing and delivery, Platform as a Service (PaaS), allowing companies to develop, deploy, manage, and update applications, and Infrastructure as a Service (IaaS), providing high-level application programming interfaces (APIs).

One of the critical differences between distributed tracing and business activity monitoring is that distributed tracing usually assumes that your transaction executes from start to end in a reasonably short time. An example would be that your call to an API might then drop a message on a queue which a function processes and loads into a database.

Migrating to a cloud-based phone system is compelling because it eliminates the costs and time associated with deploying and managing legacy phone system/PBX hardware and proprietary business phones. However, moving 100% of an organization’s communications infrastructure off-site can present new challenges. If the connection to the cloud is lost, a site could lose both external communications and intra-site communications.

Has this ever happened in your weekly stand-up? ‍