Testing
Overview
Validate a configuration and run real sample telemetry through it before you deploy.
Telflo distinguishes two ways of checking a configuration:
| Question it answers | Where | |
|---|---|---|
| Validation | Is the config well-formed and valid? | Inline in the editor, and the Validation tab. |
| Testing | Does the config actually process telemetry the way I expect? | The Testing tab → Tests. |
Validation is static — it checks structure and schema. Testing is dynamic — Telflo spins up a real OpenTelemetry Collector of your selected version, feeds your sample telemetry through your configuration, and shows you what comes out.
The Testing tab
Open the Testing tab in the editor. It has three sub-tabs:
- Tests — run your config against a sample input and review run history. See Running tests.
- Validation — define checks that a run's output must satisfy. See Validating configs.
- Suites — group reusable tests and run them together. See Test suites.
The Testing tab operates on the current saved version of your configuration, within your current organization. Save a version first if prompted.
What a test run does
- You pick a sample input file and a pipeline to run it through.
- Telflo launches a collector (matching your configuration's collector version) and runs your config for a chosen duration (1–60 seconds, default 5).
- Your sample telemetry is fed in; the collector's output is captured.
- The run appears in the history with a status, and you can inspect its results.
The next pages walk through each part in detail.