Skip to main content
Early Preview: Rootly Private Agent is under active development and available only to approved customers. Features, configuration, limits, and APIs may change before general availability. Confirm the approved agent and backend versions with your Rootly representative before production use.
Use this page as the canonical numeric reference for the early-access Private Agent. Setup guides link here rather than repeating policy defaults and ceilings. Confirm compatibility with your Rootly representative when upgrading either the agent or backend.

​
Shared Runtime and AI Context

Local provider limits and AI context limits are independent. A response that fits an adapter’s local limit can still exceed the AI context limit. Request deadlines and cancellation also bound execution and result delivery.

​
Kubernetes

The Kubernetes guide explains targeted log arguments, truncation, permissions, and resource sizing. These bounds limit agent-side handling, not Kubernetes API server workload.

​
Prometheus

Set these keys under an instance’s policy mapping to tighten its limits. Omitted or zero local policy values select defaults. Positive values may tighten the bounds. Explicit tool limits and timeouts must be positive and cannot exceed local policy. The shared runtime concurrency bound also applies. Metric-name and label-value discovery use GET-only upstream endpoints. Their aggregate request-target limit counts all selectors, percent-encoding, other parameters, and the configured endpoint path; individually valid arguments may need narrowing to fit. Metadata GETs share this bound. Query and label-name tools use form-encoded POST requests.

​
Health Probes

Prometheus health observations are cached for 15 seconds. Each instance has one serialized query probe with a timeout of at most 2 seconds, independent of user-request admission, and one reserved HTTP connection. The runtime permits at most 17 concurrent provider probes so the supported Prometheus instances plus Kubernetes fit in one probe wave within the 5-second readiness budget. User saturation alone does not mark an upstream unhealthy. A failed upstream probe can still affect readiness. See the Prometheus guide for status behavior and compatibility.

​
Maintaining This Reference

Update this reference alongside changes to agent policy defaults, tool input validation, runtime health budgets, or Rootly’s schema and AI-context guards. Keep setup examples illustrative, link to these tables for limits, and validate the examples against matching early-access builds. These limits are not a production load-capacity guarantee.