Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.drdroid.io/llms.txt

Use this file to discover all available pages before exploring further.

DrDroid connects to OpenSearch so DroidAgent can query logs during alert investigations. Add the integration from the OpenSearch setup page or through the VPC agent.

Connection via dashboard

Open Agent Setup → Integrations → OpenSearch, or go directly to aiops.drdroid.io/integrations/open_search. Choose one of the two connection types:

OpenSearch Connection with Basic Auth

Use this when your cluster requires a username and password.
FieldDescription
Integration NameA label for this connector (e.g. Production OpenSearch).
Protocolhttp or https.
HostOpenSearch hostname, e.g. my-opensearch.example.com or localhost. Do not include the port in the host if you set Port separately.
PortCluster port, e.g. 9200.
UsernameRead-only user with access to the indices the agent should query.
PasswordPassword for that user.
Save the form and test the connection.

OpenSearch Connection (Host Only)

Use this when your cluster does not require basic authentication (for example, a VPC-restricted endpoint or a cluster behind another auth layer). Fill in Integration Name, Protocol, Host, and Port the same way as above. Username and password are not required for this connection type.

Connection via VPC agent

If you run DrDroid through the VPC agent, add an OpenSearch entry to your secrets.yaml (copy from credentials_template.yaml):
connector_name:
  type: "OPEN_SEARCH"   # do not change
  protocol: "https"     # http or https
  host: your-opensearch-host.example.com
  username: your_username
  password: your_password
  port: 443             # optional
  ssl_verify: "false"   # optional (default false)
See the OpenSearch section in the credentials template for the full field list. Restart or reload the agent after updating secrets so the new connector is picked up.

Permissions

Use a dedicated read-only user. Grant access only to the indices and index patterns your on-call team expects the agent to query.