Skip to main content
After your service sends telemetry, open Foveus and inspect the execution. An execution is one run of work in your application. For an API service, it is usually one HTTP request.

​
Open the Executions page

In the Foveus dashboard, go to Executions. The Executions page is query-first because execution data can be high-volume. Start with a service name, endpoint, trace ID, issue ID, or context value. If you set ServiceName to orders-api, search: 
service:orders-api
If you did not set ServiceName, Foveus uses your project assembly name.

​
Find the request you triggered

Use the time range picker to include the time when you triggered the request. Then search by service: 
service:orders-api
You can narrow the result further by endpoint or method. 
service:orders-api method:GET endpoint:/orders
Open the most recent matching execution.

​
Understand the execution row

An execution row gives you a quick summary of what happened. Common fields include:
FieldMeaning
ServiceThe service that produced the execution.
EndpointThe HTTP path or operation that ran.
OutcomeWhether the execution succeeded, failed, or returned an unknown outcome.
DurationHow long the execution took.
TimeWhen the execution occurred.
Matched contextContext fields that matched your search, if you searched by context.

​
Open execution details

Open an execution to inspect the full execution detail page. Execution details can include:
  • request and response context
  • execution timeline
  • logs
  • duration
  • outcome
  • failure details
  • related issue, if the execution was grouped into an issue
The execution timeline helps you understand what happened in order.

​
Search by context

If your service captures structured context, you can search for executions by business values. For example, if the response contains: 
{
  "orderStatus": {
    "value": 1,
    "label": "Confirmed"
  }
}
Search by the nested value: 
service:orders-api context:orderStatus.value=1
Search by string values with quotes: 
service:orders-api context:orderStatus.label="Confirmed"
Strings should use quotes. Numbers and booleans do not need quotes.
Foveus searches indexed execution context. It does not scan arbitrary raw request bodies.

​
Use context search for support cases

Context search is useful when someone reports a problem but does not have a trace ID or execution ID. For example, if a customer reports that an order failed, search by a known business identifier: 
service:orders-api context:customerId="cus_12345"
Or search by a request ID: 
service:orders-api context:request_id="req_12345"
Foveus normalizes common key styles, so these can resolve to the same searchable key when indexed: 
requestId
request_id
request-id

​
If you do not see the execution

Check the following:

​
You are viewing the right mode

Foveus defaults to Test mode. If you are using a test key, make sure the dashboard is showing Test mode. If you are using a live key, set Mode to live in your SDK configuration and view Live mode in the dashboard.

​
Your time range includes the request

Set the time range to include when the request happened.

​
Your service name matches the execution

If you did not set ServiceName, search by your project assembly name. If you overrode ServiceName, search by that value. 
service:orders-api

​
Context fields may not be indexed yet

Execution Context Search works on indexed context. If you recently changed context indexing settings, trigger a new request and search again. New indexing settings apply to newly ingested executions.

​
The execution may not include the value you searched for

Open a nearby execution and check the request or response context. For example, if you searched: 
context:orderStatus.value=1
confirm that the execution response actually included: 
{
  "orderStatus": {
    "value": 1
  }
}

​
What to do next