What can an Expert Library and Digital Assistants do for your team?

Send alerts to Assistants first.

The steps from our library let them triage many different types of alerts out of the box, showing which to escalate and collecting all of the information that an expert would need. Where safe, they can even automate basic remediation. With enough steps, this reduces the load of on-call engineers by 20-80%.

Send your developers here first.

Your developers have a simple question to ask - "is it my code, or something else?" Instead of a group slack channel sending them to an IDP, give an Assistant to automate the process of checking other microservices, platform services, underlying configurations, etc. to see where the problem is first to address the #1 point of friction most developers have when moving to cloud-native architectures.

Did a test fail?

Assistants can collect the status of other microservices and platform components, the env vars, stacktraces and other errors in logs out of the box. Automated information collection for failed tests and CI/CD jobs addresses 40-60%+ of “Keep The Lights On” semi-repetitive work for QA, DevOps and Platform teams

Give Assistants rather than production credentials.

Thousands of teams every year fall out of compliance due to the access they give to production environments. Only a very small team of experts should have direct access, but you often need all-hands-on-deck. Assistants keep you compliant as they hold the credentials and can only run the automation your team has approved.

Digital Assistants connected to key alerts can generate advanced triage reports whenever a key metric goes out of range.  Since the triage reports typically include the output needed for troubleshooting, the vast majority of metrics, logs and traces stored in expensive observability systems become redundant for users embracing this approach.

RunWhen itself reduced our monitoring/logging bills by $40k/month with this approach across our dev clusters.

Runbooks take time... a lot of time...

Writing good runbooks takes time. Automating them takes even more time. Maintaining them in any form takes even more time. Using AI Assistants to run steps from our expert library and/or your own team's private steps, this approach reduces the time and total cost of ownership of runbook automation by 100x.