- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a rule of thumb, use the existing attributes/metrics where you can before creating SMs. Sometimes the metric you're seeking is already there on container resources such as groups. If you're interested in specifically CPU Demand (Mhz), you're in luck. This metric is already aggregated for a Group ResourceKind.
This is the metric: Virtual Machine > CPU > Total Demand(MHz)
You're losing me a little bit on your last two sentences, but it seems like you're having a problem applying the supermetric to a resource. As a reference, a supermetric by itself in the editor window is merely a definition of a formula. It needs to be added to a supermetric package, then that package needs to be assigned to a resources to be applied. The SM will then be calculated with the next collection.