Skip to main content
Use Foveus to investigate HTTP 500 errors without starting from raw logs. An HTTP 500 usually means the service failed while processing the request. Foveus helps you find the failed execution, inspect the timeline, review response context, and check whether the error belongs to a repeated issue pattern.

​
Start with the service

Open Executions. Search for failed executions in the affected service:
If you know the endpoint, add it:
Use the time range picker to include the period when the error happened.

​
Open the failed execution

Open a matching execution. Start with:
  • endpoint
  • method
  • status
  • duration
  • outcome
  • request context
  • response context
  • logs, if configured
  • exception details, if available
  • linked issue, if available
The goal is to understand what happened during this exact request.

​
Check the execution timeline

Use the timeline to inspect the order of events. Look for:
  • request received
  • validation step
  • downstream call
  • provider response
  • database operation
  • exception
  • timeout
  • final response
The timeline helps you see where the execution moved from normal behavior to failure.

​
Inspect response context

If response context was captured, check what your service returned. For example:
You can search for similar executions by response fields:
This helps you find other executions with the same failure signal.

​
Check provider or downstream responses

Some HTTP 500 errors are caused by downstream services or providers. For example, your service may return HTTP 500 because a provider returned a failure response:
Search for matching provider responses:
Or narrow to failed executions:

​
Check logs linked to the execution

If logs are configured, use linked logs to inspect log lines from the same execution. Look for:
  • exception messages
  • stack traces
  • failed provider calls
  • timeout logs
  • retry attempts
  • validation failures
  • database errors
Linked logs are useful because they are scoped to the execution. You do not need to search through unrelated log streams first.

​
Check if Foveus created an issue

If the execution is linked to an issue, open the issue. An issue can show:
  • failure pattern
  • common factors
  • suggested diagnostic step
  • representative execution
  • linked executions
  • recent activity
  • lifecycle
Use the issue when the HTTP 500 is part of a repeated pattern. For example:
The issue can help you see whether this is a one-off failure or something recurring.

​
Search for the same failure pattern

Use context, endpoint, and status filters to find related executions. By endpoint:
By response error code:
By provider status:
By customer or business ID:

​
Identify the failure boundary

When debugging HTTP 500 errors, try to identify where the failure happened. Foveus gives you evidence. You still decide the fix.

​
Record the next step

After reviewing the execution, record the next step in the linked issue or your team workflow. Good notes are specific:
Avoid vague notes:

​
If no execution appears

Check:
  • the service name matches the service shown in Foveus
  • the dashboard is showing the correct mode
  • the time range includes the error
  • status:failed is not too restrictive
  • the endpoint path matches the captured endpoint
  • the route was not excluded by SDK configuration
  • the SDK middleware is registered
  • the execution is still within retention

​
If response context is missing

Check:
  • CaptureResponseBodies is enabled
  • the route is not excluded
  • the response body is within the capture size limit
  • the response content type is supported
  • redaction did not mask the value
  • sampling did not skip the context snapshot
Example configuration:
  1. Search failed executions by service.
  2. Add endpoint or method if known.
  3. Open a failed execution.
  4. Inspect the timeline.
  5. Review response context and provider evidence.
  6. Check linked logs.
  7. Open the linked issue if available.
  8. Search for the same failure pattern.
  9. Record the next diagnostic step.

​
What to do next