Overview
Pipeline Intelligence is a suite of recommendations and AI-powered features that help you understand your telemetry data and automate your pipeline configuration.
Pipeline Intelligence
Pipeline Intelligence allows you to avoid manual configuration and complex OTTL syntax, and instead use natural language descriptions and intelligent data analysis to quickly build and optimize your pipelines.
With Pipeline Intelligence, you can:
Global Pipeline Intelligence
Global Pipeline Intelligence applies the same intelligence across all your pipeline data, continuously. Recommendations surface as notifications based on what's actually flowing through your pipelines, without you having to open a snapshot. Learn more about Global Pipeline Intelligence here.
AI Features
Pipeline Intelligence AI features are only available for Enterprise, Bindplane Enterprise (Google Edition), and Honeycomb licenses.
Some Pipeline Intelligence features use generative AI to analyze your data and produce configurations. Others, like the Chronicle Forwarder and Splunk Universal Forwarder migrator, use deterministic logic with no AI involved. The table below shows which features use AI.
How your data is used
When AI features are enabled, only the minimal input data needed to generate a response (such as log structure and content snippets) is sent for processing. We do not store AI inputs after processing. Data is used solely during transmission to generate a response and is not retained.
Anonymized and de-identified data may be used to evaluate and improve Bindplane's AI features. Identifiable personal information is never used for this purpose.
Pipeline Intelligence AI features are off by default. Nothing changes in your environment until an org admin explicitly enables them.
For full details, please review our Privacy Policy and EULA.
Best Practices
Always review AI-generated processors before deploying to production. While AI is designed to create correct configurations, it may make mistakes.
Things to verify:
Field paths match your actual data structure
Conditions and filters work as expected
Processor order is correct for your use case
Begin with simple requests and gradually add complexity.
Use multiple Pipeline Intelligence features together:
Use "Get Log Types" to identify log types
Use "Standardize Log Types for SecOps" on those log types if needed
Use "Parse Field" to parse fields if needed
Use "Generate Processors" to add any transformations
Last updated
Was this helpful?