This post will go over the second scenario for the ThousandEyes lab. To see all the posts in this series expand the box below.
ThousandEyes Walkthrough Table of Contents
- Part 1 – The What and the Why
- Part 2 – Lab build
- Part 3 – Enterprise and Endpoint Agent Installs
- Part 4.1 – SNMP Monitoring
- Part 4.2 – Scenarios and Test Types
- Part 4.3.1 – Scenario 1 – Enterprise agent to agent test configuration
- Part 4.3.2 – Scenario 2 – Enterprise DNS test configuration <–You Are Here
- Part 4.3.3 – Scenario 3 – Enterprise and Endpoint HTTP test configuration (Coming soon)
- Part 4.3.4 – Scenario 4 – Enterprise Page Load test configuration (Coming less soon)
- Part 4.3.5 – Scenario 5 – Enterprise Transaction test configuration and Endpoint Agent Browser Settings (Coming more less soon)
- Part 4.4+ – Details TBD
There are some behind-the-scenes posts that go into more detail on how and why I took the approach that I did. Those can be found here:
- Behind the Scenes – The Lab Build
- Ok, there’s only one so far, but I plan to add more where it makes sense.
Scenario 2
Scenario: It’s known that critical applications are dependent on other network services, but there is a concern that the underlying services aren’t able to support the applications.
Technical requirements: DNS has been identified as a critical service that other applications are dependent on. The CML.LAB domain must be monitored for availability and performance.
All of the scenario information can be found in this post: https://www.mytechgnome.com/2022/08/thousandeyes-walkthrough-42-scenarios.html
This scenario provides a few options for tests. An agent-to-server test could be used, but those tests don’t give DNS-specific info. Also, DNS could use UDP, and agent-to-server tests do not support UDP. A DNS Server test would check for DNS server connectivity, and identify if a change was made to a DNS record. That meets the objective of the scenario, so that’s the test we’ll set up.
Create an Enterprise DNS Server test
- Log in to ThousandEyes (I presume this skill has been mastered by now)
- On the left side, expand the menu, then click on Cloud and Enterprise Agents to expand that list, and then click Test Settings
- Click Add New Test.
- This will be a DNS Server test. Click DNS for the Layer, and then DNS Server for the Test Type
- Enter a name for the test
- Under Basic Configuration, in the Domain field enter cml.lab
- Leave the record options as default, IN and A
- NOTE: This is an internal domain that can’t be resolved by the ThousandEyes cloud. It will show a warning that it is unable to resolve the target. That warning can be ignored.
- As before, set the interval to 30 minutes to reduce the test load
- In the Agents field, select all the enterprise agents deployed
- Enter the lab DNS server IP in the DNS Servers field: 10.133.100.10
- Uncheck the Enable box for alerts
- When complete it should look like this:
- Click Create New Test
This will create the new test, and it will start running right away. Just like the agent-to-agent tests, this test can be disabled to save test units if it’s not being used.