Latest Profiler Request

Learn how to open the latest captured profiler request, interpret its diagnostic data, and keep profiler access secure in development.

The latest profiler request view identifies the most recently captured request that the application profiler has stored. It provides a quick entry point to a request-specific diagnostic profile, where you can inspect timing, database activity, logs, exceptions, and other debugging information.

What the latest profiler view does

A profiler is a development diagnostic tool that collects request-level and performance information. The latest profile is the most recently stored request record available to that profiler.

The latest view is useful when you have just loaded a page, reproduced a slow response, or triggered an error. Instead of searching through older records, you can open the newest captured profile and begin investigating immediately.

The latest view is an entry point, not usually the complete diagnostic report. After selecting the latest captured request, open its request-specific profile to inspect the details collected during that request.

Accessing the latest profile

Use the profiler's latest-request route in a development environment:

/_profiler/latest/

Run the application in its local or protected development environment.
Load a page or send another request to the application.
Navigate to the latest profiler request.
Select the latest captured profile and review its request summary.

The route can show a useful result only when profiler collection is enabled and at least one request has been recorded. A development toolbar may also provide a link from a rendered response to the associated profile. A debug toolbar is a development interface attached to or associated with a response; it commonly links to profiler details for that request.

Understanding a captured profile

Request token

Each captured profile normally has a request token, a unique identifier used to distinguish one recorded request from another. The token can help you confirm that you opened the intended request and can be useful when searching profiler history or correlating a profile with logs.

Do not assume that the newest profile is always the request you intended to inspect. Browsers can make background requests for assets, polling, analytics, or health checks. Inspect the URL, method, timestamp, and token before drawing conclusions.

Common request details

The available information depends on the enabled collectors and the profiler implementation. A profile collector is a component that gathers one category of diagnostic data, such as logs, database queries, or timing information.

Profile area	What it helps diagnose	Typical details
Request summary	Whether the captured request is the one being investigated	Request token, method, URL, route, controller, timestamp, and environment
Response	How the application completed the request	HTTP status, response headers, response size, and redirect information
Timing and performance	Why a response is slow	Total duration, component timings, event time, template time, and external-service time
Memory	Whether the request uses an unexpectedly large amount of memory	Memory usage or peak memory measurements
Database activity	Slow, repeated, or excessive database work	Queries, query duration, parameters where supported, and query count
Logs	Events and warnings produced during the request	Log messages, severity, timestamps, and context
Exceptions	Why a request failed	Exception class, message, stack trace, and related request context
Request context	How inputs and execution context affected the result	Route parameters, request parameters, headers, session details, and configuration-related context where collected

Practical examples

Inspect a recent page load

Load the page in the development application.
Open the latest-request view.
Confirm that the URL, route, method, and request token match the page load.
Review the request summary, response status, duration, and memory use.
Open database, log, or template-related sections if the summary suggests a problem.

Investigate a slow response

Reproduce the slow request in a safe development environment.
Open the latest profile immediately afterward.
Compare total duration with database, template, event, and external-service timing information.
Look for slow queries, repeated work, unusually long events, or a slow dependency.
Repeat the test after a change and compare profiles rather than relying only on a single measurement.

Investigate an error response

Reproduce the failing request in a safe development environment.
Open the corresponding latest profile.
Confirm the response status and request token.
Review exception details, stack information, logs, and request context.
Use the profile together with application logs to identify the failing operation and its inputs.

Development-only usage and security

Profiler pages should normally be available only on a local machine or inside a protected development environment. Profiler data is intentionally detailed and may expose request parameters, headers, session or context values, database activity, application configuration details, file paths, stack traces, and other diagnostic information.

Do not expose profiler routes publicly unless access is deliberately controlled and the information is appropriate for that environment. Protect development tooling with environment restrictions and access control, and avoid sharing captured profiles that contain secrets or personal data.

Before investigating a production issue, prefer the application's approved logging and observability tools. If profiling must be enabled in another environment, assess data exposure, retention, authentication, and network access first.

Troubleshooting

No latest profile is available

Possible cause: No request has been captured yet. Resolution: Make a request to the application and try again.
Possible cause: Profiler collection is disabled. Resolution: Verify that profiling is enabled for the active development environment.
Possible cause: The profiler storage location is unavailable or has been cleared. Resolution: Confirm that the storage location is writable and that captured profiles are retained.
Possible cause: The current environment does not expose profiler routes. Resolution: Check the route and access-control configuration for development tooling.

The latest entry is not the request being investigated

Background browser requests, asset requests, or health checks may have created newer profiles.
Multiple users or processes may share the same profiler storage.
Use the profiler history or search interface to locate the request by URL, status, method, time, or request token.
Reproduce the request and inspect the latest profile promptly.
Filter or isolate development traffic where the profiler supports it.

Profiler information is incomplete

Specific collectors may be disabled. Check which collectors are enabled, including timing, logs, database, and exception collectors.
The request may have terminated before all data could be recorded. Review application logs alongside the profile.
Storage retention may have removed older details. Adjust development profiler retention only when appropriate and avoid retaining sensitive data longer than necessary.

Exam-relevant notes

The latest profile means the most recently stored request record, not necessarily the request you intended to inspect.
A request token uniquely identifies a captured request profile.
Profiler collection must be enabled, and at least one request must be recorded, before a latest profile can be opened.
Common profile data includes route, controller, response status, duration, memory use, logs, database activity, and exceptions.
Profiler pages are development diagnostics and can disclose sensitive request and configuration information, so they should be protected from public access.