Velocity's Documentation
  • Welcome to Velocity
  • 📚Guides
    • How to Use Velocity
  • 🔌Integrations
    • Coralogix Integration
    • Datadog Integration
    • GitHub Integration
    • GitLab Cloud Integration
    • Grafana Integration
    • GroundCover Integration
    • Jira Integration
    • New Relic Integration
    • OpsGenie Integration
    • Sumo Logic Integration
  • ❓FAQs
    • General FAQ
    • Privacy and Security FAQ
Powered by GitBook
On this page
  • 💡 Tips for Best Results
  • 1. Investigate an Existing Slack Thread / Message
  • 2. 🆕 Start a New Investigation
  • 3. Automatically Investigate Alerts & Incidents
  1. Guides

How to Use Velocity

How to use Velocity to investigate production issues, on demand or automatically.

PreviousWelcome to VelocityNextCoralogix Integration

Last updated 1 day ago

Make sure the Velocity Slack app is installed and added to the Slack channel where you’re trying to use it. If Velocity isn’t in the channel, it won’t be able to respond or investigate.

This guide walks you through the three main ways to trigger Velocity investigations:

  1. Reply to an existing message, alert, or thread.

  2. Start a new message with context.

  3. Automatically trigger investigations via alert and incident rules.

💡 Tips for Best Results

  • Be clear and specific when asking Velocity to investigate.

  • Include:

    • Service names

    • Timeframes

    • Relevant context or symptoms

  • Use Slack threads whenever possible for continuity and context.

1. Investigate an Existing Slack Thread / Message

You can ask Velocity to investigate directly within an existing Slack thread, whether it’s an alert from a monitoring tool or an active conversation.

When to use:

  • You’re replying to an alert (e.g., from Datadog, PagerDuty, OpsGenie, Incident.io, Grafana Alerts, etc...).

  • You’re joining a conversation about a production issue.

How to trigger:

Reply in the thread with the relevant instructions to Velocity, for example:

  1. @velocity investigate

  2. @velocity ????

  3. @velocity what’s going on here?

Velocity will reply in-thread with a detailed investigation summary.

Tip: Thread replies ensure Velocity has the full alert and discussion context.

2. 🆕 Start a New Investigation

You can trigger a new investigation by messaging @velocity in any Slack channel with the relevant context.

When to use:

  • You noticed something off (e.g., latency, error spikes).

  • You received an alert outside the normal alerting flow.

  • You want to proactively analyze service behavior.

How to trigger:

Send a message like:

  1. @velocity I have an issue with service-x that started around 2 PM UTC. Please investigate.

  2. @velocity analyze the last hour of dashboard-x and let me know if you see anything unusual.

  3. @velocity I got this alert about 5xx errors from API-Gateway. Can you check?

  4. @velocity CPU usage on service-y is spiking since 10 AM. What's going on?

The more specific your message (service name, timeframe, context), the better Velocity can help.

Velocity can be configured to automatically trigger investigations based on alerts or incidents from your monitoring and on-call tools.

Velocity works in the background so your team has investigation results ready when they engage.

When to use:

  • You want Velocity to proactively triage high-priority incidents.

  • You want zero manual effort during critical moments.

Setup Examples:

  • Auto-investigate all P1 PagerDuty incidents.

  • Auto-investigate Datadog alerts tagged with auto-investigate.

3. Automatically Investigate Alerts & Incidents

📚
🧵
⚠️