Data import and export
Import files let you bring an existing inventory into the model Cartographit expects. Prepare names, object types and fields before importing, then check the result on a limited scope.
- Define how your data maps to Cartographit objects.
- Harmonise names to avoid duplicates.
- Check the information and complete the necessary relationships.
Kubernetes connector
The Kubernetes connector collects information from your containerised environments to enrich the map. Its configuration must take into account the environments and access involved.
REST API
The REST API lets you build integrations with your tools and organise exchanges with your Cartographit project. The documentation details the available operations and authentication methods.
- Identify the data to exchange and its reference source.
- Define the project scope and the access required.
- Look up the available operations in the API documentation.
Update the map without starting from scratch
A first import sets the scope. After that, Kubernetes collection and exchanges through the REST API can feed the technical objects, depending on the integrations in place. For example, a team can check the items collected in its containerised environment, then complete their links with applications and business processes. The frequency and scope of updates are defined with your sources and your control rules.
Automation that keeps its meaning
Technical collection does not replace business knowledge. Identify one reference source for each piece of information, define update rules and plan checks on imported data. Processes and responsibilities require input from the teams.