Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
It is now (7.0 at least):
This presents us with a problem when distributing dashboards with our Beats. Where previously we could just rely on e.g. the
I like 2 because it's a longer term solution, but I did want to see if there are other opinions, and maybe if somebody from the Kibana team can confirm if this is the way to go.
/cc @sayden @ruflin @jsoriano - since you hit this as well in #10076
(Somebody on the Beats team please correct me if I'm wrong)
So I don't think that we create index patterns in the Beats, at least I don't see where just now. We create index mapping templates and then import dashboards. I guess now we might have to create index patterns as well?
All this is automated (user just runs
So I've done a bit more research.
The premise of all this is that we want to make it simple for users to get started with any Beat. To that end, each Beat ships with an index pattern and one or (usually) more dashboards.
The way it currently works we get these two objects like this:
Users can then use the
Maybe this could be addressed by defaulting
I tried setting
Only this week I have seen two reports caused by this:
Was this already changed in Kibana 6.6?
I wonder if we can do something to improve the experience here.