Validating configs

Running a test shows you what your pipeline produces. The Validation sub-tab lets you go further and assert what the output should be, so a run can pass or fail against rules you define rather than relying on a manual read of the output.

Validation rules

In the Validation sub-tab you define rules that a run's output is checked against. Rules let you encode expectations such as:

• The output contains (or does not contain) a particular value.
• A field matches a pattern (for example, a regular expression).
• The output has the shape you expect for the signal type.

When you build a rule that uses a pattern, Telflo provides a picker and editor so you can select or author the regular expression and confirm it matches the sample you expect.

How it fits with a run

1. Define your validation rules in the Validation sub-tab.
2. Run a test (see Running tests).
3. Telflo evaluates the captured output against your rules and reports which passed and which failed, so you get a clear verdict rather than just raw output.

This is what powers repeatable, automated checks — especially when combined with test suites, where each saved test can carry its own expected-output checks.

Static validation, too

Remember that Telflo also validates the configuration structurally and against the collector schema as you build — see Build → Validation. That static validation and these output checks are complementary: one confirms the config is valid, the other confirms it behaves correctly on real data.