Skip to main content
Insights analyzes traces, and Chat (formerly Polly) helps you work with LangSmith data. Both are part of the base installation and are enabled by default in Helm chart version 0.15.1 or later. They do not require any additional features, such as Sandboxes, Fleet, or LangSmith Deployment.
For charts before 0.15.1, Insights and Chat are not enabled by default. Use the configuration supported by your pinned chart, or upgrade before following this guide.
Each feature requires its own Fernet encryption key and model access. If you followed the Kubernetes installation guide, you already set the keys in langsmith_config.yaml. Continue with Configure model access.

​
Set the encryption keys

To generate one key per feature, see Keys and secrets. Do not commit encryption keys to version control. Provide the keys in one of two ways:
  • Inline: Set insights.encryptionKey and polly.encryptionKey in langsmith_config.yaml, as in the minimum configuration.
  • Existing Secret: Add insights_encryption_key and polly_encryption_key to your existing LangSmith app Secret. Reference it through config.existingSecretName.
Apply your Helm configuration:

​
Configure model access

Insights and Chat call models through your provider credentials and model configurations. For keyless Vertex AI on GKE, see Configure GKE workload identity.

​
Disable Insights or Chat

Disable either feature when your installation does not need it. Set the corresponding top-level flag to false in your langsmith_config.yaml. You do not need an encryption key for a disabled feature.
Apply your Helm configuration:
Disabling Insights does not disable Engine or remove their shared deployment when engine.enabled is true.

​
Upgrade existing configurations

This section applies only to installations upgrading from earlier chart versions. Current charts reject the legacy config.insights, config.polly, and backend.agentBootstrap settings. Remove these settings rather than setting them to false. Contact technical support through the Support Portal for legacy deployment migration guidance. Starting with chart 0.16.0, Insights and Engine share the langsmith-insights-engine image and deployment. This does not enable Engine. Move legacy insights.apiServer, insights.queue, insights.postgres, insights.redis, and insights.namePrefix values to engineInsightsAgent. Keep insights.enabled and insights.encryptionKey under insights. If you pin the retired langsmith-clio image, remove or update that pin before upgrading. For private registries, mirror langsmith-insights-engine. See Mirroring images. For the general upgrade procedure, see Upgrade an installation.

​
See also

Connect these docs to your agent of choice via MCP for real-time answers.
Edit this page on GitHub or file an issue.