Class LogExclusion (1.15.1)

Specifies a set of log entries that are not to be stored in Logging. If your GCP resource receives a large volume of logs, you can use exclusions to reduce your chargeable logs. Exclusions are processed after log sinks, so you can export log entries before they are excluded. Note that organization-level and folder-level exclusions don't apply to child resources, and that you can't exclude audit log entries.

.. attribute:: name

Required. A client-assigned identifier, such as "load- balancer-exclusion". Identifiers are limited to 100 characters and can include only letters, digits, underscores, hyphens, and periods. First character has to be alphanumeric.

Required. An advanced logs filter </logging/docs/view/advanced-queries> that matches the log entries to be excluded. By using the sample function </logging/docs/view/advanced-queries#sample>, you can exclude less than 100% of the matching log entries. For example, the following query matches 99% of low-severity log entries from Google Cloud Storage buckets: "resource.type=gcs_bucket severity<ERROR sample(insertId, 0.99)"

Output only. The creation timestamp of the exclusion. This field may not be present for older exclusions.

Inheritance

builtins.object > google.protobuf.pyext._message.CMessage > builtins.object > google.protobuf.message.Message > LogExclusion