Swap defaultAppId with defaultRoute in example config

[matschaffer]

Connected to #6902

Summary

Swaps example config based on current actual functionality. I got
confused about which setting to use after using the example config as a
starting point.

Checklist

• This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-operations

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[mistic]

Maybe we can also deprecate the old defaultAppId option. What do you think @tylersmalley ?

[matschaffer]

Does defaultAppId still do something? When I tried to set it to "monitoring" kibana just gave me a blank screen (on 6.3.2)

[mistic]

@matschaffer I believe it is working. At least I just set into the kibana.yml
kibana.defaultAppId: "dashboards"

And it worked. Let's see if @tylersmalley has any insights on this.

[fbaligand]

Now that we have Kibana Spaces, it would be great that "defaultRoute" is available as advanced setting!
It would let to define a default route per space!

[fbaligand]

BTW, for this PR, it could be interesting to fix documentation for "kibana.defaultAppId" default value.
Currently, it is indicated "discover", although the right default value is "home":
https://github.com/elastic/kibana/blob/master/docs/setup/settings.asciidoc

[fbaligand]

Compared to defaultAppId, I see a major limitation in defaultRoute:

• defaultAppId is the default home page per space (as it contains only hash part)
• defaultRoute is not per space (as it contains full URI)

Personally, I use defaultAppId to define a custom dashboard home page per space.
Example: "dashboard/home"

[jbudz]

Yeah this is a little confusing, but +1 on the swap to de-emphasize kibana the application. Taking a step back, we have the kibana platform which has applications. Inside that there's a SPA called kibana which includes discover, visualize, dashboard, home, dev tools).

kibana.defaultAppId sets the page that you'll be redirected to if you visit localhost:5601/app/kibana using the browser router

server.defaultRoute sets the page that you'll be redirected to if you visit localhost:5601/ using the server router

I think deprecating defaultAppId isn't going to be very straight forward because the triggers are separate.

[jbudz]

LGTM, #28547 (comment) would be cool too. Spaces integration sounds interesting but I'm not 100% familiar with it yet

[fbaligand]

I realized today that for a "home page per Kibana Space", there is already an issue for that :
#26126

[epixa]

I'm removing my review on this since @jbudz already reviewed it. I'm not sure what the plan is here since it has been idle since January.

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[matschaffer]

Rebased to try to clear CI failures. Diff looks unchanged. @jbudz - let me know if I'm clear to click squash merge or if something else should happen first (after CI passes, of course).

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[jbudz]

👍 go for it