- Home
- >
- Software Development
- >
- Transposit Automates Workflow with a Human Touch – InApps Technology 2022
Transposit Automates Workflow with a Human Touch – InApps Technology is an article under the topic Software Development Many of you are most interested in today !! Today, let’s InApps.net learn Transposit Automates Workflow with a Human Touch – InApps Technology in today’s post !
Read more about Transposit Automates Workflow with a Human Touch – InApps Technology at Wikipedia
You can find content about Transposit Automates Workflow with a Human Touch – InApps Technology from the Wikipedia website
For Tina Huang, the idea of automation without human intervention is misguided. That comes from her study at the University of Chicago on cultural anthropology and blogging, as well as stints at Google and Twitter.
“I worked on Google News, and then, later on, moved up to Twitter. And I had this passion around the human in the loop, right? — like how can you augment artificial intelligence with human editorial?” said Huang, found and Chief Technology Officer at Transposit.
The San Francisco-based startup is focused on integrating the tools used in DevOps and site reliability engineering (SRE). It aims to provide a single source of truth to calm the chaos through automation plus human action.
She maintains that the majority of workflow tools, like Zapier and others, aspire to full automation without human intervention.
“That’s really nice,” she said, “but it very, very limited in the class of problems that can help.”
People often suggest she’ll be out of a job if people can fully automate everything. Her response:
“Well, that’s true if you have a system in a silo that has no change internally and no change externally.”
An incident can happen with change: I’m adding new features to my codebase. I’m adding new infrastructure to my stack. But changes can also happen externally.
“Like at Twitter, a lot of the incidents happen because you have a different traffic pattern due to the Super Bowl, or some event you didn’t expect.
“I remember the Arab Spring causing challenges at Twitter because that was like a spike of usage and a different style of usage than we had expected,” she said.
Modeled on SQL
Huang and Adam Leventhal founded the company in 2016, pulling in Divanny Lamas from Splunk as CEO. Leventhal and Lamas go back to Sutter Hill Ventures, one of its funding partners. The company has raised $50.4 million total after a $35 million Series B a year ago led by Altimeter Capital Management.
Huang saw the world for developers changing, rather than building something from scratch, it was becoming more common to piece together components from various data sources connected by APIs.
They spent three years creating a platform to bring all the workflow tools together in one place. In their Series A pitches, they described it as a relational database of APIs.
“Imagine being able to just query your data with the ease of something like SQL, and not have to worry whether that data was coming from GitHub, coming from Slack, coming from any of these different sources?” Huang said.
Looking at the technology, they realized that DevOps and IT operations were the most likely fit for the idea of human-in-the-loop response, even while directing machine learning to the tasks at hand.
They modeled their technology on that of SQL, which gave developers a way to talk about what data they were trying to retrieve without having to think about how to actually access the data:
“At the very core, that is what the Transposit integration technology is based on. So you could write a SQL query, and we would deal with authentication, pagination, kind of throttling of queries, etc. …
“One of those areas that sort of differentiates us from pretty much any integration platform that I’ve seen out there is the depth to which we sort of took that where it’s not just a thin wrapper on top of API calls. But it really allows the developer not to think about the underlying services.”
Automated Documentation
They applied their ideas initially to runbooks for incident management, that binder that some companies create for those 2 a.m. hair’s-on-fire calls when something breaks. On those occasions the on-call engineer might be sweating the details of code he didn’t write or operations procedures she’s unfamiliar with.
Transposit’s platform enables organizations to build automated runbooks laying out a set of DevOps processes to be executed across multiple tools.
Huang concedes that runbooks aren’t a sexy topic to go after, but maintains that’s largely because people have been pretty uncreative with them — they tend to be flat wiki pages that everyone knows, or at least assumes, are not up to date, so they don’t use them.
Transposit’s answer to this to make them more interactive and useful by aggregating semi-structured and unstructured machine data along with human data.
You can set a trigger, that kicks off an automated workflow on how to proceed. It could be things like starting a Slack channel, filing a ticket for it, assigning a commander, notifying customer success that this incident is ongoing, figuring out which team is involved and paging the person on call.
“It can be everything from flat documentation to adding buttons that help you, so you might have a button that says, ‘restart the service,’ ‘update the status page,’ etc.” Huang said.
It can break down silos and unify workflows between dev and ops with hundreds of pre-built integrations or easily connect to any API. Afterward, you can have a cleanup process as well.
At the same time, it’s documenting every step of the way, providing a full audit trail and postmortem report. The runbooks aren’t static documents. Underlying machine learning algorithms can look at how the engineers recovered and provide data-driven revisions to the processes. That can capture institutional knowledge as well.
In a blog post explaining the need for codified processes, both machine and human, Huang wrote:
“The ideal world is about being able to seamlessly bind these two together. When you allow humans to stitch together pieces of automation, you actually end up with more automation and more robust automation.
“That’s because you can let human intuition step in where the logic to automate would end up being so complex as to cause more problems than it solves, where the logic would be so closely tied to the specifics of a fast-evolving product that it would need to be updated almost as frequently as the product itself.”
Tickets Plus Action
Late last year, Transponsit announced Activities, taking on ticketing systems like JIRA and ServiceNow.
The company doesn’t call them tickets because it generally requires action beyond the ticket itself. There’s usually an accompanying document, a Confluence page maybe, that tells you how you’re supposed to use that JIRA ticket — categorize the incident according to these circumstances, for instance. At the same time, people are talking about the issue on Slack or Microsoft Teams. There are repeatable actions required for filing any ticket — you have to fill in these 10 fields, perhaps.
“One of the beautiful things about the DevOps role is a lot of this can also be automated,” Huang said. “And so some pieces of them that require human intervention like that human router for dispatch — we hear a lot of people still use some form of NOC (network operations center). … Honestly, we’ve heard people even outsource these to third parties. Their job is literally to look at some graphs and determine what team to actually page. Right? So there’s a slight human element to it.
“But then once a human identifies what team to reach out to, the rest of it could be automated.”
No-code Builder
The company touts Transposit as a no-code platform.
In a BetaNews article on 2022 predictions, Ed Sawma, Transposit’s vice president of operations, posited:
Low-code and no-code technologies have opened up new paths to innovation by empowering more users across an organization — with or without technical experience — to contribute and add value to projects or workflows. In 2022, we’ll see DevOps practices gain broader adoption across functions outside of traditional software development. In addition to the growing adoption of no-code tools, non-technical users will get to experience all the benefits of a continuous delivery approach and will want to adopt it for everything digital they create.
The company has a no-code platform as well as a more advanced developer platform. Its no-code builder can have git repositories associated with them. It’s written in Python and designed to be very developer-friendly.
“What we’ve seen from our early customers is [that] they get delighted by the fact that they don’t have to wait on us to build something out for them. You don’t even need to wait on us to build you a data connector,” Huang said.
“We’re built on open standards with OpenAPI. So you know, if you have an internal system, anything that’s an API, you can plug into our system. …You can build almost anything you want. You know, we’ve seen customers string together … transpose it to trigger AWS Lambda to call edge nodes in their compute clusters. And so, it’s very powerful and very, very flexible.”
Source: InApps.net
List of Keywords users find our article on Google:
jira workflow |
python mongodb query builder |
jira issue |
jira workflow automation |
confluence vs servicenow |
confluence vs servicenow knowledge management |
jira ticket |
jira automation documentation |
jira automation email |
servicenow vs jira |
jira email automation |
splunk sort |
splunk jira |
jira automation based on email |
workflow management in confluence |
python jira custom fields |
confluence slack integration |
automation for jira |
runbook |
confluence vs jira service management |
jira custom post function |
mongodb stitch |
confluence workflow management |
create jira ticket from slack |
jira automation based on email address |
automation for jira from email |
jira ticket template |
python create jira ticket |
jira automation issue fields |
software development chicago |
jira portfolio vs splunk |
splunk documentation |
chief technology officer jobs san francisco |
splunk confluence integration |
hire confluence developers |
sql change automation |
google form to jira ticket |
create jira ticket from confluence |
add due date to jira issue |
change status of jira ticket |
issue templates for jira |
jira change workflow |
jira automation send email |
jira system fields |
confluence integration with slack |
automation ideas in jira |
what is jira core |
jira service desk automation limitations |
workflow servicenow |
ticketing system in microsoft teams |
splunk transpose |
which of the following are core areas of jira |
semi automation wikipedia |
mongodb stitch vs aws lambda |
qa-touch |
linkedin zapier |
how to close jira ticket |
workflow post function jira |
can i see custom fields in jira portfolio reports |
tina nguyen facebook |
how to close ticket in jira |
jira spike |
mongodb stitch authentication |
jira issue templates |
confluence workflow automation |
create confluence page from jira issue |
jira change ticket type |
microsoft teams jira connector |
create confluence page from jira |
teams jira connector |
jira automation comment updates reply status |
jira workflow api |
jira ticket templates |
spike jira |
confluence jira table |
how to automate confluence |
jira automation fields |
jira slack connector |
how to change status of jira ticket |
slack jira connector |
hairon plus |
create jira issue from confluence |
2nd line ticket system slack |
confluence create jira issue template |
confluence workflow |
mongodb ops manager upgrade |
confluence vs github |
noc software developer |
spike in jira |
change workflow in jira |
how to change status in jira ticket |
it operation ticket system slack |
jira workflow automation triggers |
confluence api user activity |
jira automation custom fields |
jira automation set due date |
jira ticket change status |
jira code sql |
how to change workflow in jira |
confluence vs slack |
jira automation based on specific email address |
jira testing workflow |
jira vs devops |
confluence automation |
confluence rest api authentication |
adam leventhal |
microsoft teams ticketing system |
confluence page break |
automation result to jira update |
jira workflow testing |
jira git workflow |
runbook designer |
splunk blogs |
binders trans |
no code workflow |
servicenow ui builder |
workflow activities in servicenow |
zapier linkedin |
sql wikipedia |
building a noc from scratch |
jira cleanup custom fields |
no laying up wikipedia |
jira to mongodb |
mongodb jira |
zapier jira |
change issue type in jira service desk automation keyword |
jira mongodb |
jira zapier |
jira post custom field value to slack |
splunk twitter |
teams confluence connector |
servicenow workflow activities |
python jira pulled in stories |
create confluence page from jira post function |
how to close a jira ticket |
icon for hire wiki |
jira add logic to dropdown custom field |
proceedit |
wiki wawa |
jira capture with custom authentiication |
jira twitter |
zapier loop |
jira post function send custom field to slack channel |
servicenow ui builder components |
zapier university |
fire custom event jira |
jira workflow post function |
workflow in servicenow |
confluence content report table |
beautiful confluence pages |
how to create confluence page from jira issue |
linkedin automation jira |
confluence document workflow |
core areas of jira |
university of chicago niche |
automation for jira field components cannot appear in both ‘fields’ and ‘update |
core area of jira |
portfolioe for jira custom fields |
create slack channel from jira issue |
iron bowl wiki |
messag custom fields jira |
splunk wiki |
a bind data source in management group has posted items to the workflow |
where do you arrange jira custom field order? |
confluence review workflow |
create jira issue from slack |
email to jira ticket |
jira post functions |
servicenow developer instance |
automation for jira not assigning |
email to ticket jira |
write a custom post function jira |
it operation ticketing slack |
pagination jobs |
what are the 3 basic components of workflow in servicenow |
create a jira ticket from slack |
external data jira custom fields |
jira portfolio custom fields |
jira ticket from email |
automation of response jira ticket |
create jira issue from confluence table |
splunk chicago office |
how to create confluence page in jira |
creating custom jira workflow and task templates |
email to jira issue |
automation for jira commented by group |
jira automation slack |
servicenow pre-sales jobs |
capture for jira pricing |
jira cloud change workflow |
servicenow query table |
slack confluence integration |
automation for jira advanced text field |
codebase ventures |
jira change project workflow |
jira database custom field table |
jira ticketing system pricing |
the slight edge wiki |
automation for jira confluence page |
expert breakdown microsoft teams |
jira add post function |
low code wiki |
post functions jira |
template jira ticket |
confluence cloud documentation |
jira servicenow connector |
jira time spent report |
there is no integration service found for this workflow |
using confluence for document management |
change workflow jira |
confluence test case template |
devops runbook confluence |
field value changed jira automation |
human touch |
jira add custom icons to confluene edit |
jira operators |
splunk case |
workflow automation triggers jira |
confluence vs microsoft teams |
jira create confluence page from template |
jira vs quality center |
jira was operator |
profile custom fields jira |
restart splunk |
automate confluence page creation |
automation due dates in jira |
confluence documentation management |
elearning splunk |
how to turn off automation for jira |
jira cleanup |
jira cloud components |
jira issue types |
jira share with custom button |
jira worflow |
automation for jira data center |
change jira ticket status |
how to change the status of jira ticket |
how to update a jira field automation |
jira automation due date based on release date |
service now vs jira |
servicenow incident fields |
servicenow to jira connector |
servicenow workflow |
splunk table sort |
automation for confluence |
jira portfolio pricing |
jira vs servicenow |
www humantouch com |
automation for jira email |
confluent ksql |
hire zapier experts |
how to change jira ticket status |
jira actions |
jira vs service now |
jira workflow trigger |
ticketing on slack |
integrating servicenow to jira via rest |
jira database custom field |
jira email ticket creation |
jira query multiple values |
python-jira client |
slack vs jira |
splunk work culture |
confluence connector |
jira operator |
jira ticke |
jira ticket automation |
servicenow jira integration |
automating reporting in jira and confluence |
create ticket jira python |
jira like query |
jira workflow for testing |
automate sql |
components in jira |
confluence and slack integration |
create jira ticket from email |
jira custom report development |
using jira and confluence together |
attach email to jira |
confluence page design ideas |
devops runbooks |
splunk wikipedia |
automation jira confluence |
jira automation dates |
jira forms workflow |
jira internal database |
jira issue.field custom time |
jira servicenow |
jira vs slack |
confluence create jira issue button |
confluence github integration |
devops vs jira |
jira custom field database |
minimal touch technology |
sql vs splunk |
automation for jira documentation |
custom jira workflow |
jira and servicenow |
jira automation due date |
jira cloud workflow |
jira custom report development for cloud |
portfolio for jira cost |
sql developer companies |
altimeter capital portfolio |
how to attach email to jira |
jira custom workflow triggers |
jira portfolio cost |
splunk slack channel |
ticket jira |
tina huang |
changing workflow in jira |
confluence attach file |
confluence cloud slack integration |
how to restart splunk |
integration connectors service now jira |
jira service desk automation custom field |
jira servicenow integration |
microsoft teams vs confluence |
slack and confluence integration |
service now, and jira ticketing systems |
slack ticket system |
what is jira and service now |
capture for jira cloud |
huangs world |
confluence page ideas |
workflow document template |
design system workflow |
Let’s create the next big thing together!
Coming together is a beginning. Keeping together is progress. Working together is success.