APM/Logs (Ready)

Question 1

What is logging?

Answer 1

The collection of raw data between devices and software

Question 2

What is a log?

Answer 2

Text record what happened and when. Come in all levels of detail and complexity to track processes

Question 3

What generates logs?

Answer 3

Anything that uses technology

Question 4

Why do we need logs?

Answer 4

Logs have traditionally been used to troubleshoot

Question 5

Why tag logs?

Answer 5

Tags allow us to correlate the data across hosts, services, applications, etc

Question 6

Why collect data from logs?

Answer 6

Data can be collected to trouble shoot, build dashboards, alerts, collect/track business metrics, and feed into machine learning to proactively identify patterns/anomalies

Question 7

What is log ingestion?

Answer 7

The storing of logs in an archive

Question 8

What is log indexing?

Answer 8

The creation of a searchable collection of certain logs, made readily available

Question 9

Why ingest all logs?

Answer 9

Useful data collection and correlation, logs available as needed for reference, pattern/anomaly detection

Question 10

Why index just some logs?

Answer 10

Not all logs are needed all the time

Question 11

What happens to ingested logs?

Answer 11

Fed into live-stream, important data parsed, tagged

Question 12

How do we store ingested logs?

Answer 12

In a Datadog hosted archive, AWS or GCP

Question 13

What is log rehydration?

Answer 13

The ability to index archived logs as need

Question 14

What is Logging Without Limits?

Answer 14

The separation of ingesting and indexing logs, rehydrating from archives as based on customer need

Question 15

What is Application Performance Monitoring (APM)?

Answer 15

Actively monitoring the errors, latency, and traffic related to an application

Question 16

Difference between an application trace vs span?

Answer 16

A trace is an application process/request. A span is a single step in a trace

Question 17

An application trace shows us…

Answer 17

The time it takes to complete an application process/request

Question 18

An application span shows us…

Answer 18

The time it takes to complete a single step in an application process/request

Question 19

What do errors tell us with APM?

Answer 19

What processes are failing

Question 20

What does latency tell us with APM?

Answer 20

How long processes are taking to complete

Question 21

What does traffic tell us with APM?

Answer 21

How many requests the application gets

Question 22

Why tag application spans?

Answer 22

Tags allow us to correlate the data across hosts, services, applications, etc

Question 23

Why collect data from application spans?

Answer 23

Data can be collected to trouble shoot, build dashboards, alerts, collect/track business metrics, and feed into machine learning to proactively identify patterns/anomalies

Question 24

What is Application Code Profiling?

Answer 24

Profiling collects representative samples of all your stack traces

Question 25

What does Application Code Profiling show?

Answer 25

Which application functions (or lines of code) consume the most resources (Memory, CPU, etc)

Question 26

What is stack tracing?

Answer 26

A time-order visual (flame graph) of the processes/functions associated with an application span

Question 27

Why use code profiling?

Answer 27

Optimize the application code to improve overall application performance, minimize resource consumption

Question 28

Why tag application code profiles?

Answer 28

Tags allow us to correlate data across hosts, services, applications, etc