FindingLimits(mapping=None, *, ignore_unknown_fields=False, **kwargs)Configuration to control the number of findings returned for inspection. This is not used for de-identification or data profiling.
When redacting sensitive data from images, finding limits don't
apply. They can cause unexpected or inconsistent results, where only
some data is redacted. Don't include finding limits in
RedactImage][google.privacy.dlp.v2.DlpService.RedactImage]
requests. Otherwise, Cloud DLP returns an error.
Attributes
| Name | Description |
| max_findings_per_item |
int
Max number of findings that will be returned for each item scanned. When set within ``InspectJobConfig``, the maximum returned is 2000 regardless if this is set higher. When set within ``InspectContentRequest``, this field is ignored. |
| max_findings_per_request |
int
Max number of findings that will be returned per request/job. When set within ``InspectContentRequest``, the maximum returned is 2000 regardless if this is set higher. |
| max_findings_per_info_type |
Sequence[google.cloud.dlp_v2.types.InspectConfig.FindingLimits.InfoTypeLimit]
Configuration of findings limit given for specified infoTypes. |
Inheritance
builtins.object > proto.message.Message > FindingLimitsClasses
InfoTypeLimit
InfoTypeLimit(mapping=None, *, ignore_unknown_fields=False, **kwargs)Max findings configuration per infoType, per content item or long running DlpJob.