Questions, answered

Click Get started, then use Proto to configure Container & K8s Management for your business. Pilot a named cluster, one service and a workload whose desired and ready replicas your team can check.

It identifies a cluster, namespace, workload, observation time and desired and ready replica figures. Use it with the service and incident records when investigating impact.

Yes. Each cluster has an environment and named owner. Agree on environment labels before loading observations so similar workload names remain distinguishable.

Assign the incident to a person and record the acknowledgment time. Keep later findings as dated updates with their authors.

A Change Approver reviews the service, risk, scheduled start and end, and rollback plan before recording an approval or rejection. The operator records implementation and its result separately.

A request captures the desired service work and its approval. Production intervention can have its own change record with risk, window, rollback plan and review decision.

Agree on the source for cluster and workload data during implementation. A Kubernetes API or telemetry connection can supply readings once configured and reconciled with the named records.

Integration receipts retain provider and external event identifiers, a received time, payload hash and intake outcome. Review rejected and failed receipts against the provider source.

Use a problem record for the service, with a named owner, root cause findings and a status that distinguishes investigation from known error and resolution.

Manual use follows the platform pricing policy. Imports, integrations and agent activity use the published metering rules; implementation scope is agreed separately.