Aident Loadout を通じて PagerDuty Tools の Pagerduty Create Incident Record を使用します。実行前に入力、出力、設定、料金、リスクを確認できます。
Creates a new incident in PagerDuty with specified details and assignments. Use this endpoint when an event requires immediate attention from on-call teams. It supports comprehensive incident documentation, including priority, urgency, and conference bridge information. The 'inc…
FromstringEmail address of a valid user associated with the PagerDuty account. This is REQUIRED for incident creation. The user must have permissions to create incidents on the specified service. You can use the GET /users/me endpoint to get the current user's email, or provide any valid…
incident__typestringSpecifies the type of object being created. Always set to "incident" for incident creation. This field helps ensure API consistency and proper object handling.
incident__titlestringA clear, descriptive title for the incident that helps responders quickly understand the issue. Best Practice Format: "<System/Service> - <Problem> - <Impact>" Examples: - "Production Database - CPU Usage 95% - Customer Queries Delayed" - "Payment API - 500 Error Rate >5% - Orde…
incident__urgencystringDetermines the immediacy of notifications and escalations. Options: - high: Immediate notifications, aggressive escalation - low: Respect service"s notification rules, standard escalation Choose based on: - Business impact - Time sensitivity - Service criticality - Customer impa…
incident__body__typestringSpecifies the type of body content
incident__assignmentsarrayList of users to assign to the incident. Maximum 10 assignees allowed. Important Notes: - Cannot be used with escalation_policy - Users must have access to the service - Assignments override default escalation - Order matters for primary/secondary
incident__service__idstringUnique identifier for the PagerDuty service. Found in service settings or via API. Example: "PSVC123"
incident__priority__idstringUnique identifier for the priority level. Example: "PRIO123"
incident__body__detailsstringComprehensive incident details in structured format. Recommended Structure: ``` CURRENT STATUS: [Brief description of current situation] IMPACT: - Business Impact: [Description] - User Impact: [Number of affected users/systems] - Revenue Impact: [If applicable] ACTIONS TAKEN: 1.…
incident__incident__keystringUnique identifier for deduplicating incidents within a service. Best Practice Format: "<source>-<type>-<identifier>-<timestamp>" Examples: - "datadog-cpu-alert-prod-db1-1640995200" - "cloudwatch-memory-warning-cache-1640995200" - "synthetic-api-failure-payments-1640995200" Notes…
incident__service__typestringObject type identifier. Always "service_reference" for service objects.
incident__priority__typestringObject type for priority reference
data必須Data from the action execution
errorstringError if any occurred during the execution of the action
successful必須booleanWhether or not the action execution was successful or not
API キー接続。リスクレベル 2/5。
無料 Action
この Action を明示的に参照する公開 Skills はまだありません。