8.1 Connecting to LLM

Most AI features in IDMP — panel generation, analysis suggestions, AI Chat, root cause analysis — require a connection to an external Large Language Model (LLM). IDMP uses an OpenAI-compatible interface, so any LLM provider or self-hosted model that exposes an OpenAI-compatible API can be used.

8.1.1 Built-In Trial Connection

IDMP ships with a built-in trial AI connection that is active for 15 days after installation. During the trial period, all LLM-dependent AI features work immediately without any configuration. Once the trial expires, you must configure your own AI connection to continue using these features.

TDgpt-based features (anomaly detection, forecasting, missing data imputation) are independent of the LLM connection. They require the TDgpt module to be installed alongside IDMP.

8.1.2 Configuring an AI Connection

AI connections are managed in the Connection Management section of the system settings, alongside TDengine data connections.

To add or edit an AI connection:

1. Navigate to Settings → Connection Management.
2. Click + Add Connection and select the AI connection type.
3. Fill in the connection fields:

Field	Description
Connection Name	A unique name to identify this AI connection
API Endpoint	The base URL of the OpenAI-compatible API (e.g., https://api.openai.com/v1)
API Key	The authentication key for the API. Leave blank for local deployments that do not require authentication.
Q&A Model	The model used for standard natural language queries and panel/analysis generation (e.g., gpt-4o)
Deep Thinking Model	The model used for complex analytical tasks that require extended reasoning, such as root cause analysis (e.g., o1 or o3)

4. Click Test Connection to verify the endpoint and credentials.
5. Click Save.

8.1.3 Two Model Configuration

IDMP uses two separate models from the same AI connection:

• Q&A Model — handles everyday interactions: answering natural language queries, generating panel suggestions, creating analysis configurations, and narrating panel insights. This model should be fast and cost-effective.
• Deep Thinking Model — handles computationally intensive tasks that benefit from extended reasoning chains, most notably Root Cause Analysis. This model can be slower and more expensive; it is only invoked when deep analysis is explicitly requested.

In the AI Chat interface, users can toggle Deep Thinking mode to route their query to the Deep Thinking Model instead of the Q&A Model.

8.1.4 Local Deployment

For organizations running a self-hosted LLM (such as a locally deployed Ollama or vLLM instance), set the API Endpoint to the local service URL and leave the API Key blank if the service does not require authentication. As long as the service exposes an OpenAI-compatible API, all IDMP AI features work without modification.

8.1.5 TLS/SSL Configuration

When the AI server uses a self-signed certificate or a certificate issued by a private CA, IDMP's default TLS verification fails with a PKIX path building error. You need to configure custom CA certificates or skip verification via environment variables.

Environment Variables

Variable	Description	Default
IDMP_TLS_CA_BUNDLE	Custom CA certificate paths. Supports multi-paths (using system path separator — : on Linux/macOS, ; on Windows), directory scanning, and mixed file+directory mode.	Empty (uses system default trust store)
IDMP_TLS_SKIP_VERIFY	Set to true to skip TLS certificate verification (development/test only)	Empty (no skip)

Both variables also fall back to the Java system property of the same name.

Using IDMP_TLS_CA_BUNDLE

Single PEM file:

export IDMP_TLS_CA_BUNDLE=/etc/idmp/certs/ca.pem

Multiple files (using system path separator):

export IDMP_TLS_CA_BUNDLE=/etc/idmp/certs/ca1.pem:/etc/idmp/certs/ca2.crt

Directory scanning (auto-discovers all .pem and .crt files):

export IDMP_TLS_CA_BUNDLE=/etc/idmp/certs/

Mixed mode:

export IDMP_TLS_CA_BUNDLE=/etc/idmp/certs/ca.pem:/etc/idmp/certs/extra/

Using IDMP_TLS_SKIP_VERIFY

export IDMP_TLS_SKIP_VERIFY=true

Note: IDMP_TLS_SKIP_VERIFY is only recommended for development and testing. Production environments should use IDMP_TLS_CA_BUNDLE with proper CA certificates.

Docker Compose Example

services:
  idmp:
    image: tdengine/idmp:latest
    environment:
      - IDMP_TLS_CA_BUNDLE=/etc/idmp/certs/ca.pem
      # - IDMP_TLS_SKIP_VERIFY=true  # development only
    volumes:
      - /path/to/certs:/etc/idmp/certs:ro

How It Works

IDMP uses a Composite TrustManager strategy: it first attempts verification using the system trust chain, and falls back to the custom CA bundle if system verification fails. This means public certificates in the system CA store remain valid and TLS connections to other services are unaffected.

8.1.6 Disabling AI Features

To disable AI features system-wide, click the avatar icon in the top-right corner of the browser, navigate to Admin Console, and pause or delete the AI connection.

You can also turn off AI suggestions directly from the analysis list or dashboard list page.