Deploy trace analysis
Deploy the trace analyzer in your infrastructure to analyze agent sessions using your model provider. Session data lives in your PostgreSQL database and trace bucket. The Promptless Dashboard shows findings, remediations, analyzer status, and agent instruction health.
Installation has two stages: prepare your cloud infrastructure, then bootstrap PIG with Helm. The analyzer and its update controller, the supervisor, follow stable releases automatically. You can pause updates or pin a release.
Choose an installation path
Section titled “Choose an installation path”The cloud guides create dedicated PIG infrastructure in your existing network. They finish with the same Helm installation. Use manual Helm management if your team needs to apply every application upgrade itself.
Before you begin
Section titled “Before you begin”| Requirement | What to prepare |
|---|---|
| Kubernetes | An existing cluster, kubectl, Helm 3 or later, and permission to install the PIG custom resource definition and scoped RBAC. |
| PostgreSQL | A dedicated database, schema-owner credentials, TLS, backups, and private connectivity from the analyzer and migration Jobs. |
| Trace bucket | Private S3, Azure Blob Storage, or Google Cloud Storage with a dedicated prefix and a workload identity that can read and write objects. |
| HTTPS endpoint | A hostname, certificate, and ingress reachable from enrolled hosts. Every proxy must accept encoded uploads of at least 10 MiB. |
| Promptless registration | Your deployment ID, runtime URL, and installation token. Keep this identity stable across upgrades and recovery. |
| Instruction Hub | A GitHub repository with a readable main branch, its canonical URL and numeric ID, and read credentials if private. |
| Model access | A supported Responses API endpoint, model name, authorization, and enough quota for analysis. |
Select infrastructure regions to meet your data residency requirements. The model provider can be in a different cloud; choose it independently from your trace bucket. See model providers for supported endpoints.
Assign ownership
Section titled “Assign ownership”| Owner | Maintains |
|---|---|
| Your platform team, using Terraform | Cloud databases and their capacity, trace storage, networking, IAM, encryption keys, backup and retention policies. |
| Your Kubernetes configuration and secret manager | Namespaces, analyzer workload identity, desired PIGDeployment configuration, secret delivery, and certificates. |
| PIG | Analyzer and supervisor application releases, generated workloads, and database schema migrations within the installed permissions. |
Keep the one-time Helm bootstrap outside Terraform’s ongoing reconciliation. After bootstrap, PIG updates its own workloads. A second controller restoring the original chart would undo those updates. GitOps ownership explains the handoff.
A release that needs more infrastructure capacity or access reports a blocked update. Your team reviews and applies the Terraform change; PIG resumes when its live checks and any required release-specific confirmations pass. PIG does not resize cloud databases or change IAM and backup policies.
Plan for production
Section titled “Plan for production”Before expanding beyond a pilot, measure compute and capacity, configure coordinated database and object-storage recovery, and confirm network access.
Finish installation by verifying a complete session. A ready pod or successful health check alone does not verify trace analysis.