Difficulty: Beginner
Estimated Time: 20 minutes

The training environment used in this course is made up of 5 machines: host01, host02, host03, host04, and host05. These serve the purposes of a utility machine to run scripts from, a load balancer, and three webservers.

The environment is started as soon as you open the Hands-On section. In this staging version, Ansible runs to install everything.

In this exercise we are going to look at how Datadog is configured on .

Note: In this staging of the Katacoda scenario, startup will take 3 minutes or so. When we go live this should drop to no more than 20 seconds

Now that we know how the agent is configured on each machine, let's move on and look at some dashboards.

About the Training Environment

Getting Started

  1. Click on the third tab on the right to open the terminal on the first web server.
  2. Navigate to the /etc/datadog-agent directory. cd /etc/datadog-agent
    This is where you can find the configuration files for the Datadog agent.
  3. Take a look at the datadog.yaml file using the following command: sudo less datadog.yaml
    At the top of the file you can see that the API Key is configured.
    A little further down, tags are configured. You should definitely take advantage of tags to make it easier to find the services you are monitoring.
  4. Press the letter Q to quit less and navigate to the /etc/datadog-agent/conf.d/couchbase.d directory. List the contents of the directory. cd /etc/datadog-agent/conf.d/couchbase.d;ls
    We are not using couchbase in this environment. Each supported agent-side integration has a directory, a conf.yaml.example file, and sometimes an auto_conf.yaml file. If there were a properly configured conf.yaml file in this directory, we would be monitoring couchbase.
  5. Navigate to the /etc/datadog-agent/conf.d/apache.d directory. List the contents of the directory. You can use the command cd /etc/datadog-agent/conf.d/apache.d;ls
    We are using apache httpd on this virtual machine. We could have customized the configuration further if we wanted, but the defaults are usually good for most users.
  6. Look at the contents of conf.yaml and conf.yaml.example.
    Notice that we only have to specify the options that we need
  7. See if you can identify how the other machines are configured. Each has a tab opened so you can easily take a look.
host02 (LB)
host03 (web)
host04 (web)
host05 (web)