Overview
Validate a configuration, then run sample telemetry through it to check what it does.
Telflo checks a configuration in two ways.
| Check | Question it answers | Where |
|---|---|---|
| Validation | Is the configuration well-formed and valid? | Inline in the editor. See Validation. |
| Testing | Does the configuration process telemetry as expected? | The Testing tab. |
Validation is static: it checks structure and schema. Testing is dynamic: Telflo runs a real OpenTelemetry Collector of the selected version, feeds your sample telemetry through the configuration, and captures the output.
pipeline.test3 passed
redact PII from log bodiesexpect → card number is maskedPASS
OTTL set k8s.cluster.nameexpect → attribute present on every spanPASS
tail_sampling at 5%expect → volume lands within budgetPASS
The Testing tab appears when testing is enabled for your account.
Testing tab
The Testing tab has three sub-tabs.
- Tests. Run the configuration against a sample input and review run history. See Running tests.
- Validation. Define rules that a run's output must satisfy. See Validating output.
- Suites. Group reusable tests and run them together. See Test suites.
The Testing tab operates on the current saved version of the configuration. Save a version first if prompted.
What a test run does
- You select a sample input file and a pipeline.
- Telflo runs a collector that matches the configuration's collector version, for a set duration (1 to 60 seconds, default 5).
- The sample telemetry is fed through the configuration, and the output is captured.
- The run is recorded in the history with a status, and you can inspect its output.
The following pages describe each part.