Are you tired of spending too much time

investigating & troubleshooting issues?

Introducing

R2D2

R2D2 is an automation tool that does early diagnosis for your services.

Add to Slack

R2D2 is for

Service Owners

As a service owner. give instructions
or write configs to create Actionbooks for
your service. Empower team mates to
debug like you.

On-call Engineers

Run actionbooks created by service
owners. Get insights on where to deep-
dive before waking someone else up.

STEP 1

CREATE
ACTIONBOOK

Give a brief description of the objective
and create Actionbooks on the fly.

STEP 2

DEFINE
TRIGGERS

Create rules with static or dynamic
thresholds, for when to run these
Actionbooks

STEP 3

AUTOMATED
ANALYSIS

Get a report within your slack alert
with an early diagnosis report

Leverage AI to create Actionbooks.

_input_tell us how you diagnose

Generally, if there’s an API service latency, check all graphs
in ABC dashboard.
Then look for the trace and see if there’s a specific
component performing poorly.
Keep an eye that “user_revenue” or “conversion_rate” has
not dropped in this duration.

_output_get auto
recommended actionbooks

Identify the dependencies or usages that is causing the conflict.
This can be done by reviewing the application’s codebase and
checking for references to the entity.

If the entity can be safely deleted, resolve any dependencies or usages and attempt the delete operation again.