Configuration Manager (CI/CD)

The TrackMe Configuration Manager (TCM) brings config-as-code to TrackMe. It captures your admin operations as replayable transactions, so configuration flows from a non-production environment, through source control, into production — instead of being hand-applied on the live system.

How it works

TCM runs in two modes:

• Receiver mode (non-production) — every admin-level operation you perform (creating a tenant, editing a policy, and so on) is recorded as a transaction in a journal.

• Producer / replay mode (production) — the production instance reads the journal and replays the exact same REST calls, applying each transaction exactly once (it is idempotent, keyed on the transaction).

The workflow is: configure in non-production → your CI/CD pipeline picks up the journal and version-controls it with the TCM release → release to production → TCM replays it.

Note

• TCM is a separate add-on (TA-trackme-conf-manager), downloaded from the TrackMe downloads site rather than Splunk Base, so Cloud customers can repackage and self-publish it.

• In a non-production search-head cluster, the journal is a local file and is not replicated across members — run TCM on a standalone non-production instance, or manage journal synchronisation yourself.

See also

• CI/CD & config manager — in depth — the producer/receiver config keys, the receiver endpoint and journal, trackmeconfmanager, and Cloud vs Enterprise packaging.

• REST API reference — the REST calls TCM records and replays.

• Backup & restore — state backups, the complement to config-as-code.