Alerting
Alerting
Defines the high-level intent for alerting rules and notification channels.
NOT YET IMPLEMENTED. Declared in the schema but currently inert: the engine registers the manifest in the dependency graph but no defaulter, validator, or executor reads its spec, so applying it provisions nothing. Intended future behavior: create and manage notification endpoints (e.g. Google Cloud Monitoring Notification Channels) and bind system-generated alerting policies to them, so observability targets are met automatically.
| Property | Type | Description |
|---|---|---|
| apiVersion | string | API schema version. Pins the manifest to a specific schema contract for backward-compatibility. Must be the constant lowops.manifests.v1. |
| kind | string | Resource kind discriminator. Identifies this document as an Alerting manifest so the engine routes it to the correct defaulter, validator, computer, and executor. Must be the constant Alerting. |
| metadata | map | Classification labels and graph linkage. Free-form key/value pairs used to classify the manifest. Certain reserved keys (e.g. name, project) are read by the engine to resolve this manifest's identity and its parent Project in the dependency graph. |
| spec | Spec | Desired alerting configuration. The authoritative, user-authored specification for this manifest. See Spec. |
Spec
User-provided alerting configuration.
NOT YET IMPLEMENTED. No consumer currently reads these fields. Intended future behavior: capture the notification-channel connectivity parameters and the toggle for whether alerting is active, serving as the inputs from which the engine provisions notification endpoints.
| Property | Type | Description |
|---|---|---|
| enabled | bool | Master switch for alerting. NOT YET IMPLEMENTED. Currently ignored by the engine. Intended future behavior: enable or disable alert routing for this scope. |
| description | string | Human-readable description of this alerting scope. Optional free text describing the intent of this configuration. Used only as context for operators and AI assistants reasoning about the manifest; it does not affect provisioning. |
| notifications | Notifications | Notification channel configuration. NOT YET IMPLEMENTED. Currently ignored by the engine. Intended future behavior: declare the channels to which platform alerts are routed. See Notifications. |
Notifications
Supported notification channels for routing alerts.
NOT YET IMPLEMENTED. Currently ignored by the engine. Intended future behavior: group the per-provider channel definitions (Slack today; PagerDuty and others in future) so the engine can conditionally provision each configured channel and forward its settings to the respective cloud API client.
| Property | Type | Description |
|---|---|---|
| slack | Slack | Slack channel configuration. NOT YET IMPLEMENTED. Currently ignored by the engine. See Slack. |
Slack
Slack notification channel definition.
NOT YET IMPLEMENTED. Currently ignored by the engine. Intended future behavior: describe the webhook endpoint and target channel for Slack-based alerts; the api_url would be validated and stored securely, while channel selects the routing target for the generated payload.
| Property | Type | Description |
|---|---|---|
| apiUrl | string | Slack incoming-webhook URL. The authenticated webhook endpoint targeting a specific Slack workspace. Constrained by buf.validate to be a syntactically valid URI. NOT YET IMPLEMENTED beyond this proto-level format check: no engine code consumes the value. |
| channel | string | Target Slack channel name. The Slack channel that alert payloads are routed to. NOT YET IMPLEMENTED: currently ignored by the engine. |