> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/devx/6.2/deployment/configuration/agent/automation.md). # Provisioning This page describes how to setup connections to Kafka and other services and have changes applied automatically for the Lenses Agent.
OverviewLearn about provisioning.OverviewLearn & Provisioning.png
HQLearn how to connect the Agent to HQ.HQConfiguration -- Lenses HQ.png
KafkaLearn how to connect the Agent to Kafka.KafkaKafka -- Apache.png
Schema RegistriesLearn how to connect the Agent to Schema Registries.Schema RegistriesSchemas.png
Kafka ConnectLearn how to connect the Agent to Kafka Connect Clusters.Kafka ConnectKafka Connect.png
ZookeeperLearn how to connect the Agent to Zookeeper.ZookeeperZookeeper.png
AWSLearn how to connect the Agent to AWS.AWSKafka -- AWS.png
Alert & Auditing IntegrationsLearn how to connect the Agent to Alert & Audit Integrations.Alert & Audit integrationsMonitoring -- Integrations.png
JMXLearn how to connect the Agent to JMX for Kafka, Schema Registries, Kafka Connect and others.Infrastructure JMX MetricsConfiguration -- JMX Metrics.png
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lenses.io/latest/devx/6.2/deployment/configuration/agent/automation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.