> For the complete documentation index, see [llms.txt](https://vibemx.gitbook.io/neuronai-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vibemx.gitbook.io/neuronai-studio/observability/inspector.md).

# Inspector

Export Neuron agent and workflow events to [Inspector](https://inspector.dev) without replacing the Studio Debugger.

## Prerequisites

* Inspector account + ingestion key
* No extra Composer package (ships with Neuron / Inspector PHP)

## Setup (< 5 minutes)

1. Copy your ingestion key from Inspector.
2. Add to `.env`:

```env
INSPECTOR_INGESTION_KEY=your_ingestion_key
```

3. Run an agent or workflow in the Studio playground (or host integrate routes).
4. Open the Inspector dashboard — you should see inference, tools, and workflow segments.

Optional force-off (even if the key is set):

```env
NEURONAI_STUDIO_INSPECTOR_ENABLED=false
```

Env-first default: `NEURONAI_STUDIO_INSPECTOR_ENABLED` is `true`. Attachment happens only when the key is present.

## Why Studio attaches explicitly

Calling `$agent->observe(TelemetryTracker)` initializes the Neuron EventBus scope. Neuron then **does not** auto-register `InspectorObserver`. Studio’s `ObservabilityManager` always attaches `Inspector\Neuron\InspectorObserver::instance()` when Inspector is active — fixing the “key set but nothing in Inspector” gap.

## Checklist CLI

```bash
php artisan neuronai-studio:install-observability inspector
```

## Related

* [Native tracing](/neuronai-studio/observability/native-tracing.md)
* [Configuration reference](/neuronai-studio/reference/configuration.md#observability)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vibemx.gitbook.io/neuronai-studio/observability/inspector.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.