Welcome To Coordimap Documentation
Coordimap helps engineering, SRE, and platform teams build an accurate picture of the infrastructure they operate. The Coordimap agent continuously discovers resources across Kubernetes, cloud accounts, and databases, then sends that inventory to Coordimap so teams can understand dependencies, visualize architecture, and work from current infrastructure data instead of stale diagrams.
The docs in this section explain how to install the agent, configure data sources, and use stable upstream identities such as scope_id so the discovered graph remains clean and reliable over time.
They also explain how to use external_mappings when you need to connect flow telemetry or cloud-side identities back to the correct Kubernetes or infrastructure scope.
Get Started With The Coordimap Agent
Choose the installation method that fits your environment.
Binaries
Download the Coordimap agent from GitHub releases and run it directly on a host.
Docker
Run the Coordimap agent as a container with a mounted configuration file.
Kubernetes
Deploy the Coordimap agent on Kubernetes with the maintained Helm chart or a raw manifest.
Start With Shared Configuration
Before you configure individual data sources, read these two pages:
Configuration Guide
Understand how Coordimap agent configuration is structured and how data_source_id differs from scope_id.
Shared Configuration Options
Learn what scope_id means, how to find it, and why stable upstream identity matters.
Configuration Troubleshooting
Fix common problems such as missing scope_id, broken external_mappings, and datasource identity mismatches.
Configure Your Data Sources
Kubernetes
Cloud Infrastructure
AWS
Configure AWS account crawling, flow telemetry, and the correct account-level scope_id.
Google Cloud Platform
Configure GCP project crawling, VPC Flow Logs, and the correct project-number scope_id.
eBPF Flows
Capture runtime network traffic with the flows datasource and connect it to the right Kubernetes scope with external_mappings.
Databases
PostgreSQL
Configure PostgreSQL schema crawling with a stable system_identifier scope_id.
MySQL And MariaDB
Configure MySQL or MariaDB schema crawling with a stable server_uuid scope_id.
MongoDB
Configure MongoDB crawling with a stable replica set or cluster scope_id.