Ridiculas amount of logging when Elasticsearch vs higher than Kibana

[LeeDr]

Kibana version: 5.0.0

Elasticsearch version: 5.0.1-SNAPSHOT

Description of the problem including expected versus actual behavior:
I'm running the Kibana 5.0 branch code and esvm is (I think) pulling from elasticsearch 5.0 branch, which apparently is now 5.0.1, so now Kibana logs a warning about ever 2 seconds!

If Elasticsearch has to put out an emergency 5.0.1 patch, the Kibana team should not have to release a 5.0.1 patch just to stay in sync. And customers should not be tortured with a relentless onslaught of warnings. Customers would quick set a log level to error to avoid filling logs with the same message.

Steps to reproduce:

1. checkout kibana 5.0 branch
2. run npm run test:ui:server
3. output includes the Elasticsearch version 5.0.1;

starting up "ui" cluster
INFO -  - cluster - Downloading & installing from "5.0" branch.
INFO -  - cluster - Installing plugins
INFO -  - cluster - Purging C:\git\kibana\esvm\test\branch-5.0\data
INFO -  - cluster - Starting 1 nodes
INFO -  - cluster - esvm log level configuration disabled
INFO - ? - ? - [2016-10-28T13:51:09,164][INFO ][o.e.n.Node               ] [] initializing ...
INFO - HHqdtkE - node_environment - using [1] data paths, mounts [[OS (C:)]], net usable_space [28.3gb], net total_space [190.2gb], spins? [unknown], types [NTFS]
INFO - HHqdtkE - node_environment - heap size [1.9gb], compressed ordinary object pointers [true]
INFO - HHqdtkE - node - node name [HHqdtkE] derived from node ID; set [node.name] to override
INFO - HHqdtkE - node - version[5.0.1-SNAPSHOT], pid[10172], build[9076512/2016-10-27T01:26:06.378Z], OS[Windows 10/10.0/amd64], JVM[Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/1.8.0_73/25.73-b02]
WARN - HHqdtkE - node - version [5.0.1-SNAPSHOT] is a pre-release version of Elasticsearch and is not suitable for production

1. then Kibana is started and logs;

server    log   [18:52:17.325] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:19.862] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:22.400] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:24.983] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:27.517] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:30.093] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:32.609] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:35.170] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:37.683] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:40.249] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:42.766] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)
server    log   [18:52:45.315] [warning] You're running Kibana 5.0.0 with some newer versions of Elasticsearch. Update Kibana to the latest version to prevent compatibility issues: v5.0.1 @ 127.0.0.1:9220 (127.0.0.1)

[LeeDr]

Note that #8515 says "we should log .. on startup...", not constantly.

Following discussion about #8267, users should be able to run a newer patch version of Kibana against an older patch version of Elasticsearch, and we should log an appropriate warning on startup whenever they do. This is the exact same behavior that we already provide when doing the opposite: running a newer patch version of Elasticsearch against an older patch version of Kibana.

[jbudz]

How recent was this branch? #8865 should address this

[LeeDr]

That should do it.