Support configs per space

[wolframhaussig]

We have a Elastic Stack installation where each team has a separate space. In every space only the index patterns exist which are required by this space. We have also installed LogTrail with a config for each of the indexes.

Currently, all index configs show up in LogTrail independently from the selected space. Therefore, this produces errors when opening LogTrail for the first time when the first entry does not exist in this space:

Cannot fetch hosts : Check if the index pattern xxx-* exists

What we would like:
I don't know what is possible but we would like to either have LogTrail recognise that the index pattern does not exist and hide the entry by itself or add a config entry which config should be shown in which space. Perfect would be to have separate configs for each space because each space is administrated by a separate user

[sivasamyk]

@wolframhaussig I have not tested logtrail with x-pack feature, so it might not be compatible with x-pack. The right solution would be have a logtrail config object per space. logtrail has the ability to store the config in ES instead of a JSON file. So the right solution would be store the logtrail config for each space in its own saved object.

I have not used Kibana Spaces, so not aware of the how the saved objects are stored internally for each space. I will check this and see how we can support this.