feat: Added support for auto-close configurations (#253)

- [ ] Regenerate this pull request now. PiperOrigin-RevId: 410253233 Source-Link: googleapis/googleapis@11e309d Source-Link: https://github.com/googleapis/googleapis-gen/commit/b4f3403a28cc99c9c7cf4cd2efca105f279a3b0f Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiYjRmMzQwM2EyOGNjOTljOWM3Y2Y0Y2QyZWZjYTEwNWYyNzlhM2IwZiJ9

Author: gcf-owl-bot[bot]

google/cloud/monitoring_v3/types/alert.py

@@ -527,6 +527,10 @@ class AlertStrategy(proto.Message):
 
  This limit is not implemented for alert policies that are
  not log-based.
+ auto_close (google.protobuf.duration_pb2.Duration):
+ If an alert policy that was active has no
+ data for this long, any open incidents will
+ close
  """
 
  class NotificationRateLimit(proto.Message):
@@ -547,6 +551,9 @@ class NotificationRateLimit(proto.Message):
  number=1,
  message="AlertPolicy.AlertStrategy.NotificationRateLimit",
  )
+ auto_close = proto.Field(
+ proto.MESSAGE, number=3, message=duration_pb2.Duration,
+ )
 
  name = proto.Field(proto.STRING, number=1,)
  display_name = proto.Field(proto.STRING, number=2,)

google/cloud/monitoring_v3/types/common.py

@@ -128,7 +128,7 @@ class TimeInterval(proto.Message):
  the end time of the previous interval.
 
  - For ``CUMULATIVE`` metrics, the start time and end time must
- specify a a non-zero interval, with subsequent points specifying
+ specify a non-zero interval, with subsequent points specifying
  the same start time and increasing end times, until an event
  resets the cumulative value to zero and sets a new start time for
  the following points. The new start time must be at least a