# Investigating why all logs aren't visible in Kibana

**URL:** <https://discuss.elastic.co/t/investigating-why-all-logs-arent-visible-in-kibana/160004>\
**Category:** Logstash\
**Created:** [December 8, 2018, 11:21am UTC](https://discuss.elastic.co/t/investigating-why-all-logs-arent-visible-in-kibana/160004 "2018-12-08T11:21:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![duncOps](https://avatars.discourse-cdn.com/v4/letter/d/c89c15/32.png) [@duncOps](https://discuss.elastic.co/u/duncOps)\
**Post date:** [December 8, 2018, 11:21am UTC](https://discuss.elastic.co/t/investigating-why-all-logs-arent-visible-in-kibana/160004/1 "2018-12-08T11:21:22Z")

</div>

Hi all,

I've put "Kibana" as the category for the post, but realistically it could be any part of the Elastic stack that I've misconfigured.

**Elastic stack structure**  
Azure-hosted VMs running the following; part of the same IP range as the DCOS platform:

- Elastic-master
- Elastic-data-1
- Elastic-data-2
- Logstash
- Kibana

**Application infrastructure**

- Master Nodes (Azure-hosted Linux VMs) running DCOS container orchestration platform
- Agent Nodes (Azure-hosted Linux VM Scale Set) running containers, orchestrated by DCOS
- Application comprised of NodeJS microservices each running as a container
- Microservices log to container's STDOUT
- Containers' STDOUT entries are stored in log files on whichever Agent Node they're running on

**Log-scraping**

- Filebeats container running on each Agent Node
- Scrapes logs from Agent Node
- Passes to Logstash
- Logstash pipeline filters/categorises log entries and passes to Elasticsearch

This setup works as intended in our `Development` environment. In Kibana, I can see all of our containers' logs/log entries and they're parsed correctly.

I've just recreated the ELK cluster in our `Pre-Production` environment and encountered the following problems in Kibana:

- Not all log entries appear to be coming through; I can only see 5 of our ~20 microservices
- If I click on "Logs", I see the error "Looks like you don't have any logging indices." yet if I go to "Management" then "Elasticsearch Index Management", I can see my indices with green health status

In an attempt to diagnose these problems, I would like to know:

- How can I be certain that all of the Elastic nodes are working together and processing data?
- In my Logstash pipeline, should I be specifying the IP addresses of _all_ of my Elastic nodes (Master and 2x Data) or just the Master? Currently I'm just specifying `hosts: [10.0.0.5]` which is the IP of the Master
- Is there a way that I can see the log entries that Logstash is sending to Elasticsearch, and a way that I can see the output that Kibana is accessing from Elasticsearch?

Thanks 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:** [January 5, 2019, 11:21am UTC](https://discuss.elastic.co/t/investigating-why-all-logs-arent-visible-in-kibana/160004/2 "2019-01-05T11:21:30Z")

</div>

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