Metric Family metric filtering at the Monitoring Profile level has removed the metric from polling. As a result it's not being polled for the related metric data.
This can be observed in a sample devices Polling Configuration. This can be found via the DA_Host:8581/dcdebug page.
In this example Speed metrics were missing data. When viewing the Polling Configuration for a sample device showing the problem we could see something like this. Note there are 36 metrics collected, none of which are the Speed metrics that were sought.
Polling Config Item ID=1328342
Poll Group ID=6435
Normalized Facet Type={http://im.ca.com/normalizer}NormalizedPortInfo
Certification Facet Type={http://im.ca.com/certifications/snmp}IfXTableMib
Polled Metrics(36)
Polled Metrics(36)
{http://im.ca.com/normalizer}NormalizedPortInfo.Availability
{http://im.ca.com/normalizer}NormalizedPortInfo.AvgInboundPacketRateforInterface
{http://im.ca.com/normalizer}NormalizedPortInfo.AvgOutboundPacketRateforInterface
{http://im.ca.com/normalizer}NormalizedPortInfo.Bits
{http://im.ca.com/normalizer}NormalizedPortInfo.BitsIn
{http://im.ca.com/normalizer}NormalizedPortInfo.BitsOut
{http://im.ca.com/normalizer}NormalizedPortInfo.BitsPerSecond
{http://im.ca.com/normalizer}NormalizedPortInfo.BitsPerSecondIn
{http://im.ca.com/normalizer}NormalizedPortInfo.BitsPerSecondOut
{http://im.ca.com/normalizer}NormalizedPortInfo.Discards
{http://im.ca.com/normalizer}NormalizedPortInfo.DiscardsIn
{http://im.ca.com/normalizer}NormalizedPortInfo.DiscardsOut
{http://im.ca.com/normalizer}NormalizedPortInfo.Errors
{http://im.ca.com/normalizer}NormalizedPortInfo.ErrorsIn
{http://im.ca.com/normalizer}NormalizedPortInfo.ErrorsOut
{http://im.ca.com/normalizer}NormalizedPortInfo.Nonunicast
{http://im.ca.com/normalizer}NormalizedPortInfo.NonunicastIn
{http://im.ca.com/normalizer}NormalizedPortInfo.NonunicastOut
{http://im.ca.com/normalizer}NormalizedPortInfo.OverrunErrors
{http://im.ca.com/normalizer}NormalizedPortInfo.PacketsDroppedGiants
{http://im.ca.com/normalizer}NormalizedPortInfo.PacketsDroppedRunts
{http://im.ca.com/normalizer}NormalizedPortInfo.PctCollisionsOut
{http://im.ca.com/normalizer}NormalizedPortInfo.PctDiscards
{http://im.ca.com/normalizer}NormalizedPortInfo.PctDiscardsIn
{http://im.ca.com/normalizer}NormalizedPortInfo.PctDiscardsOut
{http://im.ca.com/normalizer}NormalizedPortInfo.PctErrors
{http://im.ca.com/normalizer}NormalizedPortInfo.PctErrorsIn
{http://im.ca.com/normalizer}NormalizedPortInfo.PctErrorsOut
{http://im.ca.com/normalizer}NormalizedPortInfo.QueueDropsIn
{http://im.ca.com/normalizer}NormalizedPortInfo.QueueDropsOut
{http://im.ca.com/normalizer}NormalizedPortInfo.Unicast
{http://im.ca.com/normalizer}NormalizedPortInfo.UnicastIn
{http://im.ca.com/normalizer}NormalizedPortInfo.UnicastOut
{http://im.ca.com/normalizer}NormalizedPortInfo.Utilization
{http://im.ca.com/normalizer}NormalizedPortInfo.UtilizationIn
{http://im.ca.com/normalizer}NormalizedPortInfo.UtilizationOut
PollingConfig's DcmID=DC_HOST:DCM_ID
Polled Items(44)
Additionally, when looking at dcdebug Detailed Poll Logging, for the filtered metrics, the "Poll Response after data processing" will show NULL for the filtered metrics.
Example:
DCMResponseVariable [name={http://im.ca.com/normalizer}NormalizedPortInfo.UtilizationOut, value=NULL ]