# Elastic Search is receiving data from beat, but no documents appear

**URL:** https://discuss.elastic.co/t/elastic-search-is-receiving-data-from-beat-but-no-documents-appear/218230
**Category:** Elasticsearch
**Created:** [February 6, 2020, 5:53pm UTC](https://discuss.elastic.co/t/elastic-search-is-receiving-data-from-beat-but-no-documents-appear/218230 "2020-02-06T17:53:57Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [February 7, 2020, 10:52am UTC](https://discuss.elastic.co/t/elastic-search-is-receiving-data-from-beat-but-no-documents-appear/218230/10 "2020-02-07T10:52:35Z")

</div>

I've looked through the source and I do not see any obvious additional logging that can be enabled to trace a single document through an ingest pipeline, sorry.

Although I'm not familiar with how Beats configures Elasticsearch, I had a quick look at the source and I see a single `drop` processor here:

> <https://github.com/elastic/beats/blob/v7.5.2/x-pack/filebeat/module/panw/panos/ingest/pipeline.yml#L176-L187>

Is this the pipeline you're running? If so, it looks like it drops messages that do not have `_temp_.message_type` set to `TRAFFIC` or `THREAT` and in the request above this field is `SYSTEM`.

---

_[View the full topic](https://discuss.elastic.co/t/elastic-search-is-receiving-data-from-beat-but-no-documents-appear/218230)._