[Monitoring] "No logs for this cluster" often mistaken by users as an error

[richiejarvis]

Kibana version: 7.5.1

Elasticsearch version: 7.5.1

Server OS version: All

Browser version: All

Browser OS version: All

Original install method (e.g. download page, yum, from source, etc.): n/a

Describe the bug:
This is an understanding bug. The Monitoring page displays the following text if no logs events were seen in the time-picker period. This message implies that something is wrong - whereas the reality is often that Elasticsearch has not logged anything in the time period.

Steps to reproduce:

1. Set logging to low logging levels
2. View Monitoring with a time period where no logs have been written

Suggestion:
The message implies an error. Can we add some additional text along the lines of the below. The idea is to distinguish between no logs because there are no log events, and situations where logs are not being ingested.

Maybe there is a better way, but I think the language could be slightly clearer on the distinction.

No events logged for this cluster in this time period. 

You may wish to double-check that your setup is correct if you are expecting to see log events during this time period.

[elasticmachine]

Pinging @elastic/stack-monitoring (Team:Monitoring)

[wixaw]

I have same probleme

Thanks

[chrisronline]

Yup, agreed. Thanks for raising this. We'll add this to our backlog