{{< site-region region="us5,gov" >}}

{{< /site-region >}}

Custom commands provide a way to trace individual commands in your CI pipelines, allowing you to measure the time your command takes without taking into account any setup or teardown actions that the job might have (for example, downloading Docker images or waiting for an available node in a Kubernetes-based infrastructure). These spans appear as part of the pipeline's trace:

Specify a valid [Datadog API key][2] in the `DATADOG_API_KEY` environment variable. For example:

DATADOG_API_KEY=&lt;key&gt; DATADOG_SITE={{< region-param key="dd_site" >}} datadog-ci trace \

--name "Greet" \

-- \

</pre>

{{< /site-region >}}

{{< site-region region="us5,gov" >}}

{{< /site-region >}}

{{< site-region region="us5,gov" >}}

{{< /site-region >}}

JUnit test report files are XML files that contain test execution information, such as test and suite names, pass/fail status, duration, and sometimes error logs. Although it was introduced by the [JUnit][1] testing framework, many other popular frameworks are able to output results using this format.

As an alternative to instrumenting your tests natively using Datadog tracers, which is the recommended option as it provides the most comprehensive test results, you can also upload JUnit XML test reports.

Specify a valid [Datadog API key][3] in the `DATADOG_API_KEY` environment variable, and the environment where tests were run (for example, `local` when uploading results from a developer workstation, or `ci` when uploading them from a CI provider) in the `DD_ENV` environment variable. For example:

--service my-api-service \

unit-tests/junit-reports e2e-tests/single-report.xml

</code>

</pre>

: [Datadog API key][3] used to authenticate the requests.<br/>

**Default**: (none)

Additionally, configure the Datadog site to use the selected one ({{< region-param key="dd_site_name" >}}):

`DATADOG_SITE` (Required)

**Default**: `datadoghq.com`<br/>

**Selected site**: {{< region-param key="dd_site" code="true" >}}

If you are running tests in non-supported CI providers or with no `.git` folder, you can set the Git information manually using environment variables. These environment variables take precedence over any auto-detected information. Set the following environment variables to provide Git information:

</testsuites>

{{< /code-block >}}

[1]: https://junit.org/junit5/

[2]: https://www.npmjs.com/package/@datadog/datadog-ci

[3]: https://app.datadoghq.com/organization-settings/api-keys

{{< site-region region="us5,gov" >}}

{{< /site-region >}}

Supported languages:

**Recommended**: `$(SRCROOT)`<br/>

**Example**: `/Users/ci/source/MyApp`

Additionally, configure the Datadog site to use the selected one ({{< region-param key="dd_site_name" >}}):

`DD_SITE` (Required)

**Default**: `datadoghq.com`<br/>

**Selected site**: {{< region-param key="dd_site" code="true" >}}

After installation, run your tests as you normally do, for example using the `xcodebuild test` command. Tests, network requests, and application logs are instrumented automatically. Pass your environment variables when running your tests in the CI, for example:

DD_TEST_RUNNER=1 DD_ENV=ci DD_SITE={{< region-param key="dd_site" >}} xcodebuild \

-project "MyProject.xcodeproj" \

-scheme "MyScheme" \

-destination "platform=macOS,arch=x86_64" \

test

</code>

</pre>

{{% /tab %}}

{{< /tabs >}}

{{< partial name="whats-next/whats-next.html" >}}

{{< site-region region="us3,us5,gov" >}}

<div class="alert alert-warning">

</div>

{{< /site-region >}}

{{< site-region region="us,eu" >}}

<div class="alert alert-warning">

</div>

{{< /site-region >}}

3. Edit the **Datadog Authentication** environment to add in your Datadog [API key][2] as the initial value and current value for the `api_key` variable, and add your Datadog [application key][2] as the initial value and current value for the `application_key` variable.

1. In the Datadog API Collection folder on the left pane, click the three dot menu, and then select **Edit**.

3. Click **Update**.

After setup is complete, you are ready to begin making API calls. In the Postman -> Datadog folder, there are subfolders for each type of API category listed in the [Datadog API Reference][7]. Expand the subfolders to see the HTTP methods and API call names.

{{< site-region region="gov" >}}

{{< /site-region >}}

To install the Datadog Agent on a host, use the [one line install command][6] updated with your [Datadog API key][7]:

Verify the Agent is running with the [status command][8]:

integration_id: "adobe"

Collect Adobe Experience Manager logs to track errors, request response time, and track badly performing web pages.

_Available for Agent version >6.0_

1. Collecting logs is disabled by default in the Datadog Agent. Enable it in your `datadog.yaml` file with:

logs_enabled: true

```

```yaml

Change the `path` and `service` parameter values and configure them for your environment.

[1]: https://app.datadoghq.com/account/settings#agent