Supported OS:
This check watches for successful build-related events and sends them to Datadog.
Unlike most Agent checks, this one doesn’t collect any metrics—just events.
The Teamcity check is included in the Datadog Agent package, so you don’t need to install anything else on your Teamcity servers.
Follow Teamcity’s documentation to enable Guest Login.
Follow the instructions below to configure this check for an Agent running on a host. For containerized environments, see the Containerized section.
Edit the teamcity.d/conf.yaml in the conf.d/ folder at the root of your Agent’s configuration directory. See the sample teamcity.d/conf.yaml for all available configuration options:
init_config:
instances:
- name: My Website
server: teamcity.mycompany.com
# the internal build ID of the build configuration you wish to track
build_configuration: MyWebsite_DeployAdd an item like the above to instances for each build configuration you want to track.
Restart the Agent to start collecting and sending Teamcity events to Datadog.
For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.
| Parameter | Value |
|---|---|
<INTEGRATION_NAME> | teamcity |
<INIT_CONFIG> | blank or {} |
<INSTANCE_CONFIG> | {"name": "<BUILD_NAME>", "server":"%%host%%", "build_configuration":"<BUILD_CONFIGURATION_ID>"} |
Run the Agent’s status subcommand and look for teamcity under the Checks section.
The Teamcity check does not include any metrics.
Teamcity events representing successful builds are forwarded to your Datadog application.
The Teamcity check does not include any service checks.
Need help? Contact Datadog support.
On this Page
