When it comes to core DDI monitoring, the world‘s largest organizations turn towards TCPWave. With over 1490 REST API calls, the TCPWave IPAM stands apart in today‘s tech-savvy automation industry. TCPWave‘s customers need not purchase a separate add-on to monitor their DDI infrastructure. The TCPWave IPAM monitors the DDI ecosystem for various kinds of thresholds, problems, security breaches, misconfigurations, overloaded data links, sluggish response times, etc. The anycast monitoring goes one step further with an insight into the backbone routing infrastructure. Leveraging the TCPWave IPAM, the customers can monitor the availability, uptime, and response time of every DDI remote on the network. The embedded reporting engine derives various valuable monitoring metrics so that the customer‘s DDI architects and engineers can quickly identify the alerting trends and take the appropriate corrective actions.
The DNS and DHCP network services on the remotes, the transport layer that communicates with the management layer, the DNS and DHCP response times, availability, replication over the wide-area network, performance of the web server and the response time of the web server are some of the key components that need constant monitoring to ensure a smooth DDI availability and functionality. Today‘s mission-critical application infrastructure needs a monitoring framework that can assimilate the core application synthetics combined with deep DDI visibility. The idea of a robust monitoring engine is to detect and alert on various thresholds so that corrective action can be taken in a timely fashion. A prompt response taken by the DDI administrator is critical to the time taken to resolve a potential DDI outage. To understand how mission-critical applications and end-users experience the applications, a powerful monitoring engine with DDI as a focal point is required. That is exactly what TCPWave delivers to its customers.
The TCPWave IPAM provides a DDI administrator with numerous screens to configure and monitor the thresholds. The monitoring engine does a periodic collection of the pre-defined and pre-configured thresholds. Some of the key performance indicators are also used in the performance charts. The configuration policy checks, that are performed periodically also alert the monitoring engine if any configuration mismatch is detected. The threshold breaches are transformed into notifications by the notifications engine. Properly worded alerts, so that an entry-level network operator can understand what to do, are embedded into the notifications engine. The alerts quickly correlate how the DDI performance and the network performance can impact the business transactions and the end-user experience.
The TCPWave IPAM provides a robust monitoring framework with alerting that can be visualized easily using the DDI management user interface. The alerts can be sorted chronologically. A set of filters can be applied to the alerts so that the customer‘s network architects can perform event correlation analysis based on the sequence of events or alerts. The custom filtered and sorted alerts can also be downloaded into an excel spreadsheet. The TCPWave monitoring framework has smart intelligence embedded in it. For example, if a TCPWave DDI remote is powered down for scheduled maintenance, it would not flood the fault management systems with dozens of redundant alerts. If the remote is not reachable over the network, there would be one overall alert about it. The application-level alerts would be suppressed at that point since the remote is powered off or isolated from the network. The monitoring design goes one step further and provides customized alerting on specific alerts so that a set of application owners would know if the DDI infrastructure is causing a problem. For example, the SSL certificates management team can subscribe and get a specific notification when the web server certificate is due for renewal. The TCPWave CLI framework also provides a list of alerts and the monitoring settings for a group of DDI devices or a single remote.
At TCPWave, we do understand that the end-user experience is extremely critical to business performance. As modern enterprises keep changing their network topologies, the overall control and the management of a seamless DDI infrastructure has a growing set of variables. The traditional applications that used to be present on-prem have changed their hosting platform to the cloud. In today‘s world, the enterprise's employees access various applications from various remote locations. Therefore, the availability of the mission-critical DNS and DHCP services are critical for the employee‘s productivity. TCPWave‘s monitoring design considers these factors carefully. The monitoring framework is engineered so that the DDI remotes perform self-monitoring and report the statistics to the upstream monitoring engine that is running on the TCPWave IPAM. This constitutes the distributed self-monitoring model. The second model is in the opposite direction where the DDI managers centrally check the DDI remotes for a different set of monitoring thresholds.
This distributed monitoring model ensures that a single device does not get overwhelmed to perform enterprise-grade monitoring. The response time for the APIs to manage the DNS entries is extremely critical to various cloud and container orchestrators. The TCPWave IPAM performs a enterprise-grade monitoring while providing a millisecond response time to the provisioning ecosystem which comprises of various cloud and container management systems. The fault management engineering combined with a correlation analysis done by the reporting engine are designed in the core TCPWave IPAM fabric to provide a 100% DDI SLA for your enterprise.