Some advisories cannot be resolved to an affected object

[jerewill-cisco]

Certain advisories cannot be resolved to a server because they are associated with a component of the server and that component inventory is not currently being imported as an inventory item. This is most likely to occur with Field Notices, but it is possible that it could occur with some other advisory type.

An example of this is FN72368 where the AffectedObjectType is memory.Unit. Because individual DIMMs are not currently being imported by the Add-On, the Moid of the AffectedObjectType cannot be resolved to it's parent server with the data available in Splunk.

In such cases, the tam.AdvisoryInstance is still available but a further search for the AffectedObjectMoid value will not return any other results.

[jerewill-cisco]

At this point, I don't believe that the additional data that would be required to resolve this limitation is worth ingesting into Splunk. If you disagree, please post here or open a discussion.