Skip to content

MonitoringAlertPolicy CRD - request to support unsetting the severity #4631

Open
@csapuntz

Description

@csapuntz

Checklist

  • I did not find a related open enhancement request.
  • I understand that enhancement requests filed in the GitHub repository are by default low priority.
  • If this request is time-sensitive, I have submitted a corresponding issue with GCP support.

Describe the feature or resource

The CRD currently states only "CRITICAL", "ERROR", and "WARNING" are supported for MonitoringAlertPolicy severity. We have an INFO level in our alert description which we map to unset severity in Google Cloud. However, there is no documented to way to unset the severity using the CRD.

              severity:
                description: |-
                  The severity of an alert policy indicates how important
                  incidents generated by that policy are. The severity level will be displayed on
                  the Incident detail page and in notifications. Possible values: ["CRITICAL", "ERROR", "WARNING"].
                type: string

In my testing, specifying severity as empty string "" will unset severity on the corresponding Alert Policy on Config Connector 1.130.2, but this is an undocumented behavior. I'm requesting that a documented behavior for unsetting the severity be created.

Additional information

No response

Importance

Nice-to-have. Not urgent.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions