Deploying Metric Drains with Aptible’s Terraform Provider is relativley straight-forward, with some minor configuration exceptions. Aptible’s Terraform Provider uses the Aptible CLI for authorization and authentication, so please run aptible login before we get started.


  1. Terraform
  2. The Aptible CLI

You also need to be logged in to Aptible.

$ aptible login

Getting Started

First, lets set up your Terraform directory to work with Aptible. Create a directory with a file and then run terraform init in the root of the directory.

Next, you will define where you want your metric drain to capture metrics. Whether this is a new environment or an exisiting one. If you are placing this in an exisiting environment you can skip this step, just make sure you have your environment ID.

data "aptible_stack" "test-stack" {
    name = "test-stack"

resource "aptible_environment" "test-env" {
    stack_id = data.aptible_stack.test-stack.stack_id
    // if you use a shared stack above, you will have to manually grab your org_id
    org_id = data.aptible_stack.test-stack.org_id
    handle = "test-env"

Next, we will actually create the metric drain resource in Terraform, please select the drain type you wish to use from below.

resource "aptible_metric_drain" "datadog_drain" {
env_id     = data.aptible_environment.example.env_id
drain_type = "datadog"
api_key    = "xxxxx-xxxxx-xxxxx"

To check to make sure your changes are valid (in case of any changes not mentioned), run terraform validate

To deploy the above changes, run terraform apply


App configuration issues with Datadog

Some users have reported issues with applications not sending logs to Datadog, applications will need additional configuration set. Below is an example.

    resource "aptible_app" "load-test-datadog" {
        env_id = data.aptible_environment.example_environment.env_id
        handle = "example-app"
        config = {
            "APTIBLE_DOCKER_IMAGE" : "",
            "DD_APM_NON_LOCAL_TRAFFIC" : true,
            "DD_BIND_HOST" : "",
            "DD_API_KEY" :"xxxxx-xxxxx-xxxxx",
            "DD_ENV" : "your environment",
            "DD_HOSTNAME" : "dd-hostname" # this does not have to match the hostname
        service {
            process_type = "cmd"
            container_count = 1
            container_memory_limit = 1024

As a final note, if you have any questions about the Terraform provider please reach out to support or checkout our public Terraform Provider Repository for more information!