You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
Brett Langdon fde203dbc8
better commands and copy
7 years ago
..
README.md Add start to DASH workshop scenario 7 years ago
background.sh use .env file for adding errors and latency 7 years ago
finish.md Add start to DASH workshop scenario 7 years ago
foreground.sh add aliases 7 years ago
index.json Update steps to remove custom dashboards 7 years ago
intro.md add background.sh 7 years ago
step_1.md add more steps 7 years ago
step_2.md add aliases 7 years ago
step_3.md make step 3 easier 7 years ago
step_3_background.sh make step 3 easier 7 years ago
step_4.md fix code 7 years ago
step_5.md automatically enable agent settings 7 years ago
step_5_background.sh fix env variable 7 years ago
step_6.md fix copy 7 years ago
step_6_background.sh shuffle steps around 7 years ago
step_7.md add step 7 7 years ago
step_8.md fix copy 7 years ago
step_8_background.sh shuffle steps around 7 years ago
step_9.md fix steps 7 years ago
step_10.md better commands and copy 7 years ago
step_11.md better commands and copy 7 years ago

README.md

Pinpointing Microservice Bottlenecks in Python with Datadog APM

https://www.dashcon.io/workshops/pinpointing-microservice-bottlenecks-in-python-with-datadog-apm/

As software moves to microservices and containers, the need for better tooling to debug our systems grows.

In this workshop, we'll introduce distributed tracing as a method to gain visibility and insight into these distributed applications.

Traces allow us to see units of work, as they pass across our subsystems. By incorporating traces with logs and metrics, we can see performance bottlenecks, verify legacy system changes, and deploy confidently into complex environments.

We'll instrument a few Python microservices with the Datadog Agent, and see how distributed traces can be used in the real world, to get better insight into the health of your systems.