Skip to content
This repository has been archived by the owner on Dec 31, 2023. It is now read-only.

feat: Added support for auto-close configurations #253

Merged
merged 2 commits into from Nov 16, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 7 additions & 0 deletions google/cloud/monitoring_v3/types/alert.py
Expand Up @@ -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):
Expand All @@ -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,)
Expand Down
2 changes: 1 addition & 1 deletion google/cloud/monitoring_v3/types/common.py
Expand Up @@ -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
Expand Down