package google.rpc

Get desktop application:
View/edit binary Protocol Buffers messages

The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors).

Used in: cel.expr.ErrorSet, cel.expr.conformance.CheckResponse, cel.expr.conformance.EvalResponse, cel.expr.conformance.ParseResponse, envoy.api.v2.DeltaDiscoveryRequest, envoy.api.v2.DiscoveryRequest, envoy.extensions.filters.http.rate_limit_quota.v3.RateLimitQuotaBucketSettings.DenyResponseSettings, envoy.service.auth.v2.CheckResponse, envoy.service.auth.v3.CheckResponse, envoy.service.discovery.v3.DeltaDiscoveryRequest, envoy.service.discovery.v3.DiscoveryRequest, envoy.service.discovery.v3.ResourceError, envoy.service.redis_auth.v3.RedisProxyExternalAuthResponse

• int32 code = 1

  The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

• string message = 2

  A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

• repeated protobuf.Any details = 3

  A list of messages that carry the error details. There is a common set of message types for APIs to use.