You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, when I check the Elasticsearch index, I can only see logs from Nginx and Filebeat itself. The logs from the other three services, including the streaming service, are missing. The primary concern is to view the logs from the streaming service, which have the following format:
06:16:00 DEBUG timeout {"stream": "6", "state": "⌛"} 06:16:00 INFO ⌛->🔴 {"stream": "6", "action": "timeout"} 06:16:02 DEBUG timeout {"stream": "10", "state": "⌛"} 06:16:02 INFO ⌛->🔴 {"stream": "10", "action": "timeout"} 06:16:11 INFO stop {"stream": "9", "type": "testFLV", "ID": "824672616960"} ...
I suspect that the log format might be the issue preventing the logs from the streaming service container from being collected in Elasticsearch.
The text was updated successfully, but these errors were encountered:
Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!
hi all,
I've recently been using Filebeat to collect logs and send them to Elasticsearch (without Logstash). I have a VM running five containers:
Nginx
Filebeat
Node-exporter
Cadvisor
Monibuca (a streaming service container)
My Filebeat configuration looks like this:
However, when I check the Elasticsearch index, I can only see logs from Nginx and Filebeat itself. The logs from the other three services, including the streaming service, are missing. The primary concern is to view the logs from the streaming service, which have the following format:
06:16:00 DEBUG timeout {"stream": "6", "state": "⌛"} 06:16:00 INFO ⌛->🔴 {"stream": "6", "action": "timeout"} 06:16:02 DEBUG timeout {"stream": "10", "state": "⌛"} 06:16:02 INFO ⌛->🔴 {"stream": "10", "action": "timeout"} 06:16:11 INFO stop {"stream": "9", "type": "testFLV", "ID": "824672616960"} ...
I suspect that the log format might be the issue preventing the logs from the streaming service container from being collected in Elasticsearch.
The text was updated successfully, but these errors were encountered: