Kibana: Management - can't set default index pattern

[stacey-gammon]

Prior to this, I ran the ./metricbeat setup -e but there was no data, so while the index pattern showed up in kibana, I'd get an error about the index pattern not existing. Not sure if that is important to repro.

Anyhoo, just refreshing the page worked, so not a blocker, but really you shouldn't need to refresh the page. Just setting the default index pattern and switching to another app should save it.

[chrisronline]

@Stacey-Gammon

I'm not able to reproduce. Are these steps correct?

[stacey-gammon]

Strange. maybe it's flaky. I think I was on the 6.1 branch, maybe that made a difference? I did seem like it wasn't always happening to me, so might just be flaky.

[chrisronline]

I'll test in 6.1, but for now, I'm going to remove that label

[stacey-gammon]

++ I thought the label was for "i found this bug in 6.1". Thanks for removing!

[ruflin]

@Stacey-Gammon Is there any update on this one? I'm hitting this issue almost always when I start with a fresh installation of any Beat. I already got used to hit Cmd-R to fix it :-) I mostly test on master ...

[stacey-gammon]

@ruflin - looks like it's on the @elastic/kibana-management roadmap but unprioritized. I think it seemed it would rarely be hit, but if it's ends up being a bigger issue for beats users, that team may bump the priority. I'm sure they can give more insight!

[chrisronline]

@ruflin Happy to help more! I'll take a look today.

[chrisronline]

@ruflin Here are the steps I followed:

1) Start a fresh ES (6.1)
2) Start Kibana (6.1)
3) Run: ./filebeat setup -e
4) Configure filebeat to read from a log file
5) Run: ./filebeat -e
6) Add some lines to the log file
7) Verify data is in ES by hitting /_cat/indices
8) Open Kibana

Am I missing or adding a step to reproduce this?

[ruflin]

@chrisronline The above looks good to me. If you switch to using metricbeat you will remove the some steps above. I mainly test with master but the issue has been around for some time, so I assume it's also in 6.1.

[kthare10]

I am observing this issue in 6.3 as well for a index created via save_objects api. Is there a workaround for it?