Skip to content

01

Find what caused an incident

Pulls signals from Dynatrace, Splunk and ServiceNow onto one timeline so you see what changed.

  • Evidence time-aligned
  • Entities linked across tools
  • Findings you can trace

Tools it uses

  • dynatrace.list_problemsRuns directly
  • dynatrace.list_deploymentsRuns directly
  • splunk.run_spl_searchRuns directly
  • servicenow.list_changes_near_timeRuns directly
  • correlation.find_entityRuns directly

    Finds the same service, host or application across every connected system.

  • correlation.time_window_overlapRuns directly

    Checks which events overlap in time, with a tolerance for systems whose clocks disagree.

  • correlation.evidence_fetchRuns directly

    Retrieves the full evidence captured earlier in the run, so every finding traces back to its source.

Every tool here only reads. Botify investigates without changing anything in your systems.

  1. Change CHG0031 approved

    ServiceNow

    09:20
  2. Deployment v2.14.0

    Dynatrace

    09:38
  3. Problem P-2409 opened

    Dynatrace

    09:42
  4. 5xx spike · 1,284 errors

    Splunk

    09:45

Likely cause

High confidence

Deployment v2.14.0

correlation.time_window_overlap

02

Reports stakeholders can open

Turn an investigation into PDF, Excel, Word or CSV — Arabic or English.

  • PDF, XLSX, DOCX and CSV
  • Right-to-left for Arabic
  • Charts from real data

Tools it uses

  • artifact.createYour policy decides
  • artifact.renderYour policy decides
  • audio.narrate_artifactYour policy decides

Creating, rendering and narrating a report follow the rules your team sets for each setup.

PDFXLSXDOCXCSV
1 page · A4
First page of an incident report generated by Botify, with KPIs, an error chart and a timeline
Prepared with artifact.render

03

An inbox helper that asks first

Searches, summarises and drafts in Gmail. Sending waits for your approval.

  • Search, read, label and draft
  • Send only after approval
  • Arabic or English drafts

Tools it uses

  • gmail.searchRuns directly
  • gmail.get_threadRuns directly
  • gmail.create_draftYour policy decides
  • gmail.sendWaits for approval

Searching and reading run directly, drafting follows your policy, and sending always waits for a person.

Gmail
Draft
To
payments-leads@company.com
Subject
payment-service incident: status and next steps

Hi team, the 09:40 failures on payment-service trace back to deployment v2.14.0. It has been rolled back and error rates are at baseline. INC0012345 stays open for the review on Thursday.

gmail.send needs your approvalApprove & send

04

Voice and phone, same Botify

Talk in the browser or over the phone — same tools and policies as chat.

  • Arabic and English speech
  • Outbound and inbound calls
  • Country and recipient limits

Tools it uses

  • phone.callWaits for approval
  • phone.transferYour policy decides
  • phone.end_callRuns directly

Every outbound call waits for approval, and only reaches the countries you allow. Premium-rate destinations are always blocked.

Outbound call

+966 5• ••• ••12

Ringing
  1. Botify

    Hello, this is Botify calling about incident INC0012345.

  2. On-call

    Go ahead, what is the status?

  3. Botify

    The deployment was rolled back and errors are back to normal.

phone.call

Pick the first job to hand over.

Root cause, reports, email or calls: start with the one that costs your team the most hours. We set it up on your systems and run it with you, approvals included.