Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Datadog Timeboard: Metadata key #61

Closed
skyzyx opened this issue Apr 19, 2018 · 11 comments · Fixed by #215
Closed

Datadog Timeboard: Metadata key #61

skyzyx opened this issue Apr 19, 2018 · 11 comments · Fixed by #215

Comments

@skyzyx
Copy link

skyzyx commented Apr 19, 2018

Terraform Version

Terraform v0.11.7
+ provider.aws v1.8.0
+ provider.datadog v1.0.3

Affected Resource(s)

Please list the resources as a list, for example:

Terraform Configuration Files

Trying to take the JSON config from a dashboard I created in Datadog, and port it to HCL so that I can manage it with Terraform. It appears that the metadata key is not supported yet by this provider.

The JSON config for Datadog is:

{
  "requests": [
    {
      "q": "sum:aws.trustedadvisor.green_checks, sum:aws.trustedadvisor.yellow_checks, sum:aws.trustedadvisor.red_checks",
      "type": "bars",
      "style": {
        "palette": "dog_classic",
        "type": "solid",
        "width": "normal"
      },
      "metadata": {
        "sum:aws.trustedadvisor.green_checks": {
          "alias": "OK"
        },
        "sum:aws.trustedadvisor.yellow_checks": {
          "alias": "WARN"
        },
        "sum:aws.trustedadvisor.red_checks": {
          "alias": "ERROR"
        }
      },
      "conditional_formats": []
    }
  ],
  "viz": "timeseries",
  "autoscale": true
}
@vineethvijay
Copy link

+1
This would be a nice feature to have, for making meaningful metadata over the graph rather than the query metric names.

@LozanoMatheus
Copy link

+1

@andreitchaltsev
Copy link

+1 to the feature.
For complicated queries the formulas may be unreadable. Having nice alias would be very helpful.

@andreafalzetti
Copy link

Anyone looking into this?

@cyprianos
Copy link

+1

2 similar comments
@michaelfoley1
Copy link

+1

@trp956s
Copy link

trp956s commented Apr 8, 2019

+1

@JohnB
Copy link

JohnB commented Apr 8, 2019

+111

@infrat
Copy link

infrat commented May 15, 2019

+1

@bkabrda
Copy link
Contributor

bkabrda commented May 16, 2019

Hey folks, I'm working on this right now. As the first step, I opened a PR to add support to the go client library: zorkian/go-datadog-api#241 - implementing this in the provider should be pretty easy after that PR is accepted.

@bkabrda
Copy link
Contributor

bkabrda commented May 20, 2019

So I seem to be running into an issue with complex nested structures handling in terraform while trying to implement this in the provider. Basically it seems I'm hitting [1]. I'm currently in discussion with Hasicorp folks to figure out a workable solution for this case. I'll keep this issue updated with the progress. Thanks for your patience everyone!

[1] https://github.com/hashicorp/terraform/issues/6215

jbenais pushed a commit to jbenais/terraform-provider-datadog that referenced this issue Aug 20, 2019
jbenais pushed a commit to jbenais/terraform-provider-datadog that referenced this issue Aug 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.