> ## Documentation Index
> Fetch the complete documentation index at: https://docs.traversal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prompt library

> Example questions to ask Traversal, from active incident investigation to onboarding into unfamiliar systems.

These examples show the kinds of questions you can ask Traversal. Type them in plain language; no special syntax is required.

## Active incident investigation

Describe what you're seeing and when it started. The more context you provide (time, service, identifiers), the more precise the results.

> "We're seeing elevated 500s in `auth-service` since around 14:30 UTC. What's going on?"

> "Investigate latency spikes in `payments-api` starting 14:32 UTC. Trace ID: `abc-123`, error: `connection pool exhausted`."

> "Deployment `a3f9c21` went out at 15:45 UTC. Did it cause the error spike we're seeing in `checkout-service`?"

> "There's a Jira ticket INC-8823 open for this. Can you investigate?"

> [!TIP]
>
> Include a start time whenever you can. It has a large effect on the accuracy of an investigation. See [Tips](https://docs.traversal.com/using-traversal/best-practices.md).

## Follow-up questions

After an initial investigation, ask follow-up questions to drill deeper, challenge a hypothesis, or expand the scope. Traversal retains the context of the investigation, so you don't need to repeat yourself.

> "Can you focus on the database layer specifically?"

> "What happened in the 15 minutes before the spike?"

> "What's the blast radius? Which other services are affected?"

## Service health

Check in on a service or system without a specific incident in mind, for example for routine health checks, pre-deploy sanity checks, or a vague concern you want to look at before it becomes a page.

> "What's the health of `auth-service` over the last 24 hours?"

> "Are there any anomalies in the data pipeline right now?"

> "What typically goes wrong with the database cluster?"

## Dashboards

Point Traversal at a dashboard and ask it to interpret what it sees. This helps when you notice something unusual but aren't sure how to read it, or want a second opinion on whether a pattern is significant.

> "Take a look at the payments dashboard and tell me if anything looks off."

> "Walk me through what you see in the `prod-us-east` latency dashboard from this morning."

> "Is the spike on the error rate dashboard related to the deployment that went out at 15:45?"

## System exploration and onboarding

Traversal can map dependencies, explain service relationships, and surface historical incident patterns. Use it when you're ramping up on an unfamiliar system or preparing for on-call.

> "What does `payments-api` depend on, and has anything changed recently?"

> "Walk me through the checkout flow and its dependencies."

> "I'm new to the payments team. What are the most common failure modes in this service?"

> "What should I know about this service before going on-call?"

## Code and pull requests

When Traversal identifies a root cause tied to a code issue, it can look at the relevant commits, identify the change that introduced the regression, and, if you've given your GitHub or GitLab connection write access, open a pull request with a fix. See [GitHub](https://docs.traversal.com/integrations/github.md) and [GitLab](https://docs.traversal.com/integrations/gitlab.md#token-permissions).

> "The root cause is a missing null check in `payments-api`. Can you open a PR to fix it?"

> "Create a pull request with a fix for the connection pool exhaustion we identified."

> "Look at recent changes to `checkout-service` and tell me if any of them could have caused this."

> "Which commit introduced this regression?"

## Alert trends and recommendations

Traversal can analyze patterns across your alert channels to surface which alerts are noisy, which are flapping, and which thresholds need adjustment.

> "Which alerts are firing most frequently this week?"

> "Are there any alerts that keep firing and resolving on their own? I want to identify what's flapping."

> "Give me recommendations for which alerts we should tune or suppress."

> "This alert has fired 47 times in the last 7 days. Is it signaling anything real, or should we adjust the threshold?"

## Post-mortems

Traversal can generate a blameless post-mortem from an incident channel or from context you provide directly. See [Post-mortems](https://docs.traversal.com/using-traversal/post-mortems.md) for the options, including automatic post-mortem generation in Slack.

> "@Traversal write a post-mortem for this incident."

> "Create a blameless post-mortem for today's auth outage starting at 09:12 UTC."


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.