Sentry Create Project Rule For Alerts

Descriptive name for the alert rule.

Owner ID (e.g., 'team:ID', 'user:ID').

List of action objects executed when conditions (and filters) are met. Each object must specify an ID (action type) and parameters. See examples for required JSON structures: **Send a notification to Suggested Assignees** - `fallthroughType` - Who the notification should be sent…

Optional list of filter objects for additional criteria after conditions are met. Each object must specify an ID (filter type) and parameters. See examples for required JSON structures: **The issue is `comparison_type` than `value` `time`** - `comparison_type` - One of `older` o…

Action performance interval in minutes (5-43200) once conditions are met.

List of condition objects defining rule triggers. Each object must specify an ID (condition type) and parameters. See examples for required JSON structures: **A new issue is created** json { "id": "sentry.rules.conditions.first_seen_event.FirstSeenEventCondition" } **The issue c…

Logic for condition evaluation: 'all' (all conditions must match) or 'any' (any condition can match). NOTE: 'none' is deprecated and no longer supported.

Sentry environment name for event filtering (e.g., 'production'). If omitted, applies to all environments.

Logic for filter evaluation ('all', 'any', 'none') for action execution. Required if 'filters' are specified.

Unique identifier (ID or slug) of the Sentry project for the rule.

Unique identifier (ID or slug) of the Sentry organization.