Getting Started Documentation

Question 1

How many integrations does Datadog officially have listed?

Answer 1

Over 600 (as of 02/06/2023

http://www.datadoghq.com/integrations

Question 2

How are custom integrations avilable?

Answer 2

Through the Datadog API

Question 3

Is the Agent open source?

Answer 3

Yes

Question 4

Is data living in a datacenter treated the same as data in an online service?

Answer 4

Yes

Question 5

Can you observe your logs in real-time using the Live Tail, without indexing them?

Answer 5

Yes

Question 6

How do you dynamically index logs?

Answer 6

With Filters

Question 7

What are 4 things you can do with the host map?

Answer 7

• Quickly visualize your environment
• Identify outliers
• Detect usage patterns
• Optimize resources

Question 8

What are 4 types of events that appear in event explorer?

Answer 8

• Code deployments
• Service health changes
• Configuration changes
• Monitoring alerts

Question 9

Do you have to instrument the event explorer?

Answer 9

The Event Explorer automatically gathers events collected by the Agent and installed integrations.

Question 10

What are 4 ways you can submit custom events?

Answer 10

• Datadog API
• Custom Agent checks
• DogStatsD
• Events email API

Question 11

Can you share dashboards?

Answer 11

Yes, you can share both dashboards

Question 12

Can graphs be embedded in an iframe?

Answer 12

Graphs can be embedded in an iframe. This enables you to give a 3rd party access to a live graph without also giving access to your data or any other information.

Question 13

What are monitors?

Answer 13

Monitors provide alerts and notifications based on metric thresholds, integration availability, network endpoints, and more.

Question 14

Are there different endpoints for Real User Monitoring (RUM), specifically for logs, traces, and RUM events?

Answer 14

Yes there are currently (as of 02/06/2023) 4 endpoints for Real User Monitoring (RUM) domains.

Question 15

Does Datadog contain different documentation for each site?

Answer 15

Yes and you can select the site near the top right of a documentation page.

Question 16

What amount of space and resources does the Agent take up on onset?

Answer 16

At the onset, you can expect around 0.08% CPU used on average with a disk space of roughly 830MB to 880MB.

Question 17

What are three metrics that the Datadog Agent sends to Datadog about itself, so that you can determine things like what hosts or containers have running Agents, when an Agent starts, and what version of Python it’s running?

Answer 17

METRIC: DESCRIPTION
datadog.agent.python.version: Shows a value of 1 if the Agent is reporting to Datadog. The metric is tagged with the python_version.
datadog.agent.running: Shows a value of 1 if the Agent is reporting to Datadog.
datadog.agent.started: A count sent with a value of 1 when the Agent starts (available in v6.12+).

Question 18

Depending on your platform, what are the core checks that are enabled by default that collect metrics for the Agent?

Answer 18

CPU
Disk
IO
Memory
Network
NTP
Uptime
File
Load
Docker
Winproc

Question 19

How is the Datadog agent configured on a host?

Answer 19

The Agent is configured using a YAML file

Question 20

How are configuration options set for a container’s Agent?

Answer 20

Configuration options for a container’s Agent are passed in with environment variables for example:

• DD_API_KEY for the Datadog API key
• DD_SITE for the Datadog site

Question 21

How are integrations identified on a host?

Answer 21

Through the Agent configuration file

Question 22

How are integrations identified in a containerized environment?

Answer 22

Integrations are automatically identified through Datadog’s Autodiscovery feature

Question 23

Is the Datadog Agent required to send logs and metrics to Datadog?

Answer 23

You can send Logs and Metrics through the Datadog API. However, the Agent is the recommended method to forward your data to the Datadog Platform.

Question 24

Does the Datadog Agent need to be installed to send data from any one of the many Agent based Integrations?

Answer 24

Yes

Question 25

How often does the Agent collect host data?

Answer 25

Every 15 seconds

Question 26

How do you verify the status of the Agent on a linux host?

Answer 26

sudo datadog-agent status

Question 27

How do you check if a Datadog agent is up?

Answer 27

Monitors > Check Summary >
datadog.agent.up

Question 28

How do you check if a Datadog agent’s status?

Answer 28

Monitors > Check Summary >
datadog.agent.check_status

Returns CRITICAL if an Agent check is unable to send metrics to Datadog, otherwise returns OK.

Question 29

How many system level metrics does the agent collect every 15-20 seconds?

Answer 29

75 to 100

Question 30

How do you use the Datadog UI to confirm via metrics that the Datadog agent is started?

Answer 30

Metrics > Summary and search for the metric datadog.agent.started

Question 31

How do you use the Datadog UI to confirm via metrics that the Datadog agent is running?

Answer 31

Metrics > Summary and search for the metric datadog.agent. running

Question 32

What is the filename for the agent’s main configuration file?

Answer 32

datadog.yaml

Question 33

What are the two required parameters for the agent configuration?

Answer 33

• Your Datadog API key, which is used to associate your Agent’s data with your organization
• The Datadog site (datadoghq.com)

Question 34

What is the default path for the configuration file on Ubuntu?

Answer 34

/etc/datadog-agent/datadog.yaml