npm - @itentialopensource/adapter-datadog - Versions diffs - 0.7.4 → 0.8.0 - Mend

@itentialopensource/adapter-datadog 0.7.4 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (18) hide show

package/CHANGELOG.md +8 -0
package/PROPERTIES.md +5 -0
package/README.md +60 -63
package/SYSTEMINFO.md +8 -1
package/TAB1.md +5 -0
package/TAB2.md +45 -3017
package/metadata.json +19 -5
package/package.json +2 -4
package/propertiesSchema.json +5 -0
package/refs?service=git-upload-pack +0 -0
package/report/adapter-openapi.json +146 -146
package/report/adapterInfo.json +4 -4
package/report/sample-openapi.json +156 -0
package/report/updateReport1714079379399.json +120 -0
package/sampleProperties.json +1 -0
package/test/integration/adapterTestIntegration.js +1 -0
package/test/unit/adapterTestUnit.js +1 -3
/package/report/{adapter-openapi.yaml → sample-openapi.yaml} +0 -0

package/TAB2.md CHANGED Viewed

@@ -2,375 +2,56 @@
 ## Table of Contents
-  - [Getting Started](#getting-started)
-    - [Helpful Background Information](#helpful-background-information)
-    - [Prerequisites](#prerequisites)
-    - [How to Install](#how-to-install)
-    - [Testing](#testing)
-  - [Configuration](#configuration)
-    - [Example Properties](#example-properties)
-    - [Connection Properties](#connection-properties)
-    - [Authentication Properties](#authentication-properties)
-    - [Healthcheck Properties](#healthcheck-properties)
-    - [Request Properties](#request-properties)
-    - [SSL Properties](#ssl-properties)
-    - [Throttle Properties](#throttle-properties)
-    - [Proxy Properties](#proxy-properties)
-    - [Mongo Properties](#mongo-properties)
-    - [Device Broker Properties](#device-broker-properties)
-  - [Using this Adapter](#using-this-adapter)
-    - [Generic Adapter Calls](#generic-adapter-calls)
-    - [Adapter Cache Calls](#adapter-cache-calls)
-    - [Adapter Broker Calls](#adapter-broker-calls)
-    - [Specific Adapter Calls](#specific-adapter-calls)
-    - [ARGUMENTS](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [ARGUMENTS](#arguments)
-    - [Arguments](#arguments)
-    - [ARGUMENTS](#arguments)
-    - [ARGUMENTS](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [ARGUMENTS](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [ARGUMENTS](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [ARGUMENTS](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Multipart Form-Data](#multipart-form-data)
-    - [XML Body](#xml-body)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Arguments](#arguments)
-    - [Authentication](#authentication)
-  - [Additional Information](#additional-information)
-    - [Enhancements](#enhancements)
-    - [Contributing](#contributing)
-    - [Helpful Links](#helpful-links)
-    - [Node Scripts](#node-scripts)
-  - [Troubleshoot](#troubleshoot)
-    - [Connectivity Issues](#connectivity-issues)
-    - [Functional Issues](#functional-issues)
+  - [Specific Adapter Information](#specific-adapter-information)
+    - [Authentication](#authentication)
+    - [Sample Properties](#sample-properties)
+    - [Swagger](#swagger)
+  - [Generic Adapter Information](#generic-adapter-information)
-## Getting Started
-These instructions will help you get a copy of the project on your local machine for development and testing. Reading this section is also helpful for deployments as it provides you with pertinent information on prerequisites and properties.
-### Helpful Background Information
-There is <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter documentation available on the Itential Documentation Site</a>. This documentation includes information and examples that are helpful for:
-```text
-Authentication
-IAP Service Instance Configuration
-Code Files
-Endpoint Configuration (Action & Schema)
-Mock Data
-Adapter Generic Methods
-Headers
-Security
-Linting and Testing
-Build an Adapter
-Troubleshooting an Adapter
-```
-Others will be added over time.
-Want to build a new adapter? Use the <a href="https://adapters.itential.io" target="_blank">Itential Adapter Builder</a>
-### Prerequisites
-The following is a list of required packages for installation on the system the adapter will run on:
-```text
-Node.js
-npm
-Git
-```
-The following list of packages are required for Itential opensource adapters or custom adapters that have been built utilizing the Itential Adapter Builder. You can install these packages by running npm install inside the adapter directory.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Package</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">@itentialopensource/adapter-utils</td>
-    <td style="padding:15px">Runtime library classes for all adapters;  includes request handling, connection, authentication throttling, and translation.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">ajv</td>
-    <td style="padding:15px">Required for validation of adapter properties to integrate with Datadog.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">axios</td>
-    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">commander</td>
-    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">dns-lookup-promise</td>
-    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">fs-extra</td>
-    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">mocha</td>
-    <td style="padding:15px">Testing library that is utilized by some of the node scripts that are included with the adapter.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">mocha-param</td>
-    <td style="padding:15px">Testing library that is utilized by some of the node scripts that are included with the adapter.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">mongodb</td>
-    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">nyc</td>
-    <td style="padding:15px">Testing coverage library that is utilized by some of the node scripts that are included with the adapter.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">ping</td>
-    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">readline-sync</td>
-    <td style="padding:15px">Utilized by the node script that comes with the adapter;  helps to test unit and integration functionality.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">semver</td>
-    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">winston</td>
-    <td style="padding:15px">Utilized by the node scripts that are included with the adapter; helps to build and extend the functionality.</td>
-  </tr>
-</table>
-<br>
-If you are developing and testing a custom adapter, or have testing capabilities on an Itential opensource adapter, you will need to install these packages as well.
-```text
-chai
-eslint
-eslint-config-airbnb-base
-eslint-plugin-import
-eslint-plugin-json
-testdouble
-```
-### How to Install
-1. Set up the name space location in your IAP node_modules.
-```bash
-cd /opt/pronghorn/current/node_modules (* could be in a different place)
-if the @itentialopensource directory does not exist, create it:
-    mkdir @itentialopensource
-```
-2. Clone/unzip/tar the adapter into your IAP environment.
-```bash
-cd \@itentialopensource
-git clone git@gitlab.com:\@itentialopensource/adapters/adapter-datadog
-or
-unzip adapter-datadog.zip
-or
-tar -xvf adapter-datadog.tar
-```
-3. Run the adapter install script.
-```bash
-cd adapter-datadog
-npm install
-npm run lint:errors
-npm run test
-```
-4. Restart IAP
-```bash
-systemctl restart pronghorn
-```
-5. Create an adapter service instance configuration in IAP Admin Essentials GUI
-6. Copy the properties from the sampleProperties.json and paste them into the service instance configuration in the inner/second properties field.
-7. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
-For an easier install of the adapter use npm run adapter:install, it will install the adapter in IAP. Please note that it can be dependent on where the adapter is installed and on the version of IAP so it is subject to fail. If using this, you can replace step 3-5 above with these:
-3. Install adapter dependencies and check the adapter.
-```bash
-cd adapter-datadog
-npm run adapter:install
-```
-4. Restart IAP
-```bash
-systemctl restart pronghorn
-```
-5. Change the adapter service instance configuration (host, port, credentials, etc) in IAP Admin Essentials GUI
-### Testing
-Mocha is generally used to test all Itential Opensource Adapters. There are unit tests as well as integration tests performed. Integration tests can generally be run as standalone using mock data and running the adapter in stub mode, or as integrated. When running integrated, every effort is made to prevent environmental failures, however there is still a possibility.
-#### Unit Testing
-Unit Testing includes testing basic adapter functionality as well as error conditions that are triggered in the adapter prior to any integration. There are two ways to run unit tests. The prefered method is to use the testRunner script; however, both methods are provided here.
-```bash
-node utils/testRunner --unit
-npm run test:unit
-npm run test:baseunit
-```
-To add new unit tests, edit the `test/unit/adapterTestUnit.js` file. The tests that are already in this file should provide guidance for adding additional tests.
-#### Integration Testing - Standalone
-Standalone Integration Testing requires mock data to be provided with the entities. If this data is not provided, standalone integration testing will fail. When the adapter is set to run in stub mode (setting the stub property to true), the adapter will run through its code up to the point of making the request. It will then retrieve the mock data and return that as if it had received that data as the response from Datadog. It will then translate the data so that the adapter can return the expected response to the rest of the Itential software. Standalone is the default integration test.
-Similar to unit testing, there are two ways to run integration tests. Using the testRunner script is better because it prevents you from having to edit the test script; it will also resets information after testing is complete so that credentials are not saved in the file.
-```bash
-node utils/testRunner
-  answer no at the first prompt
-npm run test:integration
-```
-To add new integration tests, edit the `test/integration/adapterTestIntegration.js` file. The tests that are already in this file should provide guidance for adding additional tests.
-#### Integration Testing
+## Specific Adapter Information
+### Authentication
-Integration Testing requires connectivity to Datadog. By using the testRunner script it prevents you from having to edit the integration test. It also resets the integration test after the test is complete so that credentials are not saved in the file.
+This document will go through the steps for authenticating the Datadog adapter with Basic Authentication. Properly configuring the properties for an adapter in IAP is critical for getting the adapter online. You can read more about adapter authentication <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/authentication/" target="_blank">HERE</a>.
-> **Note**: These tests have been written as a best effort to make them work in most environments. However, the Adapter Builder often does not have the necessary information that is required to set up valid integration tests. For example, the order of the requests can be very important and data is often required for `creates` and `updates`. Hence, integration tests may have to be enhanced before they will work (integrate) with Datadog. Even after tests have been set up properly, it is possible there are environmental constraints that could result in test failures. Some examples of possible environmental issues are customizations that have been made within Datadog which change order dependencies or required data.
+#### Basic Authentication
+The Datadog adapter requires Basic Authentication. If you change authentication methods, you should change this section accordingly and merge it back into the adapter repository.
-```bash
-node utils/testRunner
-answer yes at the first prompt
-answer all other questions on connectivity and credentials
+STEPS
+1. Ensure you have access to a Datadog server and that it is running
+2. Follow the steps in the README.md to import the adapter into IAP if you have not already done so
+3. Use the properties below for the ```properties.authentication``` field
+```json
+"authentication": {
+  "auth_method": "basic user_password",
+  "username": "<username>",
+  "password": "<password>",
+  "token": "",
+  "token_timeout": 1800000,
+  "token_cache": "local",
+  "invalid_token_error": 401,
+  "auth_field": "header.headers.Authorization",
+  "auth_field_format": "Basic {b64}{username}:{password}{/b64}",
+  "auth_logging": false,
+  "client_id": "",
+  "client_secret": "",
+  "grant_type": ""
+}
 ```
+4. Restart the adapter. If your properties were set correctly, the adapter should go online.
-Test should also be written to clean up after themselves. However, it is important to understand that in some cases this may not be possible. In addition, whenever exceptions occur, test execution may be stopped, which will prevent cleanup actions from running. It is recommended that tests be utilized in dev and test labs only.
-> **Reminder**: Do not check in code with actual credentials to systems.
-## Configuration
+#### Troubleshooting
+- Make sure you copied over the correct username and password.
+- Turn on debug level logs for the adapter in IAP Admin Essentials.
+- Turn on auth_logging for the adapter in IAP Admin Essentials (adapter properties).
+- Investigate the logs - in particular:
+  - The FULL REQUEST log to make sure the proper headers are being sent with the request.
+  - The FULL BODY log to make sure the payload is accurate.
+  - The CALL RETURN log to see what the other system is telling us.
+- Remember when you are done to turn auth_logging off as you do not want to log credentials.
-This section defines **all** the properties that are available for the adapter, including detailed information on what each property is for. If you are not using certain capabilities with this adapter, you do not need to define all of the properties. An example of how the properties for this adapter can be used with tests or IAP are provided in the sampleProperties.
+### Sample Properties
-### Example Properties
+Sample Properties can be used to help you configure the adapter in the Itential Automation Platform. You will need to update connectivity information such as the host, port, protocol and credentials.
 ```json
   "properties": {
@@ -486,6 +167,7 @@ This section defines **all** the properties that are available for the adapter,
       }
     },
     "devicebroker": {
+      "enabled": false,
       "getDevice": [
         {
           "path": "/get/devices/{id}",
@@ -620,2661 +302,7 @@ This section defines **all** the properties that are available for the adapter,
     }
   }
 ```
+### [Swagger](https://gitlab.com/itentialopensource/adapters/telemetry-analytics/adapter-datadog/-/blob/master/report/adapter-openapi.json)
-### Connection Properties
-These base properties are used to connect to Datadog upon the adapter initially coming up. It is important to set these properties appropriately.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">host</td>
-    <td style="padding:15px">Required. A fully qualified domain name or IP address.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">port</td>
-    <td style="padding:15px">Required. Used to connect to the server.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">base_path</td>
-    <td style="padding:15px">Optional. Used to define part of a path that is consistent for all or most endpoints. It makes the URIs easier to use and maintain but can be overridden on individual calls. An example **base_path** might be `/rest/api`. Default is ``.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">version</td>
-    <td style="padding:15px">Optional. Used to set a global version for action endpoints. This makes it faster to update the adapter when endpoints change. As with the base-path, version can be overridden on individual endpoints. Default is ``.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">cache_location</td>
-    <td style="padding:15px">Optional. Used to define where the adapter cache is located. The cache is used to maintain an entity list to improve performance. Storage locally is lost when the adapter is restarted. Storage in Redis is preserved upon adapter restart. Default is none which means no caching of the entity list.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">encode_pathvars</td>
-    <td style="padding:15px">Optional. Used to tell the adapter to encode path variables or not. The default behavior is to encode them so this property can be used to stop that behavior.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">encode_queryvars</td>
-    <td style="padding:15px">Optional. Used to tell the adapter to encode query parameters or not. The default behavior is to encode them so this property can be used to stop that behavior.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">save_metric</td>
-    <td style="padding:15px">Optional. Used to tell the adapter to save metric information (this does not impact metrics returned on calls). This allows the adapter to gather metrics over time. Metric data can be stored in a database or on the file system.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">stub</td>
-    <td style="padding:15px">Optional. Indicates whether the stub should run instead of making calls to Datadog (very useful during basic testing). Default is false (which means connect to Datadog).</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">protocol</td>
-    <td style="padding:15px">Optional. Notifies the adapter whether to use HTTP or HTTPS. Default is HTTP.</td>
-  </tr>
-</table>
-<br>
-A connectivity check tells IAP the adapter has loaded successfully.
-### Authentication Properties
-The following properties are used to define the authentication process to Datadog.
->**Note**: Depending on the method that is used to authenticate with Datadog, you may not need to set all of the authentication properties.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">auth_method</td>
-    <td style="padding:15px">Required. Used to define the type of authentication currently supported. Authentication methods currently supported are: `basic user_password`, `static_token`, `request_token`, and `no_authentication`.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">username</td>
-    <td style="padding:15px">Used to authenticate with Datadog on every request or when pulling a token that will be used in subsequent requests.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">password</td>
-    <td style="padding:15px">Used to authenticate with Datadog on every request or when pulling a token that will be used in subsequent requests.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">token</td>
-    <td style="padding:15px">Defines a static token that can be used on all requests. Only used with `static_token` as an authentication method (auth\_method).</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">invalid_token_error</td>
-    <td style="padding:15px">Defines the HTTP error that is received when the token is invalid. Notifies the adapter to pull a new token and retry the request. Default is 401.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">token_timeout</td>
-    <td style="padding:15px">Defines how long a token is valid. Measured in milliseconds. Once a dynamic token is no longer valid, the adapter has to pull a new token. If the token_timeout is set to -1, the adapter will pull a token on every request to Datadog. If the timeout_token is 0, the adapter will use the expiration from the token response to determine when the token is no longer valid.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">token_cache</td>
-    <td style="padding:15px">Used to determine where the token should be stored (local memory or in Redis).</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">auth_field</td>
-    <td style="padding:15px">Defines the request field the authentication (e.g., token are basic auth credentials) needs to be placed in order for the calls to work.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">auth_field_format</td>
-    <td style="padding:15px">Defines the format of the auth\_field. See examples below. Items enclosed in {} inform the adapter to perofrm an action prior to sending the data. It may be to replace the item with a value or it may be to encode the item.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">auth_logging</td>
-    <td style="padding:15px">Setting this true will add some additional logs but this should only be done when trying to debug an issue as certain credential information may be logged out when this is true.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">client_id</td>
-    <td style="padding:15px">Provide a client id when needed, this is common on some types of OAuth.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">client_secret</td>
-    <td style="padding:15px">Provide a client secret when needed, this is common on some types of OAuth.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">grant_type</td>
-    <td style="padding:15px">Provide a grant type when needed, this is common on some types of OAuth.</td>
-  </tr>
-</table>
-<br>
-#### Examples of authentication field format
-```json
-"{token}"
-"Token {token}"
-"{username}:{password}"
-"Basic {b64}{username}:{password}{/b64}"
-```
-### Healthcheck Properties
-The healthcheck properties defines the API that runs the healthcheck to tell the adapter that it can reach Datadog. There are currently three types of healthchecks.
-- None - Not recommended. Adapter will not run a healthcheck. Consequently, unable to determine before making a request if the adapter can reach Datadog.
-- Startup - Adapter will check for connectivity when the adapter initially comes up, but it will not check afterwards.
-- Intermittent - Adapter will check connectivity to Datadog at a frequency defined in the `frequency` property.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">type</td>
-    <td style="padding:15px">Required. The type of health check to run.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">frequency</td>
-    <td style="padding:15px">Required if intermittent. Defines how often the health check should run. Measured in milliseconds. Default is 300000.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">query_object</td>
-    <td style="padding:15px">Query parameters to be added to the adapter healthcheck call.</td>
-  </tr>
-</table>
-<br>
-### Request Properties
-The request section defines properties to help handle requests.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">number_redirects</td>
-    <td style="padding:15px">Optional. Tells the adapter that the request may be redirected and gives it a maximum number of redirects to allow before returning an error. Default is 0 - no redirects.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">number_retries</td>
-    <td style="padding:15px">Tells the adapter how many times to retry a request that has either aborted or reached a limit error before giving up and returning an error.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">limit_retry_error</td>
-    <td style="padding:15px">Optional. Can be either an integer or an array. Indicates the http error status number to define that no capacity was available and, after waiting a short interval, the adapter can retry the request. If an array is provvided, the array can contain integers or strings. Strings in the array are used to define ranges (e.g. "502-506"). Default is [0].</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">failover_codes</td>
-    <td style="padding:15px">An array of error codes for which the adapter will send back a failover flag to IAP so that the Platform can attempt the action in another adapter.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">attempt_timeout</td>
-    <td style="padding:15px">Optional. Tells how long the adapter should wait before aborting the attempt. On abort, the adapter will do one of two things: 1) return the error; or 2) if **healthcheck\_on\_timeout** is set to true, it will abort the request and run a Healthcheck until it re-establishes connectivity to Datadog, and then will re-attempt the request that aborted. Default is 5000 milliseconds.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">global_request</td>
-    <td style="padding:15px">Optional. This is information that the adapter can include in all requests to the other system. This is easier to define and maintain than adding this information in either the code (adapter.js) or the action files.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">global_request -> payload</td>
-    <td style="padding:15px">Optional. Defines any information that should be included on all requests sent to the other system that have a payload/body.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">global_request -> uriOptions</td>
-    <td style="padding:15px">Optional. Defines any information that should be sent as untranslated  query options (e.g. page, size) on all requests to the other system.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">global_request -> addlHeaders</td>
-    <td style="padding:15px">Optioonal. Defines any headers that should be sent on all requests to the other system.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">global_request -> authData</td>
-    <td style="padding:15px">Optional. Defines any additional authentication data used to authentice with the other system. This authData needs to be consistent on every request.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">healthcheck_on_timeout</td>
-    <td style="padding:15px">Required. Defines if the adapter should run a health check on timeout. If set to true, the adapter will abort the request and run a health check until it re-establishes connectivity and then it will re-attempt the request.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">return_raw</td>
-    <td style="padding:15px">Optional. Tells the adapter whether the raw response should be returned as well as the IAP response. This is helpful when running integration tests to save mock data. It does add overhead to the response object so it is not ideal from production.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">archiving</td>
-    <td style="padding:15px">Optional flag. Default is false. It archives the request, the results and the various times (wait time, Datadog time and overall time) in the `adapterid_results` collection in MongoDB. Although archiving might be desirable, be sure to develop a strategy before enabling this capability. Consider how much to archive and what strategy to use for cleaning up the collection in the database so that it does not become too large, especially if the responses are large.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">return_request</td>
-    <td style="padding:15px">Optional flag. Default is false. Will return the actual request that is made including headers. This should only be used during debugging issues as there could be credentials in the actual request.</td>
-  </tr>
-</table>
-<br>
-### SSL Properties
-The SSL section defines the properties utilized for ssl authentication with Datadog. SSL can work two different ways: set the `accept\_invalid\_certs` flag to true (only recommended for lab environments), or provide a `ca\_file`.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">enabled</td>
-    <td style="padding:15px">If SSL is required, set to true.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">accept_invalid_certs</td>
-    <td style="padding:15px">Defines if the adapter should accept invalid certificates (only recommended for lab environments). Required if SSL is enabled. Default is false.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">ca_file</td>
-    <td style="padding:15px">Defines the path name to the CA file used for SSL. If SSL is enabled and the accept invalid certifications is false, then ca_file is required.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">key_file</td>
-    <td style="padding:15px">Defines the path name to the Key file used for SSL. The key_file may be needed for some systems but it is not required for SSL.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">cert_file</td>
-    <td style="padding:15px">Defines the path name to the Certificate file used for SSL. The cert_file may be needed for some systems but it is not required for SSL.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">secure_protocol</td>
-    <td style="padding:15px">Defines the protocol (e.g., SSLv3_method) to use on the SSL request.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">ciphers</td>
-    <td style="padding:15px">Required if SSL enabled. Specifies a list of SSL ciphers to use.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">ecdhCurve</td>
-    <td style="padding:15px">During testing on some Node 8 environments, you need to set `ecdhCurve` to auto. If you do not, you will receive PROTO errors when attempting the calls. This is the only usage of this property and to our knowledge it only impacts Node 8 and 9.</td>
-  </tr>
-</table>
-<br>
-### Throttle Properties
-The throttle section is used when requests to Datadog must be queued (throttled). All of the properties in this section are optional.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">throttle_enabled</td>
-    <td style="padding:15px">Default is false. Defines if the adapter should use throttling or not.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">number_pronghorns</td>
-    <td style="padding:15px">Default is 1. Defines if throttling is done in a single Itential instance or whether requests are being throttled across multiple Itential instances (minimum = 1, maximum = 20). Throttling in a single Itential instance uses an in-memory queue so there is less overhead. Throttling across multiple Itential instances requires placing the request and queue information into a shared resource (e.g. database) so that each instance can determine what is running and what is next to run. Throttling across multiple instances requires additional I/O overhead.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">sync-async</td>
-    <td style="padding:15px">This property is not used at the current time (it is for future expansion of the throttling engine).</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">max_in_queue</td>
-    <td style="padding:15px">Represents the maximum number of requests the adapter should allow into the queue before rejecting requests (minimum = 1, maximum = 5000). This is not a limit on what the adapter can handle but more about timely responses to requests. The default is currently 1000.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">concurrent_max</td>
-    <td style="padding:15px">Defines the number of requests the adapter can send to Datadog at one time (minimum = 1, maximum = 1000). The default is 1 meaning each request must be sent to Datadog in a serial manner.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">expire_timeout</td>
-    <td style="padding:15px">Default is 0. Defines a graceful timeout of the request session. After a request has completed, the adapter will wait additional time prior to sending the next request. Measured in milliseconds (minimum = 0, maximum = 60000).</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">average_runtime</td>
-    <td style="padding:15px">Represents the approximate average of how long it takes Datadog to handle each request. Measured in milliseconds (minimum = 50, maximum = 60000). Default is 200. This metric has performance implications. If the runtime number is set too low, it puts extra burden on the CPU and memory as the requests will continually try to run. If the runtime number is set too high, requests may wait longer than they need to before running. The number does not need to be exact but your throttling strategy depends heavily on this number being within reason. If averages range from 50 to 250 milliseconds you might pick an average run-time somewhere in the middle so that when Datadog performance is exceptional you might run a little slower than you might like, but when it is poor you still run efficiently.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">priorities</td>
-    <td style="padding:15px">An array of priorities and how to handle them in relation to the throttle queue. Array of objects that include priority value and percent of queue to put the item ex { value: 1, percent: 10 }</td>
-  </tr>
-</table>
-<br>
-### Proxy Properties
-The proxy section defines the properties to utilize when Datadog is behind a proxy server.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">enabled</td>
-    <td style="padding:15px">Required. Default is false. If Datadog is behind a proxy server, set enabled flag to true.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">host</td>
-    <td style="padding:15px">Host information for the proxy server. Required if `enabled` is true.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">port</td>
-    <td style="padding:15px">Port information for the proxy server. Required if `enabled` is true.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">protocol</td>
-    <td style="padding:15px">The protocol (i.e., http, https, etc.) used to connect to the proxy. Default is http.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">username</td>
-    <td style="padding:15px">If there is authentication for the proxy, provide the username here.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">password</td>
-    <td style="padding:15px">If there is authentication for the proxy, provide the password here.</td>
-  </tr>
-</table>
-<br>
-### Mongo Properties
-The mongo section defines the properties used to connect to a Mongo database. Mongo can be used for throttling as well as to persist metric data. If not provided, metrics will be stored in the file system.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">host</td>
-    <td style="padding:15px">Optional. Host information for the mongo server.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">port</td>
-    <td style="padding:15px">Optional. Port information for the mongo server.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">database</td>
-    <td style="padding:15px">Optional. The database for the adapter to use for its data.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">username</td>
-    <td style="padding:15px">Optional. If credentials are required to access mongo, this is the user to login as.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">password</td>
-    <td style="padding:15px">Optional. If credentials are required to access mongo, this is the password to login with.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">replSet</td>
-    <td style="padding:15px">Optional. If the database is set up to use replica sets, define it here so it can be added to the database connection.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">db_ssl</td>
-    <td style="padding:15px">Optional. Contains information for SSL connectivity to the database.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">db_ssl -> enabled</td>
-    <td style="padding:15px">If SSL is required, set to true.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">db_ssl -> accept_invalid_cert</td>
-    <td style="padding:15px">Defines if the adapter should accept invalid certificates (only recommended for lab environments). Required if SSL is enabled. Default is false.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">db_ssl -> ca_file</td>
-    <td style="padding:15px">Defines the path name to the CA file used for SSL. If SSL is enabled and the accept invalid certifications is false, then ca_file is required.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">db_ssl -> key_file</td>
-    <td style="padding:15px">Defines the path name to the Key file used for SSL. The key_file may be needed for some systems but it is not required for SSL.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">db_ssl -> cert_file</td>
-    <td style="padding:15px">Defines the path name to the Certificate file used for SSL. The cert_file may be needed for some systems but it is not required for SSL.</td>
-  </tr>
-</table>
-<br>
-### Device Broker Properties
-The device broker section defines the properties used integrate Datadog to the device broker. Each broker call is represented and has an array of calls that can be used to build the response. This describes the calls and then the fields which are available in the calls.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Property</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice</td>
-    <td style="padding:15px">The array of calls used to get device details for the broker</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevicesFiltered</td>
-    <td style="padding:15px">The array of calls used to get devices for the broker</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">isAlive</td>
-    <td style="padding:15px">The array of calls used to get device status for the broker</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getConfig</td>
-    <td style="padding:15px">The array of calls used to get device configuration for the broker</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getCount</td>
-    <td style="padding:15px">The array of calls used to get device configuration for the broker</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> path</td>
-    <td style="padding:15px">The path, not including the base_path and version, for making this call</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> method</td>
-    <td style="padding:15px">The rest method for making this call</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> query</td>
-    <td style="padding:15px">Query object containing and query parameters and their values for this call</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> body</td>
-    <td style="padding:15px">Body object containing the payload for this call</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> headers</td>
-    <td style="padding:15px">Header object containing the headers for this call.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig/getCount -> handleFailure</td>
-    <td style="padding:15px">Tells the adapter whether to "fail" or "ignore" failures if they occur.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">isAlive -> statusValue</td>
-    <td style="padding:15px">Tells the adapter what value to look for in the status field to determine if the device is alive.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig -> requestFields</td>
-    <td style="padding:15px">Object containing fields the adapter should send on the request and where it should get the data. The where can be from a response to a getDevicesFiltered or a static value.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice/getDevicesFiltered/isAlive/getConfig -> responseFields</td>
-    <td style="padding:15px">Object containing fields the adapter should set to send back to iap and where the value should come from in the response or request data.</td>
-  </tr>
-</table>
-<br>
-## Using this Adapter
-The `adapter.js` file contains the calls the adapter makes available to the rest of the Itential Platform. The API detailed for these calls should be available through JSDOC. The following is a brief summary of the calls.
-### Generic Adapter Calls
-These are adapter methods that IAP or you might use. There are some other methods not shown here that might be used for internal adapter functionality.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">connect()</td>
-    <td style="padding:15px">This call is run when the Adapter is first loaded by he Itential Platform. It validates the properties have been provided correctly.</td>
-    <td style="padding:15px">No</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">healthCheck(callback)</td>
-    <td style="padding:15px">This call ensures that the adapter can communicate with Adapter for Datadog. The actual call that is used is defined in the adapter properties and .system entities action.json file.</td>
-    <td style="padding:15px">No</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">refreshProperties(properties)</td>
-    <td style="padding:15px">This call provides the adapter the ability to accept property changes without having to restart the adapter.</td>
-    <td style="padding:15px">No</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">encryptProperty(property, technique, callback)</td>
-    <td style="padding:15px">This call will take the provided property and technique, and return the property encrypted with the technique. This allows the property to be used in the adapterProps section for the credential password so that the password does not have to be in clear text. The adapter will decrypt the property as needed for communications with Adapter for Datadog.</td>
-    <td style="padding:15px">No</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapUpdateAdapterConfiguration(configFile, changes, entity, type, action, callback)</td>
-    <td style="padding:15px">This call provides the ability to update the adapter configuration from IAP - includes actions, schema, mockdata and other configurations.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapSuspendAdapter(mode, callback)</td>
-    <td style="padding:15px">This call provides the ability to suspend the adapter and either have requests rejected or put into a queue to be processed after the adapter is resumed.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapUnsuspendAdapter(callback)</td>
-    <td style="padding:15px">This call provides the ability to resume a suspended adapter. Any requests in queue will be processed before new requests.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapGetAdapterQueue(callback)</td>
-    <td style="padding:15px">This call will return the requests that are waiting in the queue if throttling is enabled.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapFindAdapterPath(apiPath, callback)</td>
-    <td style="padding:15px">This call provides the ability to see if a particular API path is supported by the adapter.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapTroubleshootAdapter(props, persistFlag, adapter, callback)</td>
-    <td style="padding:15px">This call can be used to check on the performance of the adapter - it checks connectivity, healthcheck and basic get calls.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapRunAdapterHealthcheck(adapter, callback)</td>
-    <td style="padding:15px">This call will return the results of a healthcheck.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapRunAdapterConnectivity(callback)</td>
-    <td style="padding:15px">This call will return the results of a connectivity check.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapRunAdapterBasicGet(callback)</td>
-    <td style="padding:15px">This call will return the results of running basic get API calls.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapMoveAdapterEntitiesToDB(callback)</td>
-    <td style="padding:15px">This call will push the adapter configuration from the entities directory into the Adapter or IAP Database.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapDeactivateTasks(tasks, callback)</td>
-    <td style="padding:15px">This call provides the ability to remove tasks from the adapter.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapActivateTasks(tasks, callback)</td>
-    <td style="padding:15px">This call provides the ability to add deactivated tasks back into the adapter.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapExpandedGenericAdapterRequest(metadata, uriPath, restMethod, pathVars, queryData, requestBody, addlHeaders, callback)</td>
-    <td style="padding:15px">This is an expanded Generic Call. The metadata object allows us to provide many new capabilities within the generic request.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">genericAdapterRequest(uriPath, restMethod, queryData, requestBody, addlHeaders, callback)</td>
-    <td style="padding:15px">This call allows you to provide the path to have the adapter call. It is an easy way to incorporate paths that have not been built into the adapter yet.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">genericAdapterRequestNoBasePath(uriPath, restMethod, queryData, requestBody, addlHeaders, callback)</td>
-    <td style="padding:15px">This call is the same as the genericAdapterRequest only it does not add a base_path or version to the call.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapRunAdapterLint(callback)</td>
-    <td style="padding:15px">Runs lint on the addapter and provides the information back.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapRunAdapterTests(callback)</td>
-    <td style="padding:15px">Runs baseunit and unit tests on the adapter and provides the information back.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapGetAdapterInventory(callback)</td>
-    <td style="padding:15px">This call provides some inventory related information about the adapter.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-</table>
-<br>
-### Adapter Cache Calls
-These are adapter methods that are used for adapter caching. If configured, the adapter will cache based on the interval provided. However, you can force a population of the cache manually as well.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapPopulateEntityCache(entityTypes, callback)</td>
-    <td style="padding:15px">This call populates the adapter cache.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapRetrieveEntitiesCache(entityType, options, callback)</td>
-    <td style="padding:15px">This call retrieves the specific items from the adapter cache.</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-</table>
-<br>
-### Adapter Broker Calls
-These are adapter methods that are used to integrate to IAP Brokers. This adapter currently supports the following broker calls.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">hasEntities(entityType, entityList, callback)</td>
-    <td style="padding:15px">This call is utilized by the IAP Device Broker to determine if the adapter has a specific entity and item of the entity.</td>
-    <td style="padding:15px">No</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevice(deviceName, callback)</td>
-    <td style="padding:15px">This call returns the details of the requested device.</td>
-    <td style="padding:15px">No</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevicesFiltered(options, callback)</td>
-    <td style="padding:15px">This call returns the list of devices that match the criteria provided in the options filter.</td>
-    <td style="padding:15px">No</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">isAlive(deviceName, callback)</td>
-    <td style="padding:15px">This call returns whether the device status is active</td>
-    <td style="padding:15px">No</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getConfig(deviceName, format, callback)</td>
-    <td style="padding:15px">This call returns the configuration for the selected device.</td>
-    <td style="padding:15px">No</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">iapGetDeviceCount(callback)</td>
-    <td style="padding:15px">This call returns the count of devices.</td>
-    <td style="padding:15px">No</td>
-  </tr>
-</table>
-<br>
-### Specific Adapter Calls
-Specific adapter calls are built based on the API of the Datadog. The Adapter Builder creates the proper method comments for generating JS-DOC for the adapter. This is the best way to get information on the calls.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Path</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">createUser(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Create a user for your organization.
-### ARGUMENTS
-* **`handle`** [*required*]: The user handle, must be a valid email.
-* **`name`** [*optional*, *default*=**None**]: The name of the user.
-* **`access_role`** [*optional*, *default*=**st**]: The access role of the user. Choose from:
-    *  **st** (standard user),
-    *  **adm** (admin user),
-    *  **ro** (read-only user).
-    *Note: users can be created with admin access role only with application keys belonging to administrators...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllUsers(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get all user for your organization.
-### Arguments
-This endpoint takes no JSON argument.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getUser(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get a user details.
-### Arguments
-* **`user_handle`** [*required*]: The handle of the user.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">updateUser(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Update a user informations,
-**Note**: It can only be used with application keys belonging to administrators.
-##### ARGUMENTS
-* **`id`** [*required*]: The handle of the user.
-* **`name`** [*optional*, *default*=**None**]: The new name of the user.
-* **`email`** [*optional*, *default*=**None**]: The new email of the user.
-* **`disabled`** [*optional*, *default*=**None**]: The new disabled status of the user.
-* **`access_role`** [*optional*, *default*=**st**]: The access role of the...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">disableUser(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete a user from an organization.
-**Note**: This endpoint can only be used with application keys belonging to administrators.
-### Arguments
-* **`id`** [*required*]: The handle of the user.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">authenticationCheck(apiKey, callback)</td>
-    <td style="padding:15px">All requests to Datadog's API must be authenticated. Requests that write data require *reporting access* and require an `API key`. Requests that read data require *full access* and also require an `application key`.
-[Manage your account's API and application keys](https://app.datadoghq.com/account/settings#api).
-This GET call just checks to see if an API call key is valid.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">postACheckStatus(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-This POST call allows for you to POST check statuses for use with monitors
-### Arguments
-* **`check`** *[required]*: The text for the message
-* **`host_name`** *[required]*: The name of the host submitting the check
-* **`status`** *[optional]*: An integer for the status of the check:
-    * 0 : OK
-    * 1 : WARNING
-    * 2 : CRITICAL
-    * 3 : UNKNOWN
-* **`timestamp`** *[optional]*: POSIX timestamp of the event.
-* **`message`** *[optional]*:   A description of why this stat...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">replyToComment(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-This POST call allows for you to POST status messages to a previous post via ID.
-### Arguments
-* **`message`** [*required*]: The comment text.
-* **`handle`** [*optional*, *default* = **application key owner**]: The handle of the user making the comment.
-* **`related_event_id`** [*optional*, *default* = **None**]: The id of another comment or event to reply to.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">editAComment(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-This POST call allows for you to change a previously posted comment by commentId
-### Arguments
-* **`message`** [*optional*, *default* = **original message**]: The comment text.
-* **`handle`** [*optional*, *default* = **Application key owner**]: The handle of the user making the comment.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteAComment(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Thiscall allows for you to DELETE a previously posted comment by with a given  .
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createADashboard(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Create a Dashboard in Datadog.
-### Arguments
-* **`title`** [*required*]: Title of the dashboard.
-* **`widgets`** [*required*]: List of widgets to display on the dashboard. Widget definitions follow this form:
-    * **`definition`** [*required*]: [Definition of the widget.](https://docs.datadoghq.com//graphing/widgets)
-    * **`id`** [*optional*, *default*=**auto-generated integer**]: ID of the widget.
-* **`layout_type`** [*required*]: Layout type of the dashboard. Available value...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">updateADashboard(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Update a Dashboard in Datadog.
-### Arguments
-* **`title`** [*required*]: Title of the dashboard.
-* **`widgets`** [*required*]: List of widgets to display on the dashboard. Widget definitions follow this form:
-    * **`definition`** [*required*]: [Definition of the widget.](https://docs.datadoghq.com/graphing/widgets)
-    * **`id`** [*optional*, *default*=**auto-generated integer**]: ID of the widget.
-* **`layout_type`** [*required*]: Layout type of the dashboard. Available values...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteADashboard(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete an existing dashboard.
-### Arguments
-This end point takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getADashboard(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Fetch an existing dashboard's definition.
-### Arguments
-This end point takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllDashboards(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Fetch all existing Dashboards.
-### Arguments
-This end point takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getADashboardList(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Fetch an existing dashboard list’s definition.
-### Arguments
-This end point takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">updateADashboardList(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Update the name of a dashboard list
-### Arguments
-*   **`name`** [*required*]: The name of the dashboard list.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteADashboardList(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete an existing dashboard list.
-### Arguments
-This end point takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllDashboardLists(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Fetch all of your existing dashboard list definitions.
-### Arguments
-This end point takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createADashboardList(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Create an empty dashboard list.
-### Arguments
-*   **`name`** [*required*]: The name of the dashboard list.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getItemsOfADashboardList(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Fetch the dashboard list’s dashboard definitions.
-### Arguments
-This end point takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">addItemsToDashboardList(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Add dashboards to an existing dashboard list.
-### Arguments
-*   **`dashboards`** [*required*]: A list of dashboards to add to the list. Dashboard definitions follow this form:
-    *   **`type`** [*required*]: The type of the dashboard. The type must be one of:
-        * `"custom_timeboard"`
-        * `"custom_screenboard"`
-        * `"integration_screenboard"`
-        * `"integration_timeboard"`
-        * `"host_timeboard"`
-    *   **`id`** [*required*]: The id of the dashboard.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">updateItemsOfADashboardList(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Update dashboards of an existing dashboard list.
-### ARGUMENTS
-*   **`dashboards`** [*required*]: The new list of dashboards for the dashboard list. Dashboard definitions follow this form:
-    *   **`type`** [*required*]: The type of the dashboard. The type must be one of:
-        * `"custom_timeboard"`
-        * `"custom_screenboard"`
-        * `"integration_screenboard"`
-        * `"integration_timeboard"`
-        * `"host_timeboard"`
-    *   **`id`** [*required*]: The id of th...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteItemsFromADashboardList(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete dashboards from an existing dashboard list.
-### Arguments
-*   **`dashboards`** [*required*]: A list of dashboards to remove from the list. Dashboard definitions follow this form:
-    *   **`type`** [*required*]: The type of the dashboard. The type must be one of:
-        * `"custom_timeboard"`
-        * `"custom_screenboard"`
-        * `"integration_screenboard"`
-        * `"integration_timeboard"`
-        * `"host_timeboard"`
-    *   **`id`** [*required*]: The id of the d...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">scheduleMonitorDowntime(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Schedule a single Downtime.
-### ARGUMENTS
-* **`scope`** [*required*]: The scope(s) to which the downtime applies, e.g. `host:app2`. Provide multiple scopes as a comma-separated list, e.g. `env:dev,env:prod`. The resulting downtime applies to sources that matches ALL provided scopes (i.e. `env:dev` **AND** `env:prod`), NOT any of them.
-* **`monitor_tags`** [*optional*, *default*=**no monitor tag filter**]: A comma-separated list of monitor tags, i.e. tags that are applied directly...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllMointorDowntimes(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get All Scheduled Downtimes
-### ARGUMENTS
-* **`current_only`** [*optional*, *default* = **False**]: Only return downtimes that are activewhen the request is made.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">updateMonitorDowntime(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Update a single Downtime by downtime_id.
-### Arguments
-* **`id`** [*required*]: The integer id of the downtime to be updated
-* **`scope`** [*required*]: The scope to which the downtime applies, e.g. 'host:app2'. Provide multiple scopes as a comma-separated list, e.g. 'env:dev,env:prod'. The resulting downtime applies to sources that matches ALL provided scopes (i.e. env:dev AND env:prod), NOT any of them.
-* **`monitor_tags`** [*optional*, *default*=**no monitor tag filter**]: A c...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">cancelMonitorDowntime(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">DELETE a Downtime Detail by downtime_id</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAMonitorDowntime(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get Downtime Detail by downtime_id
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">cancelMonitorDowntimesByScope(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-DELETE all Downtimes that match the scope of X
-### Arguments
-* **`scope`** [*required*]:   Cancel all downtimes with the given scope(s), e.g.: `env:prod`, `role:db,role:db-slave`</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllEmbeddableGraphs(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Gets a list of previously created embeddable graphs.
-Returns: A JSON list containing information on previously created embeds from both the UI and the API. Each JSON graph response is in the same format as returned by GET `api/v1/graph/embed/ `.
-### ARGUMENTS
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createEmbedGraph(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Creates a new embeddable graph.
-Returns: A JSON consisting of the same elements returned by GET `api/v1/graph/embed/ `. On failure, the return value is a JSON containing an error message {errors: [messages]}.
-Note: If an embed already exists for the exact same query in a given organization, the older embed is returned instead of creating a new embed.
-If you are interested in using template variables, see [Embeddable Graphs with Template Variables](https://docs.datadoghq.com/grap...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getASpecificEmbed(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get the HTML fragment for a previously generated embed with embed_id.
-Returns: A JSON object with 8 elements:
-* `embed_id`: Token of the embed
-* `graph_title`: Tile of the graph
-* `dash_name`: Name of the dashboard the graph is on (null if none)
-* `dash_url`: URL of the dashboard the graph is on (null if none)
-* `shared_by`: ID of the use who shared the embed
-* `html`: HTML fragment for the embed (iframe)
-* `revoked`: Boolean flag for whther or not the embed is revoked
-On failur...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">enableEmbed(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Enable a specified embed.
-Returns: A JSON containing the success message `{success: [message]}`. On failure, the return value is a JSON containing an error message `{errors: [messages]}`.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">revokeEmbed(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Revoke a specified embed.
-Returns: A JSON containing the success message `{success: [message]}`. On failure, the return value is a JSON containing an error message `{errors: [messages]}`.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">postAnEvent(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-This endpoint allows you to post events to the stream. Tag them, set priority and event aggregate them with other events.
-### Arguments
-* **`title`** [*required*]:   The event title. *Limited to 100 characters.* Use `msg_title` with [the Datadog Ruby library](https://github.com/DataDog/dogapi-rb).
-* **`text`** [*required*]:   The body of the event. *Limited to 4000 characters.* The text supports [markdown](https://docs.datadoghq.com/graphing/event_stream/#markdown-events). Use `m...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">queryTheEventStream(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-The [event stream](https://docs.datadoghq.com/graphing/event_stream) can be queried and filtered by time, priority, sources and tags.
-Note: if the event you're querying contains markdown formatting of any kind, you may see characters such as %,\,n in your output
-### Arguments
-* **`start`** [*required*]: POSIX timestamp.
-* **`end`** [*required*]: POSIX timestamp.
-* **`priority`** [*optional*, *default*=**None**]: Priority of your events: **low** or **normal**.
-* **`sources`** [*op...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAnEvent(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get event details by event_id
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteAnEvent(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-DELETE event details by event_id
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">graphASnapshot(apiKey, applicationKey, metricQuery, start, end, title, callback)</td>
-    <td style="padding:15px">### Overview
-Get a Graph snapshot.
-##### ARGUMENTS
-* **`metric_query`** [*required*]: The metric query.
-* **`start`** [*required*]: The POSIX timestamp of the start of the query.
-* **`end`** [*required*]: The POSIX timestamp of the end of the query.
-* **`event_query`** [*optional*, *default*=**None**]: A query that adds event bands to the graph.
-* **`graph_def`** [*optional*, *default*=**None**]: A JSON document defining the graph. `graph_def` can be used instead of `metric_query`. The JSON d...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">searchHosts(apiKey, applicationKey, filter, sortField, sortDir, start, count, callback)</td>
-    <td style="padding:15px">### Overview
-This endpoint allows searching for hosts by name, alias, or tag. Hosts live within the past 3 hours are included. Results are paginated with a max of 100 results at a time.
-### Arguments
-* **`filter`** [*optional*, *default*=**None**]: Query string to filter search results.
-* **`sort_field`** [*optional*, *default*=**cpu**]: Sort hosts by the given field. Options: **status**, **apps**, **cpu**, **iowait**, **load**
-* **`sort_dir`** [*optional*, *default*=**desc**]: Direction of s...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">hostTotals(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-This endpoint returns the total number of active and up hosts in your Datadog account. Active means the host has reported in the past hour, and up means it has reported in the past two hours.
-### ARGUMENTS
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">muteAHost(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Mute a host in order to avoid any monitor to trigger on it.
-### Arguments
-* **`end`** [*optional*, *default*=**None**]: POSIX timestamp when the host is unmuted. If omitted, the host remains muted until explicitly unmuted.
-* **`message`** [*optional*, *default*=**None**]: Message to associate with the muting of this host.
-* **`override`** [*optional*, *default*=**False**]: If true and the host is already muted, replaces existing host mute settings.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">unmuteAHost(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Unmute a previously muted host
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">listAWSAccounts(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-List all configured AWS accounts for Datadog.
-### Arguments
-This endpoint takes no JSON argument.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createAnAWSIntegration(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Create a Datadog-Amazon Web Services integration.
-**Note**: Using the `POST` method updates your integration configuration by **adding** your new configuration to the existing one in your Datadog organization.
-### Arguments
-* **`account_id`** [*required*]:
-    Your AWS Account ID without dashes.
-    [Consult the Datadog AWS integration to learn more][1] about your AWS account ID.
-* **`access_key_id`** [*optional*, *default*=**None**]:
-    If your AWS account is a GovCloud or ...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteAnAWSIntegration(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete your Datadog-AWS integration directly through Datadog API. [Read more about Datadog-AWS integration][1].
-### Arguments
-This endpoint takes no JSON argument.
-[1]: https://docs.datadoghq.com/integrations/amazon_web_services</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">listAvailableNamespaceRules(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-List available namespace rules for your AWS integration
-### Arguments
-This endpoint takes no JSON arguments</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">listAWSFilteringRules(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-List AWS Accounts (role-based only) in Datadog.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">configureAWSFilteringRuleCopy(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-List AWS Accounts (role-based only) in Datadog. [Read more about Datadog-AWS integration][1].
-### Arguments
-* **`account_id`** [*required*]: Your AWS Account ID without dashes. [Consult the Datadog AWS integration to learn more][2] about your AWS account ID.
-* **`access_key_id`** [*optional*, *default*=**None**]: If your AWS account is a GovCloud or China account, enter the corresponding Access Key ID.$
-* **`namespace`** [*required*]: The AWS namespace to apply filtering too (e...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteAWSFilteringRule(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">Delete a Datadog-AWS Filtering rule</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">generateNewExternalIDs(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Generate a new AWS external id for a given AWS account id and role name pair.
-### Arguments
-* **`account_id`** [*required*]:
-    Your AWS Account ID without dashes.
-    [Consult the Datadog AWS integration to learn more][1] about your AWS account ID.
-* **`role_name`** [*required*]:
-    Your Datadog role delegation name.
-    For more information about you AWS account Role name, [see the Datadog AWS integration configuration info][2].
-[1]: /integrations/amazon_web_services/#co...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">listAzureAccount(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-List all Datadog-Azure integrations configured for your Datadog Account.
-### Arguments
-This endpoint takes no JSON argument.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">updateAzureAccountSHostFilters(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Update Datadog-Azure host filtering.
-### Arguments
-Refer to the [Datadog-Azure integration installation instructions][1] to see how to obtain the following field values for your organization.
-* **`tenant_name`** [*required*]: Your Azure Active Directory ID.
-* **`client_id`** [*required*]: Your Azure web application ID.
-* **`client_secret`** [*required*]: Your Azure web application secret key.
-* **`host_filters`** [*optional*, *default*=**None**]: Limit the Azure instances th...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteAnAzureAccount(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete a Datadog-Azure integration.
-### Arguments
-This endpoint takes no JSON argument.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">listGCPAccounts(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-List all Datadog-GCP integrations configured for your Datadog Account.
-### Arguments
-This endpoint takes no JSON argument.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createGCPAccount(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Configure your Datadog-Google Cloud Platform integration directly through the Datadog API.
-[Read more about Datadog-Google Cloud Platform integration][1].
-**Note**:  Using the `POST` method updates your integration configuration by **adding** your new configuration to the existing one in your Datadog organization.
-### Arguments
-All of the following fields' values are provided by the JSON service account key file created in the [GCP Console for service accounts][2]; Refer to t...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">updateAGCPServiceAccountSAutomuteOption(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Update your Datadog-Google Cloud Platform integration Automute options.
-[Read more about Datadog-Google Cloud Platform integration][1].
-### Arguments
-* **`project_id`** [*required*]: Your Google Cloud project ID found in your JSON service account key.
-* **`client_email`** [*required*]: Your email found in your JSON service account key.
-* **`automute`** [*optional*, *default*=**false**]: Silence monitors for expected GCE instance shutdowns.
-[1]: https://docs.datadoghq.com/integ...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteAGCPServiceAccount(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete the Datadog-Google Cloud Platform integration. [Read more about Datadog-Google Cloud Platform integration][1].
-### Arguments
-This endpoint takes no JSON argument.
-[1]: https://docs.datadoghq.com/integrations/google_cloud_platform</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getPagerDutyConfiguration(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-List all Datadog-PagerDuty integrations configured for your Datadog Account.
-### Arguments
-This endpoint takes no JSON argument.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">addNewServicesAndSchedules(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Add new services and schedules to your Datadog-PagerDuty integration. [Read more about Datadog-PagerDuty integration][1].
-### Arguments
-* **`services`** : Array of PagerDuty service objects. [Learn how to configure you Datadog service with PagerDuty documentation][2]. A PagerDuty service object is composed by:
-    * **`service_name`** [*required*]: Your Service name in PagerDuty.
-	* **`service_key`** [*required*]: Your Service name associated service key in Pagerduty.
-* **`schedu...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deletePagerDutyConfiguration(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete a Datadog-PagerDuty integration configured in your Datadog Account. [Read more about Datadog-PagerDuty integration][1].
-### Arguments
-This endpoint takes no JSON arguments
-[1]: https://docs.datadoghq.com/integrations/pagerduty</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getSlackConfigurationDetails(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-List all Datadog-Slack integrations configured for your Datadog Account.
-### Arguments
-This endpoint takes no JSON argument.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">addChannelsToExistingConfiguration(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Add channels to your existing Datadog-Slack integration directly through Datadog API. [Read more about Datadog-Slack integration][1].
-### Arguments
-* **`channels`** [*required*]: Array of slack channel objects to post to. A slack channel object is composed by:
-    * **`channel_name`** [*required*]: Your channel name e.g: `#general`, `#private`
-    * **`transfer_all_user_comments`** [*optional*, *default*=**False**]: To be notified for every comment on a graph, set it to `true`....(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteSlackConfigurationDetails(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete a Datadog-Slack integration configured in your Datadog Account. [Read more about Datadog-Slack integration][1].
-### Arguments
-This endpoint takes no JSON arguments
-[1]: https://docs.datadoghq.com/integrations/slack</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllWebhookConfigurations(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px"></td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">addToCurrentConfiguration(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">ARGUMENTS</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteWebhookConfigurations(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px"></td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">replaceCurrentConfiguration(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">ARGUMENTS</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllAPIKey(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get all API keys available for your account.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createANewAPIKey(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Create an API key with a given name.
-### Arguments
-* **`name`** [*required*]: Name of your API key.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAGivenAPIKey(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get a given API key.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">editAGivenAPIKey(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Edit an API key name.
-### Arguments
-* **`name`** [*required*]: Name of your API key.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteAnAPIKey(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete a given API key.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllApplicationKey(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get all application keys available for your account.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createANewApplicationKey(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Create an application key with a given name.
-### Arguments
-* **`name`** [*required*]: Name of your application key.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAGivenApplicationKey(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get a given application key.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">editAGivenApplicationKey(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Edit an application key name.
-### Arguments
-* **`name`** [*required*]: Name of your application key.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteAnApplicationKey(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete a given application key.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">sendLogsOverHTTP(body, ddsource, service, hostname, datadogApiKey, callback)</td>
-    <td style="padding:15px">### Overview
-Send your logs to your Datadog platform over HTTP. Limits per HTTP request are:
-* Maximum content size per payload: 2MB
-* Maximum size for a single log: 256kB
-* Maximum array size if sending multiple logs in an array: 50 entries
-**Note**: If you are in the Datadog EU site (`app.datadoghq.eu`), the HTTP log endpoint is: `http-intake.logs.datadoghq.eu`.
-### Arguments
-| Item             | Description                                                                                 ...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAListOfLogs(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-List endpoint returns logs that match a log search query. Results are paginated.
-### Arguments
-* **`query`** [*required*]: The search query - following the [Log search syntax][1] .
-* **`time.from`** [*required*]: Minimum timestamp for requested logs. Format can be either
-    - an ISO-8601 string
-    - a unix timestamp (number representing the elapsed millisec since epoch)
-    - a relative time (`now -10m`, `now - 1h`, `now - 1d`)
-* **`time.to`** [*required*]: Maximum timestamp fo...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllActiveMetrics(apiKey, applicationKey, from, host, callback)</td>
-    <td style="padding:15px">### Overview
-Get the list of actively reporting metrics from a given time until now. This endpoint is not available in the Python and Ruby libraries.
-### Arguments
-* **`from`** [*required*]: EPOCH timestamp from which to list metrics.
-* **`host`** [*optional*]: Hostname for filtering the list of metrics returned. If set, metrics retrieved are those with the corresponding hostname tag.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">sendTimeSeriesPoint(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-The metrics end-point allows you to post time-series data that can be graphed on Datadog's dashboards. The limit for compressed payloads is 3.2 megabytes (3200000), and 62 megabytes (62914560) for decompressed payloads.
-### Arguments
-* **`series`** [*required*]: Pass a JSON array where each item in the array contains the following arguments:
-    * **`metric`** [*required*]: The name of the timeseries
-    * **`type`** [*optional*, *default*=**gauge**]: [Type][1] of your metric ei...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">queryTimeSeriesPoints(apiKey, applicationKey, from, to, query, callback)</td>
-    <td style="padding:15px">### Overview
-This endpoint allows you to query for metrics from any time period.
-### Arguments
-* **`from`** [*required*]: EPOCH Timestamp from which to query metrics data.
-* **`to`** [*required*]: EPOCH Timestamp until which to query metrics data.
-* **`query`** [*required*]: The query string for the metric to retrieve. See [graphing documentation]() to learn how to build a metrics query.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">viewMetricMetadata(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-The metrics metadata endpoint allows you to get metadata about a specific metric.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">editMetricMetadata(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-The metrics metadata endpoint allows you to edit fields of a metric's metadata. [Find more about supported types][1]
-### Arguments
-* **`type`** [*required*]: [Metric type][1] such as **gauge** or **rate**
-* **`description`** [*optional*, *default*=**None**]: String description of the metric" default
-* **`short_name`** [*required*]: Short name string of the metric
-* **`unit`** [*optional*, *default*=**None**]: Primary unit of the metric such as **byte** or **operation**. [See the ...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">searchMetrics(q, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-This endpoint allows you to search for metrics from the last 24 hours in Datadog.
-### Arguments
-* `q` [*required*]: The query string. Must be prefixed with `metrics:`.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createAMonitor(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-If you manage and deploy monitors programmatically, it's easier to define the monitor in the Datadog UI and [export its valid JSON][1].
-### Arguments
-*   **`type`** [*required*]: The [type of the monitor][2], chosen from:
-| Monitor Type | type attribute value |
-| :--------    | :-------             |
-| anomaly      | `query alert`        |
-| apm          | `query alert`        |
-| composite    | `composite`          |
-| custom       | `service check`      |
-| event        | `eve...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAMonitorSDetails(apiKey, applicationKey, groupStates, callback)</td>
-    <td style="padding:15px">### Overview
-Get a monitor details based on its monitor ID.
-### Arguments
-* **`group_states`** [*optional*, *default*=**None**]: If this argument is set, the returned data includes additional information (if available) regarding the specified group states, including the last notification timestamp, last resolution timestamp and details about the last time the monitor was triggered. The argument should include a string list indicating what, if any, group states to include. Choose one or more f...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">editAMonitorSDetails(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Edit a monitor details based on its monitor ID.
-### Arguments
-* **`query`** [*required*]: The metric query to alert on.
-* **`name`** [*required*]: The name of the monitor.
-* **`message`** [*optional*, *default*=**dynamic, based on query**]: A message to include with notifications for this monitor. Email notifications can be sent to specific users by using the same '@username' notation as events.
-* **`options`** [*optional*, *default*=**{}**]: Refer to the create monitor documenta...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteAMonitor(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete a monitor based on its monitor ID.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">resolveMonitor(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Resolve a monitor by monitorId & Group.
-### Arguments
-* **`resolve`** [*required*]: Array of group(s) to resolve for a given monitor_id, e.g.: `{"monitor_id": "group_to_resolve"}`
-    * It supports multiple groups per monitor, e.g.: `resolve: [{"monitor_id": "group_1"}, {"monitor_id": "group_2"}]`
-    * It can also resolve all triggered groups with the pseudo-group `ALL_GROUPS`: `resolve: [{"monitor_id": "ALL_GROUPS"}]`</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">muteASpecificMonitor(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Mute a specific monitor base on its ID.
-### Arguments
-* **`scope`** [*optional*, *default*=**None**]: The scope to apply the mute to, e.g. **role:db**. For example, if your alert is grouped by `{host}`, you might mute `host:app1`.
-* **`end`** [*optional*, *default*=**None**]: A POSIX timestamp for when the mute should end.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">unmuteASpecificMonitor(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-### Arguments
-* **`scope`** [*optional*, *default*=**None**]: The scope to apply the mute to. For example, if your alert is grouped by {host}, you might mute 'host:app1'
-* **`all_scopes`** [*optional*, *default* = **False**]: Clear muting across all scopes</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">muteAllMonitors(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Muting prevents all monitors from notifying through email and posts to the [event stream][1]. State changes are only visible by checking the alert page.
-### Arguments
-This endpoint takes no JSON arguments.
-[1]: https://docs.datadoghq.com/graphing/event_stream</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">unmuteAllMonitors(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Disables muting all monitors. Throws an error if mute all was not enabled previously.
-### Arguments
-This endpoint takes no JSON arguments.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">validateAMonitorDefinitions(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Validates a monitor definition.
-### Arguments
-See [Create a monitor][1] documentation for details on constructing a monitor definition.
-[1]: https://docs.datadoghq.com/api/#create-a-monitor</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">monitorSearch(apiKey, applicationKey, query, page, perPage, sort, callback)</td>
-    <td style="padding:15px">### Overview
-Search and filter your monitors details.
-### Arguments
-* **`query`** [*optional*]: After entering a search query in your [Manage Monitor page][1] use the query parameter value in the URL of the page as value for this parameter. Consult the dedicated [manage monitor documentation][2] page to learn more. The query can contain any number of space-separated monitor attributes, for instance `query="type:metric status:alert"`.
-* **`page`** [*optional*, *default* = **0**]: Page to star...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">monitorGroupSearch(apiKey, applicationKey, query, page, perPage, sort, callback)</td>
-    <td style="padding:15px">### Overview
-Search and filter your monitor groups details.
-### ARGUMENTS
-* **`query`** [*optional*]: After entering a search query in your [Manage Monitor page][1] use the query parameter value in the URL of the page as value for this parameter. Consult the dedicated [manage monitor documentation][2] page to learn more.
-* **`page`** [*optional*, *default* = **0**]: Page to start paginating from.
-* **`per_page`** [*optional*, *default*=**30**]: Number of monitors to return per page.
-* **`s...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createChildOrganization(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-This endpoint requires the [multi-org account][1] feature and must be enabled by [contacting support][2].
-### Arguments
-* **`name`** [*required*]: The name of the new child-organization, limited to 32 characters.
-* **`subscription`** [*required*]: A JSON array of subscription type. Types available are `trial`, `free`, and `pro`.
-* **`billing`** [*required*]: A JSON array of billing type. Note that only `parent_billing` is supported.
-Once a new child-organization is created, you ...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllOrganizations(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get all child-organisation details for a given Master organisation.
-### Arguments
-This endpoint takes no JSON argument.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getOrganization(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get an organisation details based on its public ID.
-### Arguments
-* **`public_id`** [*required*]: The public id of the organization.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">updateOrganization(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Update a Datadog organization information.
-##### ARGUMENTS
-* **`name`** [*optional*]: The organization name.
-* **`settings`** [*optional*]: A JSON array of settings. Settings include:
-    * **`saml`** - Set the boolean property `enabled` to enable or disable single sign on with SAML. See the [SAML documentation][1] for more information about all SAML settings.
-    * **`saml_idp_initiated_login`** - has one property `enabled` (boolean).v
-    * **`saml_strict_mode`** - has one prope...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">uploadIDPMetadata(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-There are a couple of options for updating the Identity Provider (IdP) metadata from your SAML IdP.
-* **Multipart Form-Data**: Post the IdP metadata file using a form post.
-* **XML Body**: Post the IdP metadata file as the body of the request.
-### Multipart Form-Data
-#### Headers
-* **`Content-Type: multipart/form-data`**
-#### Arguments
-* **`idp_file`** [*required*]: The path to the XML metadata file you wish to upload.
-### XML Body
-#### Headers
-* **`Content-Type: applicatio...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">createATest(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Create a Synthetics test to initiate and configure the tests you want Datadog to send to your API endpoints or to your browser app. You can configure the endpoints being tested, the number of tests, and where they are coming from. The parameters required are different for API and browser tests and they are marked accordingly—if a parameter is marked as _required_, it is required for both types of tests. Once you create a test, it shows up in the UI in your [Synthetics list][1]
-A b...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllTests(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get a list of all existing tests.
-### Arguments
-*This endpoint takes no JSON arguments.*</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">startOrPauseATest(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Start or pause an existing Synthetics test.
-##### Arguments
-*   **`new_status`** - _required_ - A key-value pair where you define whether you want to start or pause a test. Valid values are `live` and `paused`. Returns `true` if the status has been changed, and `false` if the status has stayed the same.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">editATest(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Use this method to update an existing Synthetics test. In order to update a test, you have to submit the same payload as creating a test.
-The parameters required are different for API and browser tests and they are marked accordingly—if a parameter is marked as _required_, it is required for both types of tests.
-A browser test is treated like a GET API test. This method gives you the ability to update the browser test, but you have to use the UI to [record your test][1].
-In orde...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">deleteATest(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Delete one or many tests.
-### Arguments
-*   **`public_ids`** - _required_ - A JSON list of the ID or IDs of the tests that you want to delete.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAllTestResults(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get the most recent results for a specific test.
-### Arguments
-*This endpoint takes no JSON arguments.*</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getASpecificTestResult(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get a specific result for a specific test.
-### Arguments
-*This endpoint takes no JSON arguments.*</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getATest(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get information on a specific test.
-### Arguments
-*This endpoint takes no JSON arguments.*</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getDevicesForBrowserChecks(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get a list of devices for browser checks.
-### Arguments
-*This endpoint takes no JSON arguments.*</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getAvailableLocations(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Get a list of available locations
-### Arguments
-*This endpoint takes no JSON arguments.*</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getTags(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Return a mapping of tags to hosts for your whole infrastructure.
-### Arguments
-*This endpoint takes no JSON arguments.*</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getHostTags(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Return the list of tags that apply to a given host.
-### Arguments
-*This endpoint takes no JSON arguments.*</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">addTagsToAHost(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-This endpoint allows you to add new tags to a host, optionally specifying where these tags come from.
-### Arguments
-* **`tags`** [*required*]: A list of tags to apply to the host
-* **`source`** [*optional*, *default*=**users**]: The source of the tags (e.g. chef, puppet). [Complete list of source attribute values][1]
-[1]: https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">updateHostTags(body, apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-This endpoint allows you to update/replace all tags in an integration source with those supplied in the request.
-### Arguments
-* **`tags`** [*required*]: A list of tags
-* **`source`** [*optional*, *default*=**users**]: The source of the tags (e.g. chef, puppet). [Complete list of source attribute values][1]
-[1]: https://docs.datadoghq.com/integrations/faq/list-of-api-source-attribute-value</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">removeHostTags(apiKey, applicationKey, callback)</td>
-    <td style="padding:15px">### Overview
-Remove all tags in an integration source for a single host.
-### Arguments
-*This endpoint takes no JSON arguments.*</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">sendTraces(body, callback)</td>
-    <td style="padding:15px">### Overview
-Datadog's APM allows you to collect performance metrics by tracing your code to determine which parts of your application are slow or inefficient.
-Tracing data is sent to the Datadog Agent via an HTTP API. We provide some [official libraries][1] that simplify sending metrics to the Datadog Agent, however you may want to interact directly with the API to instrument applications that cannot use the libraries or are written in languages that don't yet have an official Datadog Tracing...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">sendServices(body, callback)</td>
-    <td style="padding:15px">https://docs.datadoghq.com/api/?lang=bash#send-traces</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getHostsAndContainersHourlyUsage(apiKey, applicationKey, startHr, endHr, callback)</td>
-    <td style="padding:15px">### Overview
-Get Hourly Usage For Hosts and Containers.
-### Arguments
-* **`start_hr`** [*required*]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour
-* **`end_hr`** [*optional*, *default*=**1d+start_hr**]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending BEFORE this hour
-#### Response
-* **`container_count`**: Shows the total number of containers reporting via the Docker integration during the hour.
-* **`ho...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getLogsHourlyUsage(apiKey, applicationKey, startHr, endHr, callback)</td>
-    <td style="padding:15px">### Overview
-Get Hourly Usage For Logs.
-### Arguments
-* **`start_hr`** [*required*]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour
-* **`end_hr`** [*optional*, *default*=**1d+start_hr**]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending BEFORE this hour
-#### Response
-* **`ingested_events_bytes`**: Contains the number of log bytes ingested.
-* **`indexed_events_count`**: Contains the number of log events in...(description truncated)</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getCustomMetricsHourlyUsage(apiKey, applicationKey, startHr, endHr, callback)</td>
-    <td style="padding:15px">### Overview
-Get Hourly Usage For [Custom Metrics][1].
-### Arguments
-* **`start_hr`** [*required*]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour
-* **`end_hr`** [*optional*, *default*=**1d+start_hr**]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending BEFORE this hour
-[1]: https://docs.datadoghq.com/developers/metrics/custom_metrics</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getTop500CustomMetricsByHourlyAverage(apiKey, applicationKey, month, names, callback)</td>
-    <td style="padding:15px">### Overview
-Get Top [Custom Metrics][1] By Hourly Average.
-### Arguments
-* **`month`** [*required*]: Datetime in ISO-8601 format, UTC, precise to month: [YYYY-MM] for usage beginning at this hour.
-* **`names`** [*optional*, *default*=**None**]: Comma-separated list of metric names.
-[1]: https://docs.datadoghq.com/developers/metrics/custom_metrics</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getMultiOrgUsageDetails(apiKey, applicationKey, startMonth, endMonth, includeOrgIds, callback)</td>
-    <td style="padding:15px">### Overview
-Get usage across your multi-org account
-### Arguments
-* **`start_month`** [*required*]: Datetime in ISO-8601 format, UTC, precise to month: [YYYY-MM] for usage beginning in this month. Maximum of 15 months ago.
-* **`end_month`** [*optional*, *default*=**current_month-3d**]: Datetime in ISO-8601 format, UTC, precise to month: [YYYY-MM] for usage ending this month.
-* **`include_org_details`** [*optional*, *default*=**true**]: Include usage summaries for each sub-org.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getTraceSearchHourlyUsage(apiKey, applicationKey, startHr, endHr, callback)</td>
-    <td style="padding:15px">### Overview
-Get hourly usage For Trace Search.
-### Arguments
-* **`start_hr`** [*required*]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour
-* **`end_hr`** [*optional*, *default*=**1d+start_hr**]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending BEFORE this hour
-#### Response
-* **`indexed_events_count`**: Contains the number of Trace Search events indexed.
-* **`hour`**: The hour for the usage.</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">getFargateHourlyUsage(apiKey, applicationKey, startHr, endHr, callback)</td>
-    <td style="padding:15px">### Overview
-Get Hourly Usage For [Fargate][1].
-### Arguments
-* **`start_hr`** [*required*]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage beginning at this hour
-* **`end_hr`** [*optional*, *default*=**1d+start_hr**]: Datetime in ISO-8601 format, UTC, precise to hour: [YYYY-MM-DDThh] for usage ending BEFORE this hour
-[1]: https://docs.datadoghq.com/integrations/ecs_fargate</td>
-    <td style="padding:15px">{base_path}/{version}?{query}</td>
-    <td style="padding:15px">Yes</td>
-  </tr>
-</table>
-<br>
-### Authentication
-This document will go through the steps for authenticating the Datadog adapter with Basic Authentication. Properly configuring the properties for an adapter in IAP is critical for getting the adapter online. You can read more about adapter authentication <a href="https://www.itential.com/automation-platform/integrations/adapters-resources/authentication/" target="_blank">HERE</a>.
-#### Basic Authentication
-The Datadog adapter requires Basic Authentication. If you change authentication methods, you should change this section accordingly and merge it back into the adapter repository.
-STEPS
-1. Ensure you have access to a Datadog server and that it is running
-2. Follow the steps in the README.md to import the adapter into IAP if you have not already done so
-3. Use the properties below for the ```properties.authentication``` field
-```json
-"authentication": {
-  "auth_method": "basic user_password",
-  "username": "<username>",
-  "password": "<password>",
-  "token": "",
-  "token_timeout": 1800000,
-  "token_cache": "local",
-  "invalid_token_error": 401,
-  "auth_field": "header.headers.Authorization",
-  "auth_field_format": "Basic {b64}{username}:{password}{/b64}",
-  "auth_logging": false,
-  "client_id": "",
-  "client_secret": "",
-  "grant_type": ""
-}
-```
-4. Restart the adapter. If your properties were set correctly, the adapter should go online.
-#### Troubleshooting
-- Make sure you copied over the correct username and password.
-- Turn on debug level logs for the adapter in IAP Admin Essentials.
-- Turn on auth_logging for the adapter in IAP Admin Essentials (adapter properties).
-- Investigate the logs - in particular:
-  - The FULL REQUEST log to make sure the proper headers are being sent with the request.
-  - The FULL BODY log to make sure the payload is accurate.
-  - The CALL RETURN log to see what the other system is telling us.
-- Remember when you are done to turn auth_logging off as you do not want to log credentials.
-## Additional Information
-### Enhancements
-#### Adding a Second Instance of an Adapter
-You can add a second instance of this adapter without adding new code on the file system. To do this go into the IAP Admin Essentials and add a new service config for this adapter. The two instances of the adapter should have unique ids. In addition, they should point to different instances (unique host and port) of the other system.
-#### Adding Adapter Calls
-There are multiple ways to add calls to an existing adapter.
-The easiest way would be to use the Adapter Builder update process. This process takes in a Swagger or OpenAPI document, allows you to select the calls you want to add and then generates a zip file that can be used to update the adapter. Once you have the zip file simply put it in the adapter directory and execute `npm run adapter:update`.
-```bash
-mv updatePackage.zip adapter-datadog
-cd adapter-datadog
-npm run adapter:update
-```
-If you do not have a Swagger or OpenAPI document, you can use a Postman Collection and convert that to an OpenAPI document using APIMatic and then follow the first process.
-If you want to manually update the adapter that can also be done the key thing is to make sure you update all of the right files. Within the entities directory you will find 1 or more entities. You can create a new entity or add to an existing entity. Each entity has an action.json file, any new call will need to be put in the action.json file. It will also need to be added to the enum for the ph_request_type in the appropriate schema files. Once this configuration is complete you will need to add the call to the adapter.js file and, in order to make it available as a workflow task in IAP, it should also be added to the pronghorn.json file. You can optionally add it to the unit and integration test files. There is more information on how to work on each of these files in the <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a> on our Documentation Site.
-```text
-Files to update
-* entities/<entity>/action.json: add an action
-* entities/<entity>/schema.json (or the schema defined on the action): add action to the enum for ph_request_type
-* adapter.js: add the new method and make sure it calls the proper entity and action
-* pronghorn.json: add the new method
-* test/unit/adapterTestUnit.js (optional but best practice): add unit test(s) - function is there, any required parameters error when not passed in
-* test/integration/adapterTestIntegration.js (optional but best practice): add integration test
-```
-#### Adding Adapter Properties
-While changing adapter properties is done in the service instance configuration section of IAP, adding properties has to be done in the adapter. To add a property you should edit the propertiesSchema.json with the proper information for the property. In addition, you should modify the sampleProperties to have the new property in it.
-```text
-Files to update
-* propertiesSchema.json: add the new property and how it is defined
-* sampleProperties: add the new property with a default value
-* test/unit/adapterTestUnit.js (optional but best practice): add the property to the global properties
-* test/integration/adapterTestIntegration.js (optional but best practice): add the property to the global properties
-```
-#### Changing Adapter Authentication
-Often an adapter is built before knowing the authentication and authentication processes can also change over time. The adapter supports many different kinds of authentication but it does require configuration. Some forms of authentication can be defined entirely with the adapter properties but others require configuration.
-```text
-Files to update
-* entities/.system/action.json: change the getToken action as needed
-* entities/.system/schemaTokenReq.json: add input parameters (external name is name in other system)
-* entities/.system/schemaTokenResp.json: add response parameters (external name is name in other system)
-* propertiesSchema.json: add any new property and how it is defined
-* sampleProperties: add any new property with a default value
-* test/unit/adapterTestUnit.js (optional but best practice): add the property to the global properties
-* test/integration/adapterTestIntegration.js (optional but best practice): add the property to the global properties
-```
-#### Enhancing Adapter Integration Tests
-The adapter integration tests are written to be able to test in either stub (standalone) mode or integrated to the other system. However, if integrating to the other system, you may need to provide better data than what the adapter provides by default as that data is likely to fail for create and update. To provide better data, edit the adapter integration test file. Make sure you do not remove the marker and keep custom code below the marker so you do not impact future migrations. Once the edits are complete, run the integration test as it instructs you to above. When you run integrated to the other system, you can also save mockdata for future use by changing the isSaveMockData flag to true.
-```text
-Files to update
-* test/integration/adapterTestIntegration.js: add better data for the create and update calls so that they will not fail.
-```
-As mentioned previously, for most of these changes as well as other possible changes, there is more information on how to work on an adapter in the <a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a> on our Documentation Site.
-### Contributing
-First off, thanks for taking the time to contribute!
-The following is a set of rules for contributing.
-#### Code of Conduct
-This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to support@itential.com.
-#### How to Contribute
-Follow the contributing guide (here)[https://gitlab.com/itentialopensource/adapters/contributing-guide]
-### Helpful Links
-<a href="https://docs.itential.com/opensource/docs/adapters" target="_blank">Adapter Technical Resources</a>
-### Node Scripts
-There are several node scripts that now accompany the adapter. These scripts are provided to make several activities easier. Many of these scripts can have issues with different versions of IAP as they have dependencies on IAP and Mongo. If you have issues with the scripts please report them to the Itential Adapter Team. Each of these scripts are described below.
-<table border="1" class="bordered-table">
-  <tr>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Run</span></th>
-    <th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run adapter:install</td>
-    <td style="padding:15px">Provides an easier way to install the adapter.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run adapter:checkMigrate</td>
-    <td style="padding:15px">Checks whether your adapter can and should be migrated to the latest foundation.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run adapter:findPath</td>
-    <td style="padding:15px">Can be used to see if the adapter supports a particular API call.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run adapter:migrate</td>
-    <td style="padding:15px">Provides an easier way to update your adapter after you download the migration zip from Itential DevSite.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run adapter:update</td>
-    <td style="padding:15px">Provides an easier way to update your adapter after you download the update zip from Itential DevSite.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run adapter:revert</td>
-    <td style="padding:15px">Allows you to revert after a migration or update if it resulted in issues.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run troubleshoot</td>
-    <td style="padding:15px">Provides a way to troubleshoot the adapter - runs connectivity, healthcheck and basic get.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run connectivity</td>
-    <td style="padding:15px">Provides a connectivity check to the Servicenow system.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run healthcheck</td>
-    <td style="padding:15px">Checks whether the configured healthcheck call works to Servicenow.</td>
-  </tr>
-  <tr>
-    <td style="padding:15px">npm run basicget</td>
-    <td style="padding:15px">Checks whether the basic get calls works to Servicenow.</td>
-  </tr>
-</table>
-<br>
-## Troubleshoot
-Run `npm run troubleshoot` to start the interactive troubleshooting process. The command allows you to verify and update connection, authentication as well as healthcheck configuration. After that it will test these properties by sending HTTP request to the endpoint. If the tests pass, it will persist these changes into IAP.
-You also have the option to run individual commands to perform specific test:
-- `npm run healthcheck` will perform a healthcheck request of with current setting.
-- `npm run basicget` will perform some non-parameter GET request with current setting.
-- `npm run connectivity` will perform networking diagnostics of the adatper endpoint.
-### Connectivity Issues
-1. You can run the adapter troubleshooting script which will check connectivity, run the healthcheck and run basic get calls.
-```bash
-npm run troubleshoot
-```
-2. Verify the adapter properties are set up correctly.
-```text
-Go into the Itential Platform GUI and verify/update the properties
-```
-3. Verify there is connectivity between the Itential Platform Server and Datadog Server.
-```text
-ping the ip address of Datadog server
-try telnet to the ip address port of Datadog
-execute a curl command to the other system
-```
-4. Verify the credentials provided for Datadog.
-```text
-login to Datadog using the provided credentials
-```
-5. Verify the API of the call utilized for Datadog Healthcheck.
-```text
-Go into the Itential Platform GUI and verify/update the properties
-```
-### Functional Issues
-Adapter logs are located in `/var/log/pronghorn`. In older releases of the Itential Platform, there is a `pronghorn.log` file which contains logs for all of the Itential Platform. In newer versions, adapters can be configured to log into their own files.
+## [Generic Adapter Information](https://gitlab.com/itentialopensource/adapters/telemetry-analytics/adapter-datadog/-/blob/master/README.md)