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

# Send first execution

After installing the SDK, trigger a request in your service and confirm that Foveus captures the execution.

An execution is one run of work in your application. For an API service, an execution is usually one HTTP request.

## Before you start

Make sure you have:

* Installed the Foveus .NET SDK
* Added your Foveus API key
* Added the Foveus middleware
* Started your service

A minimal setup looks like this:

```csharp theme={null}
builder.Services.AddFoveus("fov_test_...");

var app = builder.Build();

app.UseFoveus();

app.MapGet("/orders", () =>
{
    return Results.Ok(new
    {
        status = "ok",
        orderStatus = new
        {
            value = 1,
            label = "Confirmed"
        }
    });
});

app.Run();
```

<Note>
  Foveus uses Test mode by default. You do not need to set `Mode` while validating your setup.
</Note>

## Trigger a request

Call one of your service endpoints.

```bash theme={null}
curl http://localhost:5000/orders
```

If the request reaches your application, the SDK captures the execution and sends it to Foveus.

## Find the execution in Foveus

Open your Foveus dashboard and go to **Executions**.

Search by service.

If you did not override `ServiceName`, Foveus uses your project assembly name.

If you set `ServiceName` to `orders-api`, search:

```text theme={null}
service:orders-api
```

You should see a recent execution for the request you just triggered.

## Open the execution

Open the execution to inspect:

* endpoint
* method
* duration
* status
* request context
* response context
* logs, if configured
* outcome and failure details, if available

Foveus shows the execution as a timeline so you can understand what happened during the request.

## Search by response context

If your response contains structured context, Foveus can index safe scalar fields for search.

The sample endpoint above returns:

```json theme={null}
{
  "status": "ok",
  "orderStatus": {
    "value": 1,
    "label": "Confirmed"
  }
}
```

Search by the nested value:

```text theme={null}
service:orders-api context:orderStatus.value=1
```

Search by the label:

```text theme={null}
service:orders-api context:orderStatus.label="Confirmed"
```

Strings should use quotes. Numbers and booleans do not need quotes.

<Note>
  Execution Context Search uses indexed execution context. It does not scan arbitrary raw request bodies.
</Note>

## If you do not see the execution

Check the following:

### The API key is valid

Confirm your configured key starts with the expected prefix.

```text theme={null}
fov_test_...
```

### You are viewing the right mode

Foveus uses Test mode by default. Make sure the dashboard is showing Test mode while using a test key.

### Your service name matches your search

If you did not set `ServiceName`, search by your project assembly name.

If you overrode `ServiceName`, search by that value.

```text theme={null}
service:orders-api
```

### The request reached the middleware

Make sure `app.UseFoveus()` is registered in the request pipeline.

```csharp theme={null}
app.UseFoveus();
```

### The selected time range includes the request

Set the dashboard time range to include the time when you triggered the request.

## What to do next

* View your first execution: [View your first execution](/get-started/view-your-first-execution)
* Learn how executions work: [Executions](/concepts/executions)
* Search by business context: [Execution Context Search](/concepts/execution-context-search)
* Configure the SDK: [SDK configuration](/sdk/configuration)