Misleading message in starting log

[jgbarah]

When launching Kibana (current master HEAD) as

npm start

I see the following mesages:

[...]
managr    log   [09:58:44.558] [info][listening] basePath Proxy running at https://localhost:5601/xed
[...]
server    log   [09:58:51.555] [info][listening] Server running at https://localhost:5603
[...] 

The first problem is that the second message above is the only one you see when launching in a 20-line console. Reading it, it seems that Kibana will be available at https://localhost:5603 But that's not the case. It is at https://localhost:5601 as the first message seems to tell.

The second problem is that both messages are difficult to interpret, and given that they are the first think you see from Kibana when trying to run it, maybe having messages simpler to interpret would be a good thing.

So, in short, I would change both messages, and make it clear, probably in an additional message, that Kibana is ready to load in the browser at https://localhost:5601 so when you see it bootstrapping for the first time, it is clear how to access it in the browser.

In addition to this, I would a note to the CONTRIBUTING.md file explaining the url to load in the browser.

All these may seem minor issues, but I spent a good deal of time, and some questions, thinking that I had trouble with my Kibana installation, until I realized everything was fine, but I was just pointing my browser at the wrong url.

If you want, I can prepare a simple pull request for the CONTRIBUTING.md file.

[epixa]

This is definitely confusing, and I'd love to see it fixed up. This is a dev-only issue though since the basePath proxy is not used in release builds, but it's still worth making this all more clear.

And an update to the CONTRIBUTING.md file would be a great first step, thanks!

[bevacqua]

Agreed about the P3 -- I was going to reply something like that 💯

[timroes]

cc @elastic/kibana-operations Is this still something we want to look into, or can we close this?

[tylersmalley]

Closing as we no longer output the base path proxy information in the info logs.