Rollbar to enhance code with new AI-assisted workflows and automation-grade grouping
Rollbar needs to shift builders’ focus to constantly enhancing code, as an alternative of getting to constantly repair it. The continual code enchancment platform supplier introduced two new options designed to cut back the time spent monitoring, investigating and debugging code.
The brand new AI-assisted workflows are automated workflows that assist improvement groups catch and deal with errors earlier than they attain customers.
Automation-grade grouping is the next-generation of Rollbar’s grouping engine, and supplies the muse of the AI-assisted workflows, and robotically teams related errors.
“Our AI-assisted workflows, powered by our automation-grade grouping, are an trade first to cut back the each day noise and handbook work of fixing code for builders to allow them to concentrate on constructing and innovating,” stated Brian Rue, CEO and co-founder of Rollbar. “Our funding in these automation options and our Steady Code Enchancment Platform – together with our firm growth, rising buyer base, latest Sequence B funding, and new visible model identification – spotlight our dedication to assist builders construct software program shortly and painlessly.”
With at the moment’s announcement, Rollbar is asserting three AI-assisted workflows that are actually out there.
Rollbar toolkit for Kubernetes with integrations with Prometheus, Kubernetes, and Weaveworks Flagger. “This enables improvement groups to automate choice making for progressive deployments of recent code variations utilizing Rollbar knowledge on distinctive new errors and regressions,” Lubos Parobek, who’s on the product administration crew at Rollbar, wrote in a weblog publish.
Automated characteristic flag triggers with LaunchDarkly integrations. This workflow will permit groups to robotically flip off characteristic flags with a kill swap. It options progressive supply, take a look at in manufacturing, proactive monitoring and A/B testing.
Automated concern monitoring with integration for concern monitoring instruments similar to Hira, GitHub, and Clubhouse. “The distinction now could be that tickets may be robotically created for any new or crucial error. Arrange predetermined guidelines to have management over how tickets are robotically generated, Parobek wrote.