Resultado da Busca
8 de dez. de 2021 · Hi, At the end of a meal with a friend at a restaurant, when you have agreed to split the bill, you can say to the server, "Separate checks, please."
Translation of "separate checks" in Portuguese. contas separadas. cheques separados. Well, we could get separate checks. Bem, podemos pedir contas separadas. You're doing more damage to the team than when we tried to get separate checks at Macaroni Grill.
Muitos exemplos de traduções com "separate check" – Dicionário português-inglês e busca em milhões de traduções.
High quality example sentences with “separate checks” in context from reliable sources - Ludwig is the linguistic search engine that helps you to write better in English.
- Overview
- Basic health probe
- Create health checks
- Register health check services
- Use Health Checks Routing
- Health check options
- Database probe
- Entity Framework Core DbContext probe
- Separate readiness and liveness probes
- Distribute a health check library
By Glenn Condron and Juergen Gutsch
ASP.NET Core offers Health Checks Middleware and libraries for reporting the health of app infrastructure components.
Health checks are exposed by an app as HTTP endpoints. Health check endpoints can be configured for various real-time monitoring scenarios:
•Health probes can be used by container orchestrators and load balancers to check an app's status. For example, a container orchestrator may respond to a failing health check by halting a rolling deployment or restarting a container. A load balancer might react to an unhealthy app by routing traffic away from the failing instance to a healthy instance.
•Use of memory, disk, and other physical server resources can be monitored for healthy status.
•Health checks can test an app's dependencies, such as databases and external service endpoints, to confirm availability and normal functioning.
For many apps, a basic health probe configuration that reports the app's availability to process requests (liveness) is sufficient to discover the status of the app.
The basic configuration registers health check services and calls the Health Checks Middleware to respond at a URL endpoint with a health response. By default, no specific health checks are registered to test any particular dependency or subsystem. The app is considered healthy if it can respond at the health endpoint URL. The default response writer writes HealthStatus as a plaintext response to the client. The HealthStatus is HealthStatus.Healthy, HealthStatus.Degraded, or HealthStatus.Unhealthy.
Register health check services with AddHealthChecks in Program.cs. Create a health check endpoint by calling MapHealthChecks.
The following example creates a health check endpoint at /healthz:
Health checks are created by implementing the IHealthCheck interface. The CheckHealthAsync method returns a HealthCheckResult that indicates the health as Healthy, Degraded, or Unhealthy. The result is written as a plaintext response with a configurable status code. Configuration is described in the Health check options section. HealthCheckResult can also return optional key-value pairs.
The following example demonstrates the layout of a health check:
The health check's logic is placed in the CheckHealthAsync method. The preceding example sets a dummy variable, isHealthy, to true. If the value of isHealthy is set to false, the HealthCheckRegistration.FailureStatus status is returned.
If CheckHealthAsync throws an exception during the check, a new HealthReportEntry is returned with its HealthReportEntry.Status set to the FailureStatus. This status is defined by AddCheck (see the Register health check services section) and includes the inner exception that caused the check failure. The Description is set to the exception's message.
To register a health check service, call AddCheck in Program.cs:
The AddCheck overload shown in the following example sets the failure status (HealthStatus) to report when the health check reports a failure. If the failure status is set to null (default), HealthStatus.Unhealthy is reported. This overload is a useful scenario for library authors, where the failure status indicated by the library is enforced by the app when a health check failure occurs if the health check implementation honors the setting.
Tags can be used to filter health checks. Tags are described in the Filter health checks section.
AddCheck can also execute a lambda function. In the following example, the health check always returns a healthy result:
Call AddTypeActivatedCheck to pass arguments to a health check implementation. In the following example, a type-activated health check accepts an integer and a string in its constructor:
To register the preceding health check, call AddTypeActivatedCheck with the integer and string passed as arguments:
Require host
Call RequireHost to specify one or more permitted hosts for the health check endpoint. Hosts should be Unicode rather than punycode and may include a port. If a collection isn't supplied, any host is accepted: To restrict the health check endpoint to respond only on a specific port, specify a port in the call to RequireHost. This approach is typically used in a container environment to expose a port for monitoring services: Warning API that relies on the Host header, such as HttpRequest.Host and RequireHost, are subject to potential spoofing by clients. To prevent host and port spoofing, use one of the following approaches: •Use HttpContext.Connection (ConnectionInfo.LocalPort) where the ports are checked. •Employ Host filtering.
Require authorization
Call RequireAuthorization to run Authorization Middleware on the health check request endpoint. A RequireAuthorization overload accepts one or more authorization policies. If a policy isn't provided, the default authorization policy is used:
Enable Cross-Origin Requests (CORS)
Although running health checks manually from a browser isn't a common scenario, CORS Middleware can be enabled by calling RequireCors on the health checks endpoints. The RequireCors overload accepts a CORS policy builder delegate (CorsPolicyBuilder) or a policy name. For more information, see Enable Cross-Origin Requests (CORS) in ASP.NET Core.
Filter health checks
By default, the Health Checks Middleware runs all registered health checks. To run a subset of health checks, provide a function that returns a boolean to the Predicate option. The following example filters the health checks so that only those tagged with sample run:
Customize the HTTP status code
Use ResultStatusCodes to customize the mapping of health status to HTTP status codes. The following StatusCodes assignments are the default values used by the middleware. Change the status code values to meet your requirements:
Suppress cache headers
AllowCachingResponses controls whether the Health Checks Middleware adds HTTP headers to a probe response to prevent response caching. If the value is false (default), the middleware sets or overrides the Cache-Control, Expires, and Pragma headers to prevent response caching. If the value is true, the middleware doesn't modify the cache headers of the response:
A health check can specify a database query to run as a boolean test to indicate if the database is responding normally.
AspNetCore.Diagnostics.HealthChecks, a health check library for ASP.NET Core apps, includes a health check that runs against a SQL Server database. AspNetCore.Diagnostics.HealthChecks executes a SELECT 1 query against the database to confirm the connection to the database is healthy.
Warning
When checking a database connection with a query, choose a query that returns quickly. The query approach runs the risk of overloading the database and degrading its performance. In most cases, running a test query isn't necessary. Merely making a successful connection to the database is sufficient. If you find it necessary to run a query, choose a simple SELECT query, such as SELECT 1.
The DbContext check confirms that the app can communicate with the database configured for an EF Core DbContext. The DbContext check is supported in apps that:
•Use Entity Framework (EF) Core.
•Include a package reference to the Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore NuGet package.
AddDbContextCheck registers a health check for a DbContext. The DbContext is supplied to the method as the TContext. An overload is available to configure the failure status, tags, and a custom test query.
By default:
•The DbContextHealthCheck calls EF Core's CanConnectAsync method. You can customize what operation is run when checking health using AddDbContextCheck method overloads.
In some hosting scenarios, a pair of health checks is used to distinguish two app states:
•Readiness indicates if the app is running normally but isn't ready to receive requests.
•Liveness indicates if an app has crashed and must be restarted.
Consider the following example: An app must download a large configuration file before it's ready to process requests. We don't want the app to be restarted if the initial download fails because the app can retry downloading the file several times. We use a liveness probe to describe the liveness of the process, no other checks are run. We also want to prevent requests from being sent to the app before the configuration file download has succeeded. We use a readiness probe to indicate a "not ready" state until the download succeeds and the app is ready to receive requests.
The following background task simulates a startup process that takes roughly 15 seconds. Once it completes, the task sets the StartupHealthCheck.StartupCompleted property to true:
The StartupHealthCheck reports the completion of the long-running startup task and exposes the StartupCompleted property that gets set by the background service:
To distribute a health check as a library:
1.Write a health check that implements the IHealthCheck interface as a standalone class. The class can rely on dependency injection (DI), type activation, and named options to access configuration data.
2.Write an extension method with parameters that the consuming app calls in its Program.cs method. Consider the following example health check, which accepts arg1 and arg2 as constructor parameters:
The preceding signature indicates that the health check requires custom data to process the health check probe logic. The data is provided to the delegate used to create the health check instance when the health check is registered with an extension method. In the following example, the caller specifies:
•arg1: An integer data point for the health check.
•arg2: A string argument for the health check.
Veja tudo sobre Separate Checks (2011): onde assistir online, dublado e legendado, streaming, trailers, elenco, sinopse, recomendações...
Check 'separate check' translations into Portuguese. Look through examples of separate check translation in sentences, listen to pronunciation and learn grammar.
