Before You Begin
Before you begin using Crosswork Service Health, you are recommended to be familiar with the following concepts and complete any planning and information-gathering steps:
-
Crosswork Service Health offers two levels of service monitoring - Basic and Advanced.
-
Basic Monitoring: This type of monitoring offers the option of adding up to 52,000 services and provides limited sub-service metrics, resulting in lower overall CPU usage. Additionally, the graphic map renderings are smaller compared to more detailed monitoring.
-
Advanced Monitoring: This monitoring approach allows for the addition of up to 2,000 services, resulting in higher CPU consumption, an increased number of sub-service metrics, and larger graphic map renderings.
-
-
You can monitor upto a total of 52000 services in total, that is 52000 services using Basic monitoring only or 50000 services using Basic monitoring and an additional 2000 services using Advanced monitoring.
-
Service Health uses Heuristic packages to monitor the health of the services. A Heuristic package contains what to monitor, how to compute the monitored metrics, and symptoms associated with service health degradation. The overall health of the service is determined by applying the rules from the Heuristic Package.
-
The default set of Heuristic packages provided with Service Health are called system packages and cannot be modified. Based on the rules that are defined in the system packages, Service Health uses various testing probes such as IP SLA, Y.1731, TWAMP, SR-PM, Accedian Skylight, or telemetry data to analyze the health and determine if the service meets the Service Level Agreement (SLA).
You can create a custom Heuristic package by exporting an existing package, modifying it, and then importing it back. See About Heuristic Packages.
-
Service Health works in environments with either standalone NSO or NSO deployed in the LSA configuration.
-
Extended CLI support using Service Health system device packages allows for more comprehensive service monitoring capabilities. These packages are capable of deriving exact sensor paths for metric health calculation, and can be installed as a bundle. Engage with your account team for more details regarding this.
-
Service Health can store a maximum of 50 GB of monitoring data on the Crosswork Cluster. Crosswork Network Controller will raise an alarm when this storage reaches 70% of the 50 GB available storage capacity. In case you need additional storage, you can configure external storage in the cloud using an Amazon Web Services (AWS) cloud account. See Configure Additional External Storage.