# Logstash filter verifier - daemon mode in Docker

**URL:** <https://discuss.elastic.co/t/logstash-filter-verifier-daemon-mode-in-docker/311556>\
**Category:** Logstash\
**Tags:** docker\
**Created:** [August 5, 2022, 3:54pm UTC](https://discuss.elastic.co/t/logstash-filter-verifier-daemon-mode-in-docker/311556 "2022-08-05T15:54:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rilcy](https://avatars.discourse-cdn.com/v4/letter/r/e99b99/32.png) [@rilcy](https://discuss.elastic.co/u/rilcy)\
**Post date:** [August 5, 2022, 3:54pm UTC](https://discuss.elastic.co/t/logstash-filter-verifier-daemon-mode-in-docker/311556/1 "2022-08-05T15:54:05Z")

</div>

Hi everyone,

I use this great project from Magnus Bäck [GitHub - magnusbaeck/logstash-filter-verifier](https://github.com/magnusbaeck/logstash-filter-verifier) to validate my Logstash filters in a Gitlab CI.

It runs the version 1.6.3 in a Docker container to validate filters for multiples pipelines.

I am wondering if there is any chance to make it works using the daemon mode [GitHub - magnusbaeck/logstash-filter-verifier](https://github.com/magnusbaeck/logstash-filter-verifier#version-20-daemon-mode-only)

I am especially interested in the pipeline configuration feature.

Because, at the moment, i have about 15 pipelines, each having their own grok filters that resides each in their own .conf file in a config directory i am mapping into the Docker container.

Seems like all of them are considered for every JSON test file i defined in my tests directory.

Does anyone know how to map a given pipeline to a JSON test file ?

Thank you in advance

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 2, 2022, 3:54pm UTC](https://discuss.elastic.co/t/logstash-filter-verifier-daemon-mode-in-docker/311556/2 "2022-09-02T15:54:08Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
