1.6.0

[1.6.0] - 2018-11-08

Updated the run script to provide a better way for users to arbitrarily modify the environment and configurations.

Added

• Added prerun.sh support so users can modify the environment and configurations
• Added appropriate documentation. Thanks to @abtreece for the postgres auto config idea!

Changed

• Updated the way python_path is built to be more reliable (uses find instead of ls)
• Updated the postgres integration documentation to include more details, including ssl enabling (required by hosted Heroku postgres)

1.5.0

[1.5.0] - 2018-08-27

External keyservers were becoming an issue for reliability so the Datadog public key has been added to the buildpack. A few updates were made regarding Agent versioning and the documentation was clarified.

Added

• Added the Datadog public PGP key.
• Invalid pinned versions of the Datadog Agent now returns a list of valid options.

Changed

• Now uses the included PGP key to validate the Datadog package
• Datadog Agent from version 6.4.1 now uses the run command. Previous versions will still use start

1.4.1

[1.4.1] - 2018-08-20

Thanks to pawelchcki for spotting that the integration support lacked a check if no integration files existed. This update fixes an issue where the Datadog Trace Agent may fail to start or drop traces.

Added

• A small check to ensure integration configuration files exist when running logic to import them.

1.4.0

[1.4.0] - 2018-07-31

Thanks to lucasm-iRonin for adding functionality to support Datadog Agent integrations!

Changed

• Now using sks-keyservers instead of ubuntu keyservers. This should increase reliability

Added

• Basic Datadog Agent integration support.

Removed

• Removed docs referencing Datadog documentation site. That site will soon pull from this repo.

1.3.4

[1.3.4] - 2018-06-11

Thanks to @dreid for help resolving the apt-key issue, fixing compatibility with the Heroku-18 stack.

Changed

• Fixed apt-key issue, buildpack compatibility with Heroku-18 stack.
• Fixed PYTHONPATH issue preventing python-based core integrations from running.
• Set APM log location resulting in log location related errors. APM log is now at /app/.apt/etc/datadog/datadog-apm.log

1.3.3

[1.3.3] - 2018-06-01

Changed

• Removed dynohost tag

1.3.2

[1.3.2] - 2018-05-21

Hostnames are not always RFC1123 compliant. Invalid hostnames led to unexpected non-reporting.

Changed

• Updated documentation to mention enabling Heroku Labs metadata (required for DD_DYNO_HOST)

Added

• Added a check for non-compliant hostnames. Buildpack will rename and throw a warning

1.3.1

[1.3.1] - 2018-04-26

Using dyno name as hostname was not properly namespaced, so multiple apps would have dyno hostname collisions. Appname has been added to prevent this.

Changed

• DD_DYNO_HOST reports hosts as appname.dynoname.

1.3.0

[1.3.0] - 2018-04-24

Fixed an issue where custom tags completely override the built-in tags for dyno information. Added a switch to change the hostname from host to dyno. This will provide some flexibility and control in how you are billed by Datadog.

Changed

• DD_TAGS will now merge with other tags set by the buildpack, rather than overriding them.

Added

• DD_DYNO_HOST will allow you to set the agent hostname to the dyno name, rather than host.
• Added a tag for dynotype.

1.2.0

[1.2.0] - 2018-04-11

Changed buildpack to use dyno hostnames rather than setting the application name as the hostname. Though the previous method helped simplify continuity, it led to metrics aggregation errors for applications running many dynos. The application name is now available under the "appname" tag when Heroku Labs Dyno Metadata is enabled or the "HEROKU_APP_NAME" environment variable is set.

Changed

• Hostname will default to dyno host name, unless DD_HOSTNAME is set (not recommended)

Added

• Application name added as "appname" tag.

Removed

• Removed README documentation about histogram percentiles and APM that were not specific to the buildpack. See https://docs.datadoghq.com for information about those features.