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

# Investigate on demand

> Ask Ordyn about your alerts, logs, metrics, or code any time, from Slack, the app, or your issue tracker.

You do not have to wait for an alert. Ask Ordyn directly and it runs a full investigation across everything you have connected.

## From Slack

Mention Ordyn in any channel it has been invited to:

```text theme={null}
@Ordyn why did p99 latency on checkout double this afternoon?
```

Ordyn replies in a thread. Follow up in the same thread.

## From the app

Open **Investigations** and type your question. Ask about a specific error, a service, a metric, or a recent change.

## From your issue tracker

| Tool | How to trigger |
| - | - |
| **Linear** | Assign the issue to Ordyn, or mention Ordyn in a comment |
| **Jira** | Assign the issue to Ordyn, or mention Ordyn in a comment |
| **Asana** | Assign the task to Ordyn, or mention Ordyn in a comment |

Ordyn posts its findings as a comment and keeps the issue updated.

## Asking good questions

* **Be specific.** "Investigate the 500s on the payments API since 2pm" beats "what's wrong?"
* **Name things.** Services, endpoints, error messages, and time ranges all help.
* **Connect more sources.** Ordyn can only reason about what it can read. See [Integrations](/integrations/overview).


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