This XML will only work when you passed VirtualMachine objects to the Scoreboard widget, that is expected since you only defined attributes for that object type. Your second portion of your statement doesn't come across clearly. The solution would be to have Custom Groups (CGs) that have SMs that roll up these aggregate #s for cpu, mem, etc. So it sounds like you're most of the way there. Just build a metric interaction file that include XML for CONTAINER adapter and whatever custom group type your using for object type. .. so if you had environment type custom groups:
<AdapterKind adapterKindKey="CONTAINER"
<ResourceKind resourceKindKey="EVIRONMENT"
In terms of organizing your customg roups, there are two ways to accomplish a clean-up:
- Create a new custom group type, only including the CGs for your use case. Then, filter your object widget to just those object types. I prefer this method.
- Create a custom group, and populate it with your custom groups you wish to isolate or view.. so we're nest CGs here. Then, when you configure the object widget, select that parent CG and select "child" and it'll populate the containing CGs of that parent. This method sometimes has advantages and allows some use cases for scoped reporting/views.