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.
Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.
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.
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
# server: user:password@teamcity.mycompany.com # if you set basic_http_authentication to true
# basic_http_authentication: true # default is false
build_configuration: MyWebsite_Deploy # the internal build ID of the build configuration you wish to track
# host_affected: msicalweb6 # defaults to hostname of the Agent's host
# is_deployment: true # causes events to use the word 'deployment' in their messaging
# ssl_validation: false # default is true
# tags: # add custom tags to events
# - test
Add 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.
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.
Mistake in the docs? Feel free to contribute!