Description
DebugProbe currently exposes its dashboard UI through the default /debug route.
While the default route works well for most applications, users do not currently have a simple way to customize the dashboard endpoint when route conflicts, organizational standards, or security requirements exist.
DebugProbe should provide a configuration option that allows users to customize the dashboard route while preserving the existing default behavior.
Current Behavior
The dashboard UI is always available at:
There is currently no dedicated option to change the dashboard route.
Expected Behavior
Users should be able to configure a custom dashboard route through DebugProbe options.
The default route should remain /debug to preserve existing behavior.
Example:
builder.Services.AddDebugProbe(options =>
{
options.RoutePrefix = "/debugdashboard";
});
Result
After this change:
- users can customize the dashboard route to match their application requirements
- route conflicts with existing endpoints can be avoided
- DebugProbe becomes more flexible for different deployment environments
- existing applications continue to work without any changes because
/debug remains the default route
Description
DebugProbe currently exposes its dashboard UI through the default
/debugroute.While the default route works well for most applications, users do not currently have a simple way to customize the dashboard endpoint when route conflicts, organizational standards, or security requirements exist.
DebugProbe should provide a configuration option that allows users to customize the dashboard route while preserving the existing default behavior.
Current Behavior
The dashboard UI is always available at:
There is currently no dedicated option to change the dashboard route.
Expected Behavior
Users should be able to configure a custom dashboard route through DebugProbe options.
The default route should remain
/debugto preserve existing behavior.Example:
Result
After this change:
/debugremains the default route