I have installed metribeat in a specific host named sag-dfo-055. in the connection between the metricbeat agent and logstash timeouts dont occur as the relative image show in a specific timeframe. So everything works ok.
Neverthelss when i apply in kibana a filter in order to see results for a specific service in the exact same timeframe i get the results that the image below shows:
Neverthelss i cant explain still the gap that i see in kibana, even when the service is down it should have been able to be seen the relative logs in the kibana index....
Finally from the logs of the metricbeat agent itself hosted in the folder path: C:\ProgramData\metricbeat\logs there are no error logs and all info logs show normal behaviour
Any help please?
I cant figure out why when i apply the specific filter i have no information at all in my kibana index. How can i troubleshoot that problem?
Metricbeat's process.name doesn't really check for services, it checks for the processes spawned by a service. It looks to me like that process crashed right about when it shows on the chart and then got restarted by the service some time after.
Thank you for your reply, nevertheless i dont understand what do you mean by saying: "process.name doesn't really check for services, it checks for the processes spawned by a service".
Do you also imply that the service itself never crashed?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.