AI Observability Module Installation
The AI Observability module is delivered as three complementary components.
Delivery Composition
| Component | Purpose |
|---|---|
| Content module | Dashboards, scheduled jobs, runtime indexes, tags, and ISM policies |
| Installation utility | Deploys ingest pipelines, index templates and patterns, gen_ai_* write indexes, lookups, the ai command preset, the GPU inventory asset, and health metrics |
| Data collection configurations | Configurations for LLM Gateway, Inference, Claude Code, Codex, and GPU, plus the Claude Code subscription-limit collector |
Installation Steps
- Installing the utility - deploy objects not included in the content module: ingest pipelines, index templates and patterns,
gen_ai_*write indexes, lookups, theaicommand preset, the GPU inventory asset, and health metrics - Installing the content module - import
ai_observability.zip(dashboards, jobs, indexes, ISM policies, and tags) - Bind retention policies - rerun the utility with
--bind-ism-policiesafter importing the content module - Setting up data collection - deploy the data collection configurations and set up telemetry routes
The utility runs before the content module is imported because module jobs and dashboards refer to templates, patterns, lookups, and a preset that the content module does not include. Retention policies, however, are included in the content module, so the utility binds them to write indexes on a second run after import.
When updating from 6.1, run the utility again after import with --remove-legacy-dashboards: this removes the version 6.1 dashboard that is not included in 6.2. The --bind-ism-policies and --remove-legacy-dashboards flags are mutually exclusive and require separate runs.
Post-installation Actions
| Action | When |
|---|---|
Import rows into claude_code_members from the organization member export in the Claude console; without them, member dashboards and incidents lack member names and seat types | after a new installation |
Adjust seat prices in claude_code_seat_pricing to match the contract; the utility writes Team plan prices only to an empty lookup | if the contract differs from Team plan prices |
Set the model in the ai_observability_default preset if its name differs on this installation | if the model name differs |
Replace HOST:PORT in ai_observability_api_* job requests and add the keystore key before enabling them (Jobs) | if the jobs are needed |
| Wait for analytics to accumulate: lookup jobs recalculate the last two days, and earlier telemetry is not added to analytics (Jobs) | after a new installation |
Reapply manual changes to Service Monitor Toolkit metrics and their permissions; rerunning the utility overwrites the supplied metrics | after each utility run |
Run the utility with --bind-ism-policies; without it, retention policies are not bound to write indexes and rollover does not work | after each content-module import |
Migrate data from gen_ai_* indexes used by version 6.1 collection using the commands printed by the utility | when updating from 6.1 |
Run the utility with --remove-legacy-dashboards; the update does not remove the AI Observability: Claude Code dashboard, and the UI does not remove it either | when updating from 6.1 |
| Delete copies of module dashboards that were edited in the UI; while such a copy exists, it opens instead of the updated dashboard | when updating from 6.1 |
Installing the Content Module
Importing the AI Observability content module through the Search Anywhere Framework Content Management menu.
Utility Installation
Deploying infrastructure objects of the AI Observability module using the ai_observability_ko_maker utility.
Data Collection Setup
Deploying the AI Observability module Data Collection Configuration — SAF Beat Manager, Logstash, OTLP Collector, LiteLLM gateway.