These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Container & K8s Management
- Process
- Observation to incident
Observation to incident
Turn a workload readiness finding into an owned service investigation.
Step by step
-
Record cluster Platform Operator
Platform Operator identifies the environment, provider, version and accountable owner.
- Establish environment and owner
- Updates Clusters, People
-
Observe workload Platform Operator
The operator records the namespace, workload, observation time and desired and ready replicas against that cluster.
- Preserve dated replica figures
- Updates Deployment observations, Clusters
-
Open incident Incident Responder
Incident Responder assesses service impact, then opens an incident with a service, asset, summary and priority.
- Create service work
- Updates Incidents, Services, Assets
-
Acknowledge incident Incident Responder
The responder assigns the person taking responsibility and records the acknowledgment time.
- Name the assigned person
- Updates Incidents, People
-
Investigate incident Incident Responder
The assigned person adds dated, attributed updates as the condition is checked.
- Keep attributed findings
- Updates Incident updates, Incidents
-
Close incident Incident Responder
After a recorded resolution, the responder closes the issue with the service outcome clear.
- Record outcome and closing state
- Updates Incidents
Who does what
Roles and permissions- Platform Operator
- Records the cluster and workload state; Incident Responder owns the incident; Service Owner checks service context.
Set up Container & K8s Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.