# Logstash 7.17 on Windows - Pipeline running but logs are not present in Elasticsearch

**URL:** https://discuss.elastic.co/t/logstash-7-17-on-windows-pipeline-running-but-logs-are-not-present-in-elasticsearch/297519
**Category:** Logstash
**Created:** [February 17, 2022, 4:30pm UTC](https://discuss.elastic.co/t/logstash-7-17-on-windows-pipeline-running-but-logs-are-not-present-in-elasticsearch/297519 "2022-02-17T16:30:23Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [February 17, 2022, 6:13pm UTC](https://discuss.elastic.co/t/logstash-7-17-on-windows-pipeline-running-but-logs-are-not-present-in-elasticsearch/297519/2 "2022-02-17T18:13:40Z")

</div>

> [@bianca6](#):
>
> ` sincedb_path => "NULL"`

That will persist the in-memory sincedb across restarts in a file called NULL in logstash's working directory. If you do not want the sincedb persisted then use "NUL".

If that does not fix things, then set `--log.level trace` and look for [messages](https://discuss.elastic.co/t/logstash-wildcards-regex-not-working/164204/2) from the filewatch module.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-7-17-on-windows-pipeline-running-but-logs-are-not-present-in-elasticsearch/297519)._