-
Title
Does the Federation Server Need Custom Derived Metrics? -
Description
A couple of custom dashboards don't work on the Federator console since the derived metrics that supply data only exist on the Federated child, but not on the Federator.
Is it a requirement to recreate the derived metrics from the Federated Child to the Federated Master?
-
Cause
The solution for the Federator is to add the Metric Property Topology Type (MPTT) of the Derived Metric (DM) (since they're not executed on the Federator).
A DM would normally not be executed on a Federator because of the missing incoming Data.
But without the DM on the Federator, the additional Metric Property is not added to the TopologyType.
The Federator thus has no clue that there is an additional field and will not pull the observations. -
Resolution
You can add the MPTT via the Web Console on the Federator per the screen shot attached and text file Metric Property Topo Types. This MPTT text file was derived from the screen shots of the two derived metrics:
Daily_CPU_Utilization_90_Percentile
Monthly_Avg_CPUUtilizationOne should be able to reverse engineer their own DM based on these DM screenshot examples.
In the screenshot case823269_import_topol_type.bmp, you'll see I selected Validate first, then one can proceed to select the Import button (both buttons at bottom of the screen).
On the Federator:
1. Web Console | Administration | Data | Topology Types
2. Paste your custom derived metric type definition into the "Import from Text" box
3. Click validate to make sure that the topology type is valid.
4. Click import. -
Attachments