Validation
How Telflo checks your configuration as you build, and how to fix problems.
Telflo validates your configuration continuously so you catch problems before you test or deploy. Validation runs at two levels: structural (connection and graph rules, in the browser) and schema (against the collector's component schemas).
What gets checked
Connection rules
| Rule | Severity |
|---|---|
| Receivers must have an outgoing connection | Warning |
| Exporters must have an incoming connection | Warning |
| Processors must have both an input and an output | Error |
| Extensions must not be connected | Error |
| Connections must respect component types | Error |
Schema validation
Beyond wiring, Telflo validates the configuration against the selected collector version's component schemas, so unknown components, fields, or invalid values are surfaced.
Visual indicators
Problems show up directly on the canvas:
- Yellow border — a warning. The pipeline can work but is incomplete or suboptimal (for example, a receiver with nothing wired to it yet).
- Red border — an error. The pipeline won't work until it's fixed.
The validation panel
The validation panel lists every issue it finds, each with:
- The node (component) affected.
- A short description of the problem.
- Its severity (warning or error).
Click an issue to focus the related component, fix it, and watch the indicator clear.
Fixing common issues
| Symptom | Likely cause | Fix |
|---|---|---|
| Red border on a processor | Missing input or output | Connect both sides into a pipeline. |
| Warning on a receiver/exporter | Not yet wired up | Draw an edge to/from it. |
| Schema error on a field | Value not allowed for this collector version | Correct the value, or change the collector version in the toolbar. |
| Canvas won't rebuild from YAML | YAML syntax error from a manual edit | Fix the syntax flagged in the YAML view. |
Validation vs. testing
Validation answers "is this configuration well-formed and valid?" To answer "does it actually do what I expect with real data?", run a test — see the Testing section.