Infra questions

Question 1

How long do we store metrics for?

Answer 1

We retain all of our metrics for 15 months

Question 2

Can I automate the build of dashboards and monitors?

Answer 2

Yes - you can use our API alongside tools like terraform to automate builds

Question 3

Do you deploy the agent as a sidecar for my Kubernetes Cluster?

Answer 3

No - it’s deployed as a daemonset, therefore one agent per host/node

Question 4

How often do we receive metrics from API crawlers?

Answer 4

For cloud - around 10 minutes, which is the same interval you’d experience in cloud native tools.

Question 5

Do we need the Agent?Or can we just configure through API

Answer 5

Since the APIs collect metrics on a 10-15 min interval, to get more granular metrics AND quicker metrics, you should get the Agent, because the agent collects every 15 seconds…Why would you NOT want the agent?

Question 6

Where is my data stored?

Answer 6

We are fully hosted in the cloud, so in multiple cloud instances (AWS, Azure, GCP, also in the EU. Mostly in USA.

Question 7

Do you offer on-prem hostings?

Answer 7

No.

Question 8

How could I get more advanced metrics from RDS?

Answer 8

Deploy the agent to an ec2 instance on the same security group as the database - you can hook into the rds like a regular DB

Question 9

Can I automate setting up multiple AWS accounts rather than manually in the UI?

Answer 9

Yes, using terraform, API, or cloudformation

Question 11

Any community dashboards?

Answer 11

No. But we have all types of dashboards and it is very easy to customize your own

Question 12

Can I convert grafana dashboards into DD so I dont have to recreate?

Answer 12

No

Question 13

Can I trigger changes on my infrastructure when an alert goes off?

Answer 13

Not directly, but we can trigger a webhook to allow a client to trigger a script based on the web hook. We also have AWS Automation and Kubernetes to autoscale

Question 14

Will I see Watchdog alerts right away?

Answer 14

No, it can take anywhere from 2-6 weeks. Watchdog needs to collect data in order to start making assumptions. The more data it has, the better

Question 15

Can I silence alerts periodically?

Answer 15

Yes, we can manage downtime in monitors easily

Question 16

How long does it take to set up Communcation integrations?

Answer 16

With any supported tech stack, very quickly, but can depend

Question 17

What If I have to completely seperate my data based on teams?

Answer 17

We could spin up multi-org environments, or seperate DD instances

Question 18

Is RBAC supported?

Answer 18

Yes, for logs and dashboards

Question 19

Do you use monitor netflow? (e.g. monitoring the flow between devices such as routers/firewalls

Answer 19

Yes, in public beta

Question 20

Can you support hybrid envrionments?

Answer 20

Yes

Question 21

Support serverless?

Answer 21

Yes - theres a Serverless page under infrastructure to show AWS lambdas and AWS serverless

Question 22

How often do live containers get updated?

Answer 22

2 second buffer period

Question 23

Whats the agent overhead?

Answer 23

Depends… .08%-3% CPU image

Question 24

If a client is running AWS ECS on Fargate, do they deploy the agent as a sidecar using Docker within the task definition?

Answer 24

Yes

Question 25

Do I have to use Helm to deploy the agent in a Kubernetes environment?

Answer 25

Nope. We also provide YAML manifests for required resources

Question 26

Can I see container health information beyond the 36 hours available in Live view?

Answer 26

Yes. Docker, Kubernetes, Chhecks/Integrations retain container info for the standard 15 months

Question 27

My K8s is epehemeral

Answer 27

Datadog can provide insights into the entire lifecycle of pods, including observing when they terminate. We can also capture real time data on CPU and memory util. of pods

Question 28

My servers are ephemeral

Answer 28

You can use a metric monitor on the system uptime metric to address this. This metric is an ever increasing timer which resets to 0 when the host starts. You can use diff() function with the metric to distinguise between a new server and a rebooted server