Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Ffleet-management%2Fconfig-navigator%2Fquick-start.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fuser-guides%2Ffleet-management%2Fconfig-navigator%2Fquick-start.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

# Quick start: your first time using Config Navigator

This guide shows how to move from raw YAML to a visual architectural map using Config Navigator, helping you validate your first configuration.

## 1. Access the visualization[​](#1-access-the-visualization "Direct link to 1. Access the visualization")

Access **Fleet Manager**, then **Configuration**. Select any of the configuration groups. The opened page displays a split view with the YAML editor on the left and the **Config Navigator** canvas on the right.

## 2. Generate the architecture map[​](#2-generate-the-architecture-map "Direct link to 2. Generate the architecture map")

The visualization updates automatically—no save action is required.

* **Existing configurations**: The graph renders as soon as the configuration loads.
* **New configurations**: Begin typing a receiver, processor, or exporter. Once the YAML is syntactically valid, the corresponding nodes appear on the canvas.

[![Generate the architecture map](/assets/images/configuration_map-f92744fe98482a04356038540fce72aa.webp)](https://docs-docusaurus.kinsta.page/assets/images/configuration_map-f92744fe98482a04356038540fce72aa.webp)

## 3. Understand pipeline components[​](#3-understand-pipeline-components "Direct link to 3. Understand pipeline components")

Read the graph from left to right to follow the lifecycle of your telemetry data:

* **Left-side nodes (green)**: **Receivers**, showing where data enters the pipeline (for example, `otlp` or `hostmetrics`).
* **Middle nodes**: **Processors**, applied in sequence. Verify that the order reflects your intended logic, such as filtering before batching.
* **Right-side nodes**: **Exporters**, representing destinations such as Coralogix or Prometheus.
* **Purple nodes**: **Connectors**, indicating where one pipeline feeds into another for advanced routing scenarios.

## 4. Navigate and inspect the graph[​](#4-navigate-and-inspect-the-graph "Direct link to 4. Navigate and inspect the graph")

Use the canvas controls to explore complex configurations:

* **Zoom and pan**: Zoom with the scroll wheel and drag the canvas to move between pipelines (logs, metrics, traces).
* **Fit to view**: Select **Fit to view** (bottom right) to center the entire architecture on the canvas.
* **Path highlighting**: Select any node to highlight its inbound and outbound connections, making it easier to trace a specific data path through dense configurations.

## 5. Identify and fix issues visually[​](#5-identify-and-fix-issues-visually "Direct link to 5. Identify and fix issues visually")

Config Navigator provides immediate feedback when it detects configuration problems.

* **Validation indicators**: Nodes outlined in red or marked with a warning icon indicate errors. Hover to view details, such as missing required fields or references to undefined components.
* **Editor correlation**: Select a problematic node to identify the corresponding section in the YAML. Visual cues indicate exactly which component requires attention.

## Next steps[​](#next-steps "Direct link to Next steps")

Learn how to create, version, and manage configurations across your fleet in [Configuration management](https://docs-docusaurus.kinsta.page/user-guides/fleet-management/configuration-management/.md).