Kibana version: 5.0.0-alpha4 (RC)
OS version: OS X
Original install method (e.g. download page, yum, from source, etc.): download page
Description of the problem including expected versus actual behavior:
Some background info: when you install a Beat, you have the option to run a script that loads the associated Kibana dashboards and index patterns by inserting docs in the .kibana index. The script creates "index patterns" in Kibana, but doesn't set them as default. After opening Kibana, you get this screen (expected):

It used to be that you could click on the metricbeat-* link to the left, mark it as default, and go on with your day. With alpha4, however, clicking on metricbeat-* results in a an error:

The only way out of this situation is to create a new index that overwrites the `metricbeat-* index pattern, but that's not ideal because we lose some defined formatters.
This is not necessarily a Kibana issue and it's more like Beats fault for messing with the Kibana index, but for the getting started experience I'd like to fix it somehow.
I see two potential solutions:
Steps to reproduce:
kibana subfolder, run ./import_dashboards.shmetricbeat-* index pattern the default@tsg good point, this is definitely a regression. I also ran into this issue once when I somehow removed my default setting, but I couldn't reproduce it.
@tylersmalley What do you think the right solution is here? Maybe we can change this line to only redirect for the root indices url instead of all subsections since this line handles redirects for non-existent index patterns anyway?
Part of me thinks we should just automatically set a default if we detect that index patterns exist, but there's no default. Eventually we're gonna remove that sidebar from the pattern creation page, and then users will be screwed again unless they know the exact url to type in to get to an existing index pattern's page. Lots of other stuff breaks in Kibana if there's no default we should just add one.
Bumping the priority on this since it's a regression.
Opened a PR to address this issue: https://github.com/elastic/kibana/pull/7588
The PR has been merged. After playing around with a couple scenarios, I ended up solving the regression instead of altering the functionality for the default index.
Many thanks @tylersmalley for the quick fix.
@epixa I assume it's too late for including it in alpha4?
@tsg Yeah, we'll need to keep the workaround in the blog post for now.
Most helpful comment
Part of me thinks we should just automatically set a default if we detect that index patterns exist, but there's no default. Eventually we're gonna remove that sidebar from the pattern creation page, and then users will be screwed again unless they know the exact url to type in to get to an existing index pattern's page. Lots of other stuff breaks in Kibana if there's no default we should just add one.