In production environments, ITSI is often deployed on a Search Head Cluster (SHC) for high availability. An SHC consists of multiple search head members managed by a captain. ITSI configuration replicates across members via the KV Store replication mechanism, not the standard SHC artifact replication.
This is a critical distinction: ITSI data lives in the KV Store, which has its own replication layer separate from the standard SHC bundle replication. If KV Store replication breaks, ITSI members may show inconsistent service health data. The captain is responsible for coordinating KV Store writes.