Transposit announced expanded functionality of Transposit Actions and Runbooks, enabling more rapid incident response times and consistent data across all integrations.
The new runbook builder template and additional capabilities for actions allow teams to automate repeatable tasks at the onset of a runbook as well as group actions together as a single executable operation. To ensure consistency of data across processes, Transposit is also enabling teams to take output from an action and pass it through as input for another action.
“Our updated no-code runbook builder amplifies the power of human-in-the-loop automation, empowering customers to automate burdensome, repetitive tasks while allowing them to step in when necessary to more rapidly take action,” said Divanny Lamas, CEO of Transposit. “Transposit is simplifying automation with stateful runbooks and other features that keep humans as our number one priority.”
With the newly extended set of capabilities, users can now conjoin a set of standalone actions into a group of actions with a singular button to execute them, drastically accelerating incident response times. While incident response actions inherently cannot be entirely automated, processes should not be entirely manual either. After the initial triage of an incident, teams move into incident coordination and remediation. In these phases, there are many actions that can be performed simultaneously, including further escalations, communications to larger groups, SLA awareness and response urgency.
Development and operations teams can now build actions in Transposit to take the output of one action as the input of another action, creating limitless opportunities for automation. Teams can create incident management processes that take the unique Jira issue key to tie together communication channels in Slack and Zoom and to escalate issues to engineers and the operations team, all with the context available in the originating ticket. In doing so, all communication channels created through the runbook use the same incident name.
The updated no-code runbook builder boosts the power of Transposit’s human-in-the-loop automation, redirecting the burden of repetitive actions to automation technology while enabling humans to intervene and take action faster. The new UI makes it simple to automate predictable tasks that kick off any activity, take action on multiple connected services with a single click and automate actions to run when a runbook is done or has an error.
The new template fully automates actions on the onset of a runbook. For example, when an incident begins, teams may create a Jira ticket and Zoom bridge and conduct an AWS service status check. Now, these actions will automatically execute once a runbook is in-use.
Teams can choose to automate actions upon completion of a runbook. Such actions can include creating an incident report, closing a Slack channel or adding an update to Statuspage. When an automated action has an error, the runbook state will update to “error,” guaranteeing teams are aware that an element has not run properly and can take corrective action. Teams can create automated actions like notifying the incident commander or restarting a server.
Transposit is creating new actions every day to create more automated scenarios for the platform’s hundreds of connectors. New actions have been added with GoToMeeting, GitHub, Google Drive, Octopus and Airtable that enable teams to do everything from creating GitHub releases and repos, to creating a Google Drive folder to deploying an Octopus release.
The Latest
I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...