How does Netuitive Service Analyzer learn the “relationship” between service components without requiring user-defined dependency maps?
Netuitive SI provides Netuitive Service Analyzer with quality analysis data for the infrastructure components that make up a service. Each component is analyzed by Netuitive SI from three different perspectives: Availability, Performance, and Workload. This data is then processed by Netuitive Service Analyzer to self-learn and continuously adapt the correlation coefficients between service metrics. These coefficients make up the service dependencies and are used to determine service health and isolate root-cause in case of service outage.
Related Questions
- How does Netuitive Service Analyzer learn the "relationship" between service components without requiring user-defined dependency maps?
- How does Netuitive learn the "relationship" between service components without requiring user-defined dependency maps?
- With the introduction of Netuitive 5.0, what happened to Netuitive SI and Netuitive Service Analyzer?