Python scripts that run in CI, build a digital twin of the running system, and push it to Studio via the API.
The IOModel Collector builds a digital twin of the system you actually run and sends it to Studio. Collectors are a set of Python scripts that you embed in your CI pipeline; on each run they capture the current state and push it to IOModel via the API.
Part of IOModel Digital Twin
Collector is the capture half of IOModel Digital Twin. The Validator is the compare half.
How it works
Add collectors to CI
Drop the Collector Python scripts into your pipeline so they run on each build or deploy.
Capture the digital twin
The scripts inspect the running system (services, dependencies, configuration) and assemble a digital twin.
Push to Studio via API
The digital twin is sent to IOModel through the API, where it is stored alongside your model.
Validate against the model
What the digital twin is
The digital twin is a snapshot of the real system, separate from the architecture model you design. Keeping both lets IOModel answer a precise question: does what we designed still match what we run?
Pro plan
The Collector is part of the IOModel Pro plan. See Plans for the full breakdown.
Related
Last updated on