Issue | Space update from object in Default space | broken links

Deployment
1

We just completed the update to V1.1.38.0, and we wanted to update one of our existing Spaces with the new objects in the “Default” space.
However after importing the generated json file from the Default space, and importing it in our other existing spaces (using option “check for existing objects, automatically overwrite conflict”). All the link are broken between dashboard.
is it a normal behavior?
did we miss something in the process?

image
image824×545 46.2 KB

Thanks

2

@fherbere Yes, in Elastic v8.12+ dashboards and other visualization objects no longer can be copied from space to space while maintaining their original GUIDs. Previously this worked because each space created a prefix for imported dashboards so:

  • “default” space dashboard would have a GUID that looked like this: “default:GUID”
  • “other” space dashboard would then have a GUID that looked like this: “other:GUID”.

The GUID value remained constant across the spaces, and we could freely copy dashboards between spaces, and they never conflicted with each other. That’s no longer the case. Now, the idea is to “share” dashboards between spaces. Now, each dashboard has a GUID that’s independent of the space that it sits on, but if you go to Stack Management > Saved Objects you can see that you can assign multiple spaces to each dashboard. That makes them “visible” in other spaces, but it’s similar to a central file. Each dashboard is centrally located, so editing it in one place reflects these changes in other spaces. A way to break that relationship is to make a copy of it and re-create it with new GUIDs.

I guess what this means for us, is that we now have a set of “central” dashboards in “default” space. These come from us (Bimbeats). I would delete all dashboards that were duplicates of the original ones and all of the dashboards that you copied around into other spaces. I would then “share” dashboards from the “default” space into other spaces as needed via the Stack Management > Saved Object interface. If you want to make a copy of any of them, that breaks that “central model” setup, just export it to NDJSON and then import it into another space, and check the box that says to “create new random GUIDs”.

2 Likes
3

Thanks for the clarification @ksobon, this is very clear and the “centralized” way of managing dashboard will be beneficial to us overall.

4

@ksobon sorry i am coming back to this topic, so i can share only Data view Object between spaces correct? Other objects type cannot be share for now.

image
image1027×165 30.4 KB

5

@fherbere Yes, “for now” it’s just Data Views. Dashboards should be available soon. 8.13 still doesn’t have it enabled but hopefully 8.14 will. I am sorry about that. I guess Elastic hasn’t finished implementing this yet.

6

thanks for the clarification , i wanted to make sure i didn’t miss anything in our setup :+1:

7

@fherbere no you haven’t. If anything I must have missed that it wasn’t there yet for 8.12. I should have phrased it better. I will keep an eye on Elastic, and let you know when that’s available. Right now, we are in a little bit of limbo. I am sorry.