System and method for applying service topology to quantifying network health metrics
An application may be hosted on a device. The application may be configured to: receive a selection of a health metric and a selection of a service topology associated with a service provided by a network to a to a subscriber device; receive configuration information for evaluating the selected health metric for the service topology; receive monitored health information from a network device; evaluate one or more health-weight products or health-weight-security products for the selected health metric and the service topology based on the received monitored health information; obtain a normalized sum of the evaluated health-weight products or the health-weight security products; compare the normalized sum to a threshold; and send an alert or initiate a fix for the service when the sum is greater than the threshold.
1. A system comprising:
an application, which is hosted on a device, configured to:
receive a selection of a health metric and a selection of a service topology associated with a service provided by a network to a subscriber device, wherein the service topology is associated with a number of pair of nodes;
receive configuration information for evaluating the selected health metric for the service topology;
receive monitored health information from a network device;
evaluate one or more health-weight products or health-weight-security products for the selected health metric and the service topology based on the received monitored health information;
obtain a health of the service score, wherein the health of the service sore is a normalized value comprising a sum of the evaluated health-weight products or the health-weight security products divided by a number of pair of nodes associated with the service;
compare the health of the service score to a threshold; and
send an alert or initiate a fix for the service when the sum is greater than the threshold.
2. The system of claim 1 , wherein the health-weight-security product includes a product of terms comprising:
a connectivity transport health of a cloud;
a first weight indicative of importance of the connectivity transport health;
a connectivity transport security health of the cloud;
a second weight indicative of importance of the connectivity transport security health;
a health of an application on the cloud;
a third weight indicative of importance of the health of the application on the cloud;
an application security health of the application on the cloud; and
a fourth weight indicative of importance of the application security health.
3. The system of claim 1 , wherein the network includes a core IP/Multi-protocol Label Switching (MPLS) network and a passive optical network (PON).
4. The system of claim 1 , wherein the service topology includes an Ethernet virtual connection (EVC) that comprises one or more operator virtual connections (OVCs).
5. The system of claim 1 , wherein the service topology includes information that specifies one or more of:
an endpoint associated with a node;
a device associated with a node;
an application associated with a node; or
a type of connection or an application flow between two nodes.
6. The system of claim 1 , wherein the service topology includes information that indicates, for a node in the service topology:
an on-net location; and
an off-net location.
7. The system of claim 1 , wherein the health-weight product includes a product of a value of health metric, included in the monitored health information, and a weight that indicates relative importance of the health metric.
8. The system of claim 7 , wherein the health-weight-security product includes a product of:
a value of a security health metric, included in the monitored health information;
a weight that indicates relative importance of the security health metric; and
the health weight product.
9. A method comprising:
receiving a selection of a health metric and a selection of a service topology associated with a service provided by a network to a subscriber device, wherein the service topology is associated with a number of pair of nodes;
receiving configuration information for evaluating the selected health metric for the service topology;
receiving monitored health information from a network device;
evaluating one or more health-weight products or health-weight-security products for the selected health metric and the service topology based on the received monitored health information;
obtaining a health of the service score, wherein the health of the service sore is a normalized value comprising a sum of the evaluated health-weight products or the health-weight security products divided by a number of pair of nodes associated with the service;
comparing the health of the service score to a threshold; and
sending an alert or initiating a fix for the service when the sum is greater than the threshold.
10. The method of claim 9 , wherein the health-weight-security product includes a product of terms comprising:
a connectivity transport health of a cloud;
a first weight indicative of importance of the connectivity transport health;
a connectivity transport security health of the cloud;
a second weight indicative of importance of the connectivity transport security health;
a health of an application on the cloud;
a third weight indicative of importance of the health of the application on the cloud;
an application security health of the application on the cloud; and
a fourth weight indicative of importance of the application security health.
11. The method of claim 9 , wherein the network includes a core IP/Multi-protocol Label Switching (MPLS) network and a passive optical network (PON).
12. The method of claim 9 , wherein the service topology includes an Ethernet virtual connection (EVC) that comprises one or more operator virtual connections (OVCs).
13. The method of claim 9 , wherein the service topology includes information that specifies one or more of:
an endpoint associated with a node;
a device associated with a node;
an application associated with a node; or
a type of connection or an application flow between two nodes.
14. The method of claim 9 , wherein the service topology includes information that indicates, for a node in the service topology:
an on-net location; and
an off-net location.
15. The method of claim 9 , wherein the health-weight product includes a product of a value of health metric, included in the monitored health information, and a weight that indicates relative importance of the health metric.
16. A non-transitory computer-readable medium comprising one or more processor executable instructions, which, when executed by one or more processors, cause the one or more processors to:
receive a selection of a health metric and a selection of a service topology associated with a service provided by a network to a subscriber device, wherein the service topology is associated with a number of pair of nodes;
receive configuration information for evaluating the selected health metric for the service topology;
receive monitored health information from an agent device;
evaluate one or more health-weight products or health-weight-security products for the selected health metric and the service topology based on the received monitored health information;
obtain a health of the service score, wherein the health of the service sore is a normalized value comprising a sum of the evaluated health-weight products or the health-weight security products divided by a number of pair of nodes associated with the service;
compare the health of the service score to a health threshold; and
send an alert or initiating a fix for the service when the sum is greater than the threshold.
17. The non-transitory computer-readable medium of claim 16 , wherein the health-weight-security product includes a product of terms comprising:
a connectivity transport health of a cloud;
a first weight indicative of importance of the connectivity transport health;
a connectivity transport security health of the cloud;
a second weight indicative of importance of the connectivity transport security health;
a health of an application on the cloud;
a third weight indicative of importance of the health of the application on the cloud;
an application security health of the application on the cloud; and
a fourth weight indicative of importance of the application security health.
18. The non-transitory computer-readable medium of claim 16 , wherein the network includes a core IP/Multi-protocol Label Switching (MPLS) network and a passive optical network (PON).
19. The non-transitory computer-readable medium of claim 16 , wherein the health-weight product includes a product of a value of health metric, included in the monitored health information, and a weight that indicates relative importance of the health metric.
20. The non-transitory computer-readable medium of claim 19 , wherein the health-weight-security product includes a product of:
a value of a security health metric, included in the monitored health information;
a weight that indicates relative importance of the security health metric; and
the health weight product.