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
- Data model and import order
The tables behind Container & K8s Management
Container & K8s Management ships with 12 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 12
- Features
- 7
- Change it
- Add fields and tables in Proto
How the model is organised
Environment and workload:
Clusters and deployment observations hold named environments, owners and dated workload replica readings.
Service response:
Services, Assets, Incidents and incident updates connect affected service context to an assigned responder and attributed findings.
Longer work:
Problems hold root cause investigation; Changes hold risk, planned window, approval state and outcome; service requests hold submitted work and completion.
Identity and intake:
Users and People supply named owners and authors. Integration receipts track external event identifiers and receipt outcomes.
Every table, by feature
- Clusters
Clusters for container and Kubernetes operations
Linked to People - Deployment observations
Deployment Observations for container and Kubernetes operations
Linked to Clusters - People
People for container and Kubernetes operations
Linked to Users
- Deployment observations
Deployment Observations for container and Kubernetes operations
Linked to Clusters - Clusters
Clusters for container and Kubernetes operations
Linked to People - Incidents
Incidents for container and Kubernetes operations
Linked to Services, Assets, People - Incident updates
Incident Updates for container and Kubernetes operations
Linked to Incidents, People
- Incidents
Incidents for container and Kubernetes operations
Linked to Services, Assets, People - Incident updates
Incident Updates for container and Kubernetes operations
Linked to Incidents, People - Services
Services for container and Kubernetes operations
Linked to People - Assets
Assets for container and Kubernetes operations
Linked to Services - People
People for container and Kubernetes operations
Linked to Users - Deployment observations
Deployment Observations for container and Kubernetes operations
Linked to Clusters
- Changes
Changes for container and Kubernetes operations
Linked to Services - Services
Services for container and Kubernetes operations
Linked to People - Incidents
Incidents for container and Kubernetes operations
Linked to Services, Assets, People - Problems
Problems for container and Kubernetes operations
Linked to Services, People - Deployment observations
Deployment Observations for container and Kubernetes operations
Linked to Clusters
- Problems
Problems for container and Kubernetes operations
Linked to Services, People - Services
Services for container and Kubernetes operations
Linked to People - Incidents
Incidents for container and Kubernetes operations
Linked to Services, Assets, People - Incident updates
Incident Updates for container and Kubernetes operations
Linked to Incidents, People - Changes
Changes for container and Kubernetes operations
Linked to Services - Deployment observations
Deployment Observations for container and Kubernetes operations
Linked to Clusters
- Service requests
Service Requests for container and Kubernetes operations
Linked to People, Services - People
People for container and Kubernetes operations
Linked to Users - Services
Services for container and Kubernetes operations
Linked to People - Changes
Changes for container and Kubernetes operations
Linked to Services
- Services
Services for container and Kubernetes operations
Linked to People - Assets
Assets for container and Kubernetes operations
Linked to Services - Integration receipts
Integration Receipts for container and Kubernetes operations
- People
People for container and Kubernetes operations
Linked to Users - Users
Users
Linked to Users
Keys and references
Use stable cluster names and external event identifiers. Link an observation to its actual cluster; link an incident to its service, asset and assigned person. Keep the author on each incident update and the owner on each problem. The service reference is the common context for incidents, changes, problems, requests and assets.
Integration receipts retain provider identifiers and payload hashes for reconciliation. A receipt’s status is an intake outcome. It is separate from a change or incident outcome. Map People to Users before testing ownership and current-user views.
Migration order
- Load Users and People, then check their user references.
- Load Services and owners, followed by Assets linked to their services.
- Load Clusters with their owners, then deployment observations tied to the correct cluster.
- Load active Incidents and incident updates, then Problems, Changes and service requests with their references.
- Reconcile integration receipts against their source events and test representative status and ownership cases.
Set up Container & K8s Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.