I like how ServiceNow IT Operations Management correlates infrastructure events and gives me useful operational context instead of just generating more alerts. It helps me see the service impact, understand dependencies through service mapping and the CMDB, and identify affected configuration items and business services. That context makes root cause analysis and impact analysis faster, and helps my team focus on resolving the actual problem rather than chasing individual alerts. I also value how discovery enriches the CMDB with infrastructure and application relationships, and how connecting monitoring data with ServiceNow ITSM and ITAM gives us a more complete operational picture and helps us respond more efficiently. The operational visibility also supports more proactive service management. Review collected by and hosted on G2.com.

I find setup moderately complex because ServiceNow IT Operations Management depends on accurate discovery, service mapping, integrations, and CMDB configuration. In large environments, it can be difficult to quickly identify why devices, relationships, or attributes are not updating as expected. When integrations exchange large payloads and a transformation fails, relationships may not map correctly, and finding the point of failure can take significant effort. I also find it complex to keep CMDB data consistent when multiple discovery sources and integrations update the same configuration item; more intuitive governance and conflict resolution would help. Review collected by and hosted on G2.com.