When inspecting raw alarm attributes within DXO2 on premise, administrators may notice that the value "Custom Metric Host (Virtual)" appears as a prefix or component within the alarm_unique_id or vertex_id fields.
A common question is whether this behavior is expected and desired for on-premises deployments.
This behavior is fully expected and is a byproduct of how DXO2 handles raw alarm formatting across different deployment types (SaaS vs. On-Premises).
This payload is properly constructed and functioning exactly as designed.
No Action Required: The presence of "Custom Metric Host (Virtual)" in these fields is normal for on-premises environments, as this virtual host is responsible for emitting the metrics.