When a threshold violation event originates from DX NetOps Performance Management and is forwarded to DX NetOps Spectrum, clicking the associated "NetOps Portal URL" within the Spectrum OneClick Console event details does not display the expected metric data. Instead, the linked NetOps Portal view may appear empty or incomplete for the specific metric that triggered the violation.
This behavior is by design and is the expected, out-of-the-box behavior for metrics that are not automatically monitored by default upon device discovery.
DX NetOps Performance Management typically only enables monitoring for a standard, default set of metrics when a device is first discovered. If the metric that triggered the threshold violation is outside this default set, it must be explicitly assigned for monitoring to the device post-discovery.
Without this explicit assignment, the data for that specific metric is not collected, and therefore cannot be displayed when clicking the NetOps Portal URL in Spectrum, even if a threshold is configured for it. This design prevents the collection of unnecessary data.
To resolve this issue, you must ensure that the specific metrics causing the threshold violations are explicitly assigned for monitoring on the relevant devices within DX NetOps Performance Management.
Steps to Address:
Verify Metric Assignment:
Configure NetOps Portal Views (if necessary):
Monitor for New Events:
This process ensures that you are only collecting and displaying the data that is most relevant to your specific monitoring needs, preventing the collection of unnecessary data while providing complete context for your threshold alerts.