EfficientIP DDI Observability Center Demo

Introduction

0:11
We will now demo the DDI Observability Center.

0:14
We’ll start by opening the main dashboard.

DDI Observability Center Dashboard Overview

0:16
The dashboard shows a number of interesting metrics, such as the amount of queries per second and indications of the load on the DNS system.

0:24
It also displays the average recursion time for the different percentile buckets.

0:29
We can see that 90% of the requests have been answered in around 260 milliseconds or less.

0:36
The dashboard also provides visibility into the types of errors detected, such as NXdomain errors.

0:42
A more detailed analysis is available on the next page.

Global Statistics Dashboard

0:47
The global statistics page provides additional details about DNS queries.

0:53
It shows how the volume of queries and the cache hit ratio evolve over time.

0:58
We can also see how many queries were completed successfully and how many failed.

1:01
The dashboard displays how errors are distributed across the environment.

1:03
Additional details are available regarding successful and erroneous queries.

1:13
The dashboard also shows the average packet size, query types, and average recursion time.

1:18
In this example, recursion time increased significantly during the last two days.

1:24
We will investigate the issue further.

Top Queries Dashboard

1:28
The top queries page shows the most frequently requested domain names.

1:33
It also indicates how they relate to the overall query distribution.

1:36
In this example, 86% of the queries were generated by the top 10% of domain names.

1:45
Because an increase in recursion time was detected earlier, we can continue troubleshooting using the health dashboards.

Average CPU Load Dashboard

1:54
This dashboard shows the average CPU load across the infrastructure.

1:59
The CPU load has not increased significantly, so it does not appear to be the root cause of the recursion time issue.

Server Health Dashboard

2:08
We can also verify whether one of the services has stopped and caused timeouts.

2:13
At first glance, this does not appear to be the case.

2:17
Not all services are active on every appliance.

2:21
For example, it is normal that the DNS server does not run the DHCP processor.

2:26
All services appear healthy, so we may need to investigate the network statistics of the appliances.

Network Health Dashboard

2:33
The network statistics dashboard reveals a traffic spike that appeared on the twenty-sixth.

2:37
This spike occurred before the increase in recursion time.

2:41
The dashboard also shows that two appliances are responsible for the traffic peak.

2:46
Both appliances are management and IPAM devices.

2:49
These devices should not be the root cause of the DNS performance issue.

2:53
The traffic spike should not impact DNS performance.

2:55
In this case, the observability data confirms that the DNS servers are operating normally.