Ah I think I ran into a similar problem a few weeks ago.
The first thing to note is the way management zones filter and the way segments filter is fundamentally different. Management zones allow filtering of all data types by entities whereas segments filter on records specified in the segment definition.
So when you create a segment it only filters on the data types specified in the segment. From what I see in your screenshot, we’re only filtering on entities and don’t have a section in the segment specifying how to filter on metrics.
The reason why this works in the infra/ops app is the base query for all of the tiles is “fetch dt.entity.host”. You can see this if you look at the network tab and refresh the page and then filter requests for “query”. With that, you can see all of the queries that make up any new platform pages. Unrelated to this, I find it very useful for learning how apps achieved specific views to help replicate them on a dashboard or notebook.
So, to fix the segment we need to add a metric section to the segment that tells the segment how to filter the metric OR we need to change the queries on the dashboard to start by fetching the host, just like in the infra/ops app.
If we wanted to add that metric section to a segment AND use the segment to filter by different types of cloud regions then we could combine the variable query something like this.
Then when we go to use the variable in our segment definitions it would look something like this.
The last thing is actually using the segment and how that looks. If we query the dt.host.cpu.usage metric and split by our regions, we can see that I have it filtered on just the region I wanted. And thanks to the pretty name I can identify which region I’m filtering for while using the technical fields behind the scenes.
As we can see though, this doesn’t work for the host query.
So now lets make it work with the host query. First we would add our region entities and then add the host relationship for each.
Now when we rerun that host query it starts working because we’ve directly addressed how to filter for that record type with our segment.
Hopefully this gets you on the right track with how segments work and how to make use of them in your case. Last time I was configuring them there was a limit to 20 configurations in a single segment so it may be difficult to make a generic “data center” segment that applies everywhere it can. If you make one for each Azure, AWS, VMWare and GCP then you’d be able to cover more use cases, but you’d also have 4 separate segments.