Skip to main content
POST
/
api
/
v1
/
postmortems
/
{name}
/
feedback
Developer Feedback
curl --request POST \
  --url https://api.example.com/api/v1/postmortems/{name}/feedback \
  --header 'Content-Type: application/json' \
  --data '
{
  "providedBy": "<string>",
  "remediationAccuracy": 123,
  "overrideRootCause": "<string>",
  "comments": "<string>"
}
'
{
  "apiVersion": "v1",
  "kind": "PostMortem",
  "resourceMeta": {
    "name": "PM-20260319-001",
    "namespace": "production"
  },
  "status": {
    "state": "InReview",
    "feedback": {
      "overrideRootCause": "Leak caused by uncancelled goroutine in webhook handler, not by the response body",
      "remediationAccuracy": 4,
      "comments": "Good analysis. Consider suggesting AdjustResources before restart next time.",
      "providedBy": "sre@company.com",
      "providedAt": "2026-03-19T09:00:00Z"
    }
  }
}
​
name
string
required
Unique postmortem name (e.g., PM-20260319-001)
​
namespace
string
default:"default"
Kubernetes namespace
​
providedBy
string
required
Identifier of who is providing feedback (e.g., email or username). Maximum 253 characters.
​
remediationAccuracy
integer
required
Rating from 1 to 5 for the AI’s automatic remediation accuracy
  • 1 — Completely wrong, did not resolve anything
  • 2 — Partially correct, but with significant issues
  • 3 — Reasonable, resolved but required manual adjustments
  • 4 — Good, resolved with minor observations
  • 5 — Excellent, perfect remediation
​
overrideRootCause
string
Human-provided root cause (overrides AI analysis). Leave empty to keep the original root cause. Maximum 4096 characters.
​
comments
string
Additional comments about the postmortem or remediation. Maximum 4096 characters.

​
When to Use

After reviewing a postmortem in the Dashboard, the developer can provide structured feedback:
  1. Rate the remediation — score from 1 to 5 the accuracy of the automated action
  2. Correct root cause — override the root cause if the AI was wrong or imprecise
  3. Add context — comments with information the AI did not have access to
Feedback is displayed directly in the Dashboard and persisted in the PostMortem CR status.
Requires operator role or higher. The providedBy field is mandatory for traceability. Submitting feedback again overwrites the previous feedback. On concurrent modification, the API returns 409 Conflict.
{
  "apiVersion": "v1",
  "kind": "PostMortem",
  "resourceMeta": {
    "name": "PM-20260319-001",
    "namespace": "production"
  },
  "status": {
    "state": "InReview",
    "feedback": {
      "overrideRootCause": "Leak caused by uncancelled goroutine in webhook handler, not by the response body",
      "remediationAccuracy": 4,
      "comments": "Good analysis. Consider suggesting AdjustResources before restart next time.",
      "providedBy": "sre@company.com",
      "providedAt": "2026-03-19T09:00:00Z"
    }
  }
}

{
  "apiVersion": "v1",
  "kind": "Error",
  "error": "remediationAccuracy must be between 1 and 5",
  "code": 400
}

{
  "apiVersion": "v1",
  "kind": "Error",
  "error": "postmortem was modified concurrently, please retry",
  "code": 409
}