+
+
+
+
+
+2. Installed PostgreSQL on the Vagrant machine and then installed the respective Datadog integration for that database.
+ - Added the public GPG key:
+ ```wget -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add -```
+ - Created a file with the repository address:
+ ```echo deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main | sudo tee /etc/apt/sources.list.d/postgresql.list```
+ - To install PostgreSQL I ran:
+ ```sudo apt-get update```
+ ```sudo apt-get install postgresql-9.3 postgresql-contrib-9.3```
+ - After installing PostgreSQL, I ran the following command to create a user for Datadog in the database.
+ ```create user datadog with password ‘######’;```
+3. Created a script file and a config file in order to create a custom metric and send it to Datadog servers through the Agent.
+
+
+
+After ```mymetric.py``` was created ```~/.datadog-agent/checks.d/mymetric.py``` added the following to the file:
+
+
+
+Then I created ```mymetric.yaml ~/.datadog-agent/conf.d/mymetric.yaml``` and added the code below.
+
+
+
+After I restarted the Agent.
+
+
+On the Datadog dashboard, I went to ```Metrics > Explorer```, and searched for my custom metric.
+The Agent was running the collector in intervals of 15–20 seconds.
+
+4. To change my check’s collection interval I edited the config file ```~/.datadog-agent/conf.d/mymetric.yaml``` and changed the ```min_collection_interval``` globally to the interval of 45 seconds.
+
+
+
+And restarted the Agent again.
+
+
+5. **Bonus Question:** Can you change the collection interval without modifying the Python check file you created?
+ **Answer:** Yes, the interval can be set by changing the instance description in the ```yaml``` file, like this:
+```
+ init_config:
+ min_collection_interval: 45
+ instances:
+ [{}]
+```
+
+
+To create my dashboard I used the content of this curl command:
+ ```
+ curl --location --request POST 'https://api.datadoghq.com/api/v1/dashboard' \
+ --header 'Content-Type: application/json' \
+ --header 'Cookie: DD-PSHARD=217' \
+ --header 'DD-API-KEY: xxxxxxxxxxxxxxxxxxxxxxxxxx' \
+ --header 'DD-APPLICATION-KEY: xxxxxxxxxxxxxxxxxxxxxxxxxx' \
+ --data-raw '{
+ "title": "Dev.Zarudnaya Hourly Anomalies",
+ "description": "A custom agent check configured to submit a metric named `my_metric` with a random value between 0 and 1000.",
+ "layout_type": "ordered",
+ "is_read_only": false,
+ "widgets": [
+ {
+ "definition": {
+ "type": "timeseries",
+ "title": "my metric timeseries",
+ "requests": [
+ {
+ "q": "my_metric{host:datadog.dev.zarudnaya.info}"
+ }
+ ]
+ },
+ "layout": {
+ "x": 0,
+ "y": 0,
+ "width": 4,
+ "height": 2
+ }
+ },
+ {
+ "definition": {
+ "type": "timeseries",
+ "title": "Postgres Sql Return Rows Anamolies",
+ "requests": [
+ {
+ "q": "anomalies(sum:postgresql.rows_returned{host:datadog.dev.zarudnaya.info}, '\''basic'\'', 5)"
+ }
+ ]
+ },
+ "layout": {
+ "x": 4,
+ "y": 0,
+ "width": 4,
+ "height": 2
+ }
+ },
+ {
+ "definition": {
+ "type": "timeseries",
+ "title": "Sum of my metric points per hour",
+ "requests": [
+ {
+ "q": "sum:my_metric{*}.rollup(sum, 3600)"
+ }
+ ]
+ },
+ "layout": {
+ "x": 8,
+ "y": 0,
+ "width": 4,
+ "height": 2
+ }
+ }
+ ]
+ }'
+ ```
+
+2. Once this was created, I accessed the Dashboard from the Dashboard List in the UI:
+ ##### My Hourly Timeboard
+ 
+
+3. The sum of my metric is grouped into hours (per instructions) so it did not show properly in a 5 minute time span. I expanded the time period on the widget and included a snapshot here.
+ 
+
+ [Hourly Anomalies Dashboard Link](https://p.datadoghq.com/sb/ab7cb560-3783-11ec-9ab2-da7ad0900002-6fcd0e111c4fd4be11af2203756fb0b8)
+
+4. Took a snapshot of this graph and used the @ notation to send it to myself. The email notice included a thumbnail, and also buttons that take you directly to the item in the Datadog panel.
+ 
+
+5. **Bonus Question:** What is the Anomaly graph displaying?
+ **Answer:** The Anomaly graph presents suspicious behaviour. I stressed PostgreSQL and made the tables list, thus, causing it to perform in a certain way. The graph provides a visualization of this performance as it relates to PostgreSQL.
+
+
+
+
+#### Configure the Monitor's Message:
+2. I configured the monitor message with below settings:
+
+
+#### Monitor Message Email Notifications
+3. Created different messages based on whether the monitor is in an Alert, Warning, or No Data state.
+
+#### Alert:
+
+
+#### Warning:
+
+
+#### Missing Data:
+
+
+**Bonus Question:** Since this monitor is going to alert pretty often, you don’t want to be alerted when you are out of the office. Set up two scheduled downtimes for this monitor:
+#### Downtime Settings:
+1. From Datadog dashboard ```Monitors > Manage Downtime``` clicked 'Schedule Downtime':
+
+
+
+2. Created a recurring downtime for days of the week and weekends. I used EST since this is my time zone and Datadog HQ time zone.
+#### Downtime Weekday Settings:
+
+
+#### Downtime Weekend Settings:
+
+
+
+
+3. Injected ```ddtrace``` in the ```app.py```:
+```
+from flask import Flask, render_template, request, redirect, url_for
+from flask_sqlalchemy import SQLAlchemy
+from ddtrace import tracer
+
+app = Flask(__name__)
+
+app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///db.sqlite'
+app.config['SQLALCHEMY_TRACK_MODIFICATIONS'] = False
+db = SQLAlchemy(app)
+
+class Todo(db.Model):
+ id = db.Column(db.Integer, primary_key=True)
+ title = db.Column(db.String(100))
+ complete = db.Column(db.Boolean)
+
+@app.route("/")
+def home():
+ todo_list = Todo.query.all()
+ return render_template("base.html", todo_list=todo_list)
+
+@app.route("/add", methods=["POST"])
+@tracer.wrap("flask.request", service='flask', resource="POST /add", span_type='web')
+def add():
+ title = request.form.get("title")
+ new_todo = Todo(title=title, complete=False)
+ db.session.add(new_todo)
+ db.session.commit()
+ return redirect(url_for("home"))
+
+@app.route("/update/
+
+5. In order for my Flask app on port 5000 to run I modified the agent port to 5050:
+
+
+
+My To Do App on the browser:
+
+
+APM dashboard on Datadog website:
+
+
+
+6. Created some entries in my To Do APP and it is showing on the APM Dashboard:
+
+
+
+#### Dashboard with both APM and Infrastructure Metrics:
+
+[Dashboard APM link](https://p.datadoghq.com/sb/ab7cb560-3783-11ec-9ab2-da7ad0900002-b486ce8c5579c41542cd9f0d78eed153) (Flask app was run on November, 21st. Please change the time range to 1 month to see the results)
+
+7. **Bonus Question:** What is the difference between a Service and a Resource?
+ **Answer:** Services are the building blocks of modern microservice architectures. A service groups together endpoints.
+ A resource is an action given to a service, such as a query to a database or an endpoint.
+ [Reference](https://docs.datadoghq.com/tracing/visualization/#pagetitle)
+
+
+
+## Final Question
+Datadog has been used in a lot of creative ways in the past. We’ve written some blog posts about using Datadog to monitor the NYC Subway System, Pokemon Go, and even office restroom availability!
+
+Is there anything creative you would use Datadog for?
+
+**Answer:** Datadog can be used in many creative ways ([Datadog in the wild: 5 fun projects](https://www.datadoghq.com/blog/datadog-in-the-wild-5-fun-projects/)). In this pandemic times lots of people are dependent on medical equipment. For example, medical systems could use Datadog monitoring to ensure that they are functioning correctly in case of an emergency or an unforeseen event and alert for any anomalies.
+Another example how I could use Datadog is to compare prices on different e-commerce websites and select the cheapest price. It could also help to monitor information regarding sales and items that are back in stock.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/flask-app/__pycache__/app.cpython-36.pyc b/flask-app/__pycache__/app.cpython-36.pyc
new file mode 100644
index 000000000..17d6d7b62
Binary files /dev/null and b/flask-app/__pycache__/app.cpython-36.pyc differ
diff --git a/flask-app/app.py b/flask-app/app.py
new file mode 100644
index 000000000..1a0a65f99
--- /dev/null
+++ b/flask-app/app.py
@@ -0,0 +1,47 @@
+from flask import Flask, render_template, request, redirect, url_for
+from flask_sqlalchemy import SQLAlchemy
+from ddtrace import tracer
+
+app = Flask(__name__)
+
+app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///db.sqlite'
+app.config['SQLALCHEMY_TRACK_MODIFICATIONS'] = False
+db = SQLAlchemy(app)
+
+class Todo(db.Model):
+ id = db.Column(db.Integer, primary_key=True)
+ title = db.Column(db.String(100))
+ complete = db.Column(db.Boolean)
+
+@app.route("/")
+def home():
+ todo_list = Todo.query.all()
+ return render_template("base.html", todo_list=todo_list)
+
+@app.route("/add", methods=["POST"])
+@tracer.wrap("flask.request", service='flask', resource="POST /add", span_type='web')
+def add():
+ title = request.form.get("title")
+ new_todo = Todo(title=title, complete=False)
+ db.session.add(new_todo)
+ db.session.commit()
+ return redirect(url_for("home"))
+
+@app.route("/update/
+
+ + {% for todo in todo_list %} + + {% endfor %} +
+
+
+
\ No newline at end of file
diff --git a/flask-app/venv/bin/Activate.ps1 b/flask-app/venv/bin/Activate.ps1
new file mode 100644
index 000000000..5b9adb2b7
--- /dev/null
+++ b/flask-app/venv/bin/Activate.ps1
@@ -0,0 +1,231 @@
+<#
+.Synopsis
+Activate a Python virtual environment for the current Powershell session.
+
+.Description
+Pushes the python executable for a virtual environment to the front of the
+$Env:PATH environment variable and sets the prompt to signify that you are
+in a Python virtual environment. Makes use of the command line switches as
+well as the `pyvenv.cfg` file values present in the virtual environment.
+
+.Parameter VenvDir
+Path to the directory that contains the virtual environment to activate. The
+default value for this is the parent of the directory that the Activate.ps1
+script is located within.
+
+.Parameter Prompt
+The prompt prefix to display when this virtual environment is activated. By
+default, this prompt is the name of the virtual environment folder (VenvDir)
+surrounded by parentheses and followed by a single space (ie. '(.venv) ').
+
+.Example
+Activate.ps1
+Activates the Python virtual environment that contains the Activate.ps1 script.
+
+.Example
+Activate.ps1 -Verbose
+Activates the Python virtual environment that contains the Activate.ps1 script,
+and shows extra information about the activation as it executes.
+
+.Example
+Activate.ps1 -VenvDir C:\Users\MyUser\Common\.venv
+Activates the Python virtual environment located in the specified location.
+
+.Example
+Activate.ps1 -Prompt "MyPython"
+Activates the Python virtual environment that contains the Activate.ps1 script,
+and prefixes the current prompt with the specified string (surrounded in
+parentheses) while the virtual environment is active.
+
+
+#>
+Param(
+ [Parameter(Mandatory = $false)]
+ [String]
+ $VenvDir,
+ [Parameter(Mandatory = $false)]
+ [String]
+ $Prompt
+)
+
+<# Function declarations --------------------------------------------------- #>
+
+<#
+.Synopsis
+Remove all shell session elements added by the Activate script, including the
+addition of the virtual environment's Python executable from the beginning of
+the PATH variable.
+
+.Parameter NonDestructive
+If present, do not remove this function from the global namespace for the
+session.
+
+#>
+function global:deactivate ([switch]$NonDestructive) {
+ # Revert to original values
+
+ # The prior prompt:
+ if (Test-Path -Path Function:_OLD_VIRTUAL_PROMPT) {
+ Copy-Item -Path Function:_OLD_VIRTUAL_PROMPT -Destination Function:prompt
+ Remove-Item -Path Function:_OLD_VIRTUAL_PROMPT
+ }
+
+ # The prior PYTHONHOME:
+ if (Test-Path -Path Env:_OLD_VIRTUAL_PYTHONHOME) {
+ Copy-Item -Path Env:_OLD_VIRTUAL_PYTHONHOME -Destination Env:PYTHONHOME
+ Remove-Item -Path Env:_OLD_VIRTUAL_PYTHONHOME
+ }
+
+ # The prior PATH:
+ if (Test-Path -Path Env:_OLD_VIRTUAL_PATH) {
+ Copy-Item -Path Env:_OLD_VIRTUAL_PATH -Destination Env:PATH
+ Remove-Item -Path Env:_OLD_VIRTUAL_PATH
+ }
+
+ # Just remove the VIRTUAL_ENV altogether:
+ if (Test-Path -Path Env:VIRTUAL_ENV) {
+ Remove-Item -Path env:VIRTUAL_ENV
+ }
+
+ # Just remove the _PYTHON_VENV_PROMPT_PREFIX altogether:
+ if (Get-Variable -Name "_PYTHON_VENV_PROMPT_PREFIX" -ErrorAction SilentlyContinue) {
+ Remove-Variable -Name _PYTHON_VENV_PROMPT_PREFIX -Scope Global -Force
+ }
+
+ # Leave deactivate function in the global namespace if requested:
+ if (-not $NonDestructive) {
+ Remove-Item -Path function:deactivate
+ }
+}
+
+<#
+.Description
+Get-PyVenvConfig parses the values from the pyvenv.cfg file located in the
+given folder, and returns them in a map.
+
+For each line in the pyvenv.cfg file, if that line can be parsed into exactly
+two strings separated by `=` (with any amount of whitespace surrounding the =)
+then it is considered a `key = value` line. The left hand string is the key,
+the right hand is the value.
+
+If the value starts with a `'` or a `"` then the first and last character is
+stripped from the value before being captured.
+
+.Parameter ConfigDir
+Path to the directory that contains the `pyvenv.cfg` file.
+#>
+function Get-PyVenvConfig(
+ [String]
+ $ConfigDir
+) {
+ Write-Verbose "Given ConfigDir=$ConfigDir, obtain values in pyvenv.cfg"
+
+ # Ensure the file exists, and issue a warning if it doesn't (but still allow the function to continue).
+ $pyvenvConfigPath = Join-Path -Resolve -Path $ConfigDir -ChildPath 'pyvenv.cfg' -ErrorAction Continue
+
+ # An empty map will be returned if no config file is found.
+ $pyvenvConfig = @{ }
+
+ if ($pyvenvConfigPath) {
+
+ Write-Verbose "File exists, parse `key = value` lines"
+ $pyvenvConfigContent = Get-Content -Path $pyvenvConfigPath
+
+ $pyvenvConfigContent | ForEach-Object {
+ $keyval = $PSItem -split "\s*=\s*", 2
+ if ($keyval[0] -and $keyval[1]) {
+ $val = $keyval[1]
+
+ # Remove extraneous quotations around a string value.
+ if ("'""".Contains($val.Substring(0,1))) {
+ $val = $val.Substring(1, $val.Length - 2)
+ }
+
+ $pyvenvConfig[$keyval[0]] = $val
+ Write-Verbose "Adding Key: '$($keyval[0])'='$val'"
+ }
+ }
+ }
+ return $pyvenvConfig
+}
+
+
+<# Begin Activate script --------------------------------------------------- #>
+
+# Determine the containing directory of this script
+$VenvExecPath = Split-Path -Parent $MyInvocation.MyCommand.Definition
+$VenvExecDir = Get-Item -Path $VenvExecPath
+
+Write-Verbose "Activation script is located in path: '$VenvExecPath'"
+Write-Verbose "VenvExecDir Fullname: '$($VenvExecDir.FullName)"
+Write-Verbose "VenvExecDir Name: '$($VenvExecDir.Name)"
+
+# Set values required in priority: CmdLine, ConfigFile, Default
+# First, get the location of the virtual environment, it might not be
+# VenvExecDir if specified on the command line.
+if ($VenvDir) {
+ Write-Verbose "VenvDir given as parameter, using '$VenvDir' to determine values"
+} else {
+ Write-Verbose "VenvDir not given as a parameter, using parent directory name as VenvDir."
+ $VenvDir = $VenvExecDir.Parent.FullName.TrimEnd("\\/")
+ $VenvDir = $VenvDir.Insert($VenvDir.Length, "/")
+ Write-Verbose "VenvDir=$VenvDir"
+}
+
+# Next, read the `pyvenv.cfg` file to determine any required value such
+# as `prompt`.
+$pyvenvCfg = Get-PyVenvConfig -ConfigDir $VenvDir
+
+# Next, set the prompt from the command line, or the config file, or
+# just use the name of the virtual environment folder.
+if ($Prompt) {
+ Write-Verbose "Prompt specified as argument, using '$Prompt'"
+} else {
+ Write-Verbose "Prompt not specified as argument to script, checking pyvenv.cfg value"
+ if ($pyvenvCfg -and $pyvenvCfg['prompt']) {
+ Write-Verbose " Setting based on value in pyvenv.cfg='$($pyvenvCfg['prompt'])'"
+ $Prompt = $pyvenvCfg['prompt'];
+ }
+ else {
+ Write-Verbose " Setting prompt based on parent's directory's name. (Is the directory name passed to venv module when creating the virutal environment)"
+ Write-Verbose " Got leaf-name of $VenvDir='$(Split-Path -Path $venvDir -Leaf)'"
+ $Prompt = Split-Path -Path $venvDir -Leaf
+ }
+}
+
+Write-Verbose "Prompt = '$Prompt'"
+Write-Verbose "VenvDir='$VenvDir'"
+
+# Deactivate any currently active virtual environment, but leave the
+# deactivate function in place.
+deactivate -nondestructive
+
+# Now set the environment variable VIRTUAL_ENV, used by many tools to determine
+# that there is an activated venv.
+$env:VIRTUAL_ENV = $VenvDir
+
+if (-not $Env:VIRTUAL_ENV_DISABLE_PROMPT) {
+
+ Write-Verbose "Setting prompt to '$Prompt'"
+
+ # Set the prompt to include the env name
+ # Make sure _OLD_VIRTUAL_PROMPT is global
+ function global:_OLD_VIRTUAL_PROMPT { "" }
+ Copy-Item -Path function:prompt -Destination function:_OLD_VIRTUAL_PROMPT
+ New-Variable -Name _PYTHON_VENV_PROMPT_PREFIX -Description "Python virtual environment prompt prefix" -Scope Global -Option ReadOnly -Visibility Public -Value $Prompt
+
+ function global:prompt {
+ Write-Host -NoNewline -ForegroundColor Green "($_PYTHON_VENV_PROMPT_PREFIX) "
+ _OLD_VIRTUAL_PROMPT
+ }
+}
+
+# Clear PYTHONHOME
+if (Test-Path -Path Env:PYTHONHOME) {
+ Copy-Item -Path Env:PYTHONHOME -Destination Env:_OLD_VIRTUAL_PYTHONHOME
+ Remove-Item -Path Env:PYTHONHOME
+}
+
+# Add the venv to the PATH
+Copy-Item -Path Env:PATH -Destination Env:_OLD_VIRTUAL_PATH
+$Env:PATH = "$VenvExecDir$([System.IO.Path]::PathSeparator)$Env:PATH"
diff --git a/flask-app/venv/bin/activate b/flask-app/venv/bin/activate
new file mode 100644
index 000000000..83c50e639
--- /dev/null
+++ b/flask-app/venv/bin/activate
@@ -0,0 +1,76 @@
+# This file must be used with "source bin/activate" *from bash*
+# you cannot run it directly
+
+deactivate () {
+ # reset old environment variables
+ if [ -n "${_OLD_VIRTUAL_PATH:-}" ] ; then
+ PATH="${_OLD_VIRTUAL_PATH:-}"
+ export PATH
+ unset _OLD_VIRTUAL_PATH
+ fi
+ if [ -n "${_OLD_VIRTUAL_PYTHONHOME:-}" ] ; then
+ PYTHONHOME="${_OLD_VIRTUAL_PYTHONHOME:-}"
+ export PYTHONHOME
+ unset _OLD_VIRTUAL_PYTHONHOME
+ fi
+
+ # This should detect bash and zsh, which have a hash command that must
+ # be called to get it to forget past commands. Without forgetting
+ # past commands the $PATH changes we made may not be respected
+ if [ -n "${BASH:-}" -o -n "${ZSH_VERSION:-}" ] ; then
+ hash -r
+ fi
+
+ if [ -n "${_OLD_VIRTUAL_PS1:-}" ] ; then
+ PS1="${_OLD_VIRTUAL_PS1:-}"
+ export PS1
+ unset _OLD_VIRTUAL_PS1
+ fi
+
+ unset VIRTUAL_ENV
+ if [ ! "${1:-}" = "nondestructive" ] ; then
+ # Self destruct!
+ unset -f deactivate
+ fi
+}
+
+# unset irrelevant variables
+deactivate nondestructive
+
+VIRTUAL_ENV="/Users/Kate/Datadog/myapp/venv"
+export VIRTUAL_ENV
+
+_OLD_VIRTUAL_PATH="$PATH"
+PATH="$VIRTUAL_ENV/bin:$PATH"
+export PATH
+
+# unset PYTHONHOME if set
+# this will fail if PYTHONHOME is set to the empty string (which is bad anyway)
+# could use `if (set -u; : $PYTHONHOME) ;` in bash
+if [ -n "${PYTHONHOME:-}" ] ; then
+ _OLD_VIRTUAL_PYTHONHOME="${PYTHONHOME:-}"
+ unset PYTHONHOME
+fi
+
+if [ -z "${VIRTUAL_ENV_DISABLE_PROMPT:-}" ] ; then
+ _OLD_VIRTUAL_PS1="${PS1:-}"
+ if [ "x(venv) " != x ] ; then
+ PS1="(venv) ${PS1:-}"
+ else
+ if [ "`basename \"$VIRTUAL_ENV\"`" = "__" ] ; then
+ # special case for Aspen magic directories
+ # see http://www.zetadev.com/software/aspen/
+ PS1="[`basename \`dirname \"$VIRTUAL_ENV\"\``] $PS1"
+ else
+ PS1="(`basename \"$VIRTUAL_ENV\"`)$PS1"
+ fi
+ fi
+ export PS1
+fi
+
+# This should detect bash and zsh, which have a hash command that must
+# be called to get it to forget past commands. Without forgetting
+# past commands the $PATH changes we made may not be respected
+if [ -n "${BASH:-}" -o -n "${ZSH_VERSION:-}" ] ; then
+ hash -r
+fi
diff --git a/flask-app/venv/bin/activate.csh b/flask-app/venv/bin/activate.csh
new file mode 100644
index 000000000..b8f8cd76f
--- /dev/null
+++ b/flask-app/venv/bin/activate.csh
@@ -0,0 +1,37 @@
+# This file must be used with "source bin/activate.csh" *from csh*.
+# You cannot run it directly.
+# Created by Davide Di Blasi To Do App
+ + + ++ + {% for todo in todo_list %} + + {% endfor %} +
-
+ {% for user in users %}
+
- {{ user.username }} + {% endfor %} +
-
+_PATCH_ON_IMPORT = {
+ "aiohttp": ("aiohttp",),
+ "aiobotocore": ("aiobotocore",),
+ "celery": ("celery",),
+ "flask": ("flask",),
+ "gevent": ("gevent",),
+ "requests": ("requests",),
+ "botocore": ("botocore",),
+ "elasticsearch": (
+ "elasticsearch",
+ "elasticsearch2",
+ "elasticsearch5",
+ "elasticsearch6",
+ "elasticsearch7",
+ ),
+ "pynamodb": ("pynamodb",),
+}
+
+
+class PatchException(Exception):
+ """Wraps regular `Exception` class when patching modules"""
+
+ pass
+
+
+class ModuleNotFoundException(PatchException):
+ pass
+
+
+def _on_import_factory(module, raise_errors=True):
+ # type: (str, bool) -> Callable[[Any], None]
+ """Factory to create an import hook for the provided module name"""
+
+ def on_import(hook):
+ # Import and patch module
+ path = "ddtrace.contrib.%s" % module
+ try:
+ imported_module = importlib.import_module(path)
+ except ImportError:
+ if raise_errors:
+ raise
+ log.error("failed to import ddtrace module %r when patching on import", path, exc_info=True)
+ else:
+ imported_module.patch()
+
+ return on_import
+
+
+def patch_all(**patch_modules):
+ # type: (bool) -> None
+ """Automatically patches all available modules.
+
+ In addition to ``patch_modules``, an override can be specified via an
+ environment variable, ``DD_TRACE_
This is a doc
') +This is a doc
') +,, and