This is a 2 part setup guide on how you can successfully use DrDroid.

​
Day 0: Setup alerts and configure team

​
Why do this:

  • This will enable you to see grouping of alerts in real-time with literally no effort apart from sending alerts via webhook or using the Slack App.
  • The will enable you to understand how issues, teams, routing, notifications and alerts work in the platform.
  • This will also expose you to understanding how our platform, on a daily-basis, gives you suggestions and updates your wiki, creates RCA when needed and summarises your noisy alerts.
This will help you understand how DrDroid is designed for real-time noise reduction.

​
Day 1A: Create services and configure data sources (integrations)

​
Why do this:

  • Define a couple of services in the catalog and the data sources of where relevant data for that services lies: For e.g. where it’s metrics / logs are (Grafana/APM tool) or where it’s deployment / code is (Github/Jenkins) or where it’s deployed (k8s, ecs, etc.).
  • This will enable you to give context of a service to the agent so that it uses the context to debug issues better after it’s raised.
  • This will improve alert correlation and root causes analysis while investigating issues.
  • Once the service to team mapping starts happening, it’ll be easy to quickly move from an alert to respective engineer/document and vice-versa in a couple of clicks.

​
Day 1B: Add custom context with Knowledge Base access

​
Why do this:

  • Enable connection to your Wiki / upload documents or create documents with guidelines and context specific to your team.
  • This will get agent access to the docs and can search it contextually during an issue/investigation.

​
Step by step instructions

​
Day 0:

  1. Send alerts to DrDroid:
    • This happens directly via webhooks or by installing DrDroid Slack App and adding it to all the channels where you receive alerts.
    • DrDroid starts taking note of every alert and it’ll start grouping it into incidents/issues in real-time.
  2. Define your team & users:
    • Go to users page and add your engineers
    • Define your first team in Team catalog. You can define the escalation & notification policy here along with the on-call rotations and mapping to respective projects in JIRA/Linear/etc.

​
Day 1A:

  1. Define a service:
    • Create a service and start filling information about the service. You might notice smart recommendations and auto-filling options in this page. These can be leveraged if you do the next step before this current one.
  2. Add integrations:
    • Decide what integrations are most relevant for that service and add those from the integrations page. We even support integrations to tools that are self-hosted. Please refer to the relevant document for how.
  3. Add integration as datasource in service:
    • Within a service, you will be required to define data sources. After you have added integrations, you can define them in the UI against that service. This will ensure that when investigating the service, the agent knows exactly where to look up for what data.

​
Day 1B:

  1. Existing Docs? Connect your Knowledge Base or Upload your own
    • We have integration with BitBucket, Github and Confluence for 1-click Wiki integrations — so if your wiki is located on one of these, with one API call, you’ll be able to connect them.
    • Alternately you can bulk upload or create documents by yourself.
    • These documents can be selected during an investigation or can be auto-selected by AI too.