---
releases:
- name: datadog-agent
  sha1: 7ba4b58c95812ecda39fd0bcf16cb8d3635c2ecd
  url: https://github.com/alphagov/paas-datadog-agent-boshrelease/releases/download/custom_007/datadog-agent-custom_007.tgz
  version: "custom_007"

meta:
  datadog:
    api_key: (( grab $DATADOG_API_KEY || "undefined" ))
    use_dogstatsd: false
  datadog_tags:
    environment: (( grab meta.environment || "undefined" ))
    aws_account: (( grab $AWS_ACCOUNT ))

---
releases:
- name: datadog-agent
  sha1: 14c7f9be2eb534fda1f4c70ea2355865ac93a87b
  url: https://github.com/alphagov/paas-datadog-agent-boshrelease/releases/download/v5.8.5.3-gds/datadog-agent-v5.8.5.3-gds.tgz
  version: "v5.8.5.3-gds"

meta:
  datadog:
    api_key: (( grab $DATADOG_API_KEY || "undefined" ))
    use_dogstatsd: false
    include_bosh_tags: true
  datadog_tags:
    environment: (( grab meta.environment || "undefined" ))
    aws_account: (( grab $AWS_ACCOUNT ))

Upgrade datadog agent and enable bosh tags
Upgrade datadog agent and enable bosh tags

The host names of our virtual machines are Bosh UUIDs in Datadog, which
is not very user friendly and makes metrics hard to find and read.

This PR was merged upstream [1] which adds tags to identify
the bosh job and index, which we can use in our checks and graphs. This
PR is merged back to our fork [2].

We add these changes to the manifest.

[1] https://github.com/onemedical/datadog-agent-boshrelease/pull/8
[2] https://github.com/alphagov/paas-datadog-agent-boshrelease/pull/7
