Skip to content

AddStandardResilienceHandler and healthchecks result in noisy logs with TestHost #6788

Open
@afscrome

Description

@afscrome

The default integration test template calls ConfigureHttpClientDefaults with AddStandardResilienceHandler

// appHost.Services.ConfigureHttpClientDefaults(clientBuilder =>
// {
// clientBuilder.AddStandardResilienceHandler();
// });

This however produces a lot of noise in 9.0 with the built in health checks this ends up producing a lot of number of distracting messages in the test host. e.g.

    info: Polly[3]
      Execution attempt. Source: '-standard//Standard-Retry', Operation Key: '', Result: '200', Handled: 'False', Attempt: '0', Execution Time: 1061.2159ms

Are these resiliency headers still a good recommendation for tests in 9.0? In 8.x before healthchecks & readiness, request resiliency was highly needed to make sure the apps had started up properly, but with 9.0's health check support is that still necessary? (Particularly if the sample tests replace WaitForResourceAsync with WaitForResourceHealthyAsync)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-app-testingIssues pertaining to the APIs in Aspire.Hosting.Testing

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions