You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
It appears that every time a terraform apply is run, the Dynatrace Terraform resources get recreated. This is especially true for e.g. dashboards, which completly clutters the dry run (terraform plan) making it hard to check planned changes to our infrastructure, seeing as some dashboards consist of thousands of lines of json code. Though an even greater issue we face with the Dynatrace Terraform provider is that between applies, different metric selectors are applied to the same metric event, as seen:
This issue shows the wrong metric selector for the correct metric event.
When checking the correct metric selector, it shows different values for different time intervals though at the same point in time
To Reproduce
I do not think this is easily reproducible
Expected behavior
Consistent behaviour between terraform applies, so that the metric selector defined in code is actually used.
Sorry for the late response - somehow we didn't notice the new ticket. Dynatrace ONE just reached out to us. Since you already have a Support Ticket open, I would suggest to continue the discussion in there.
Describe the bug
It appears that every time a
terraform apply
is run, the Dynatrace Terraform resources get recreated. This is especially true for e.g. dashboards, which completly clutters the dry run (terraform plan) making it hard to check planned changes to our infrastructure, seeing as some dashboards consist of thousands of lines of json code. Though an even greater issue we face with the Dynatrace Terraform provider is that between applies, different metric selectors are applied to the same metric event, as seen:This issue shows the wrong metric selector for the correct metric event.
When checking the correct metric selector, it shows different values for different time intervals though at the same point in time
To Reproduce
I do not think this is easily reproducible
Expected behavior
Consistent behaviour between
terraform applies
, so that the metric selector defined in code is actually used.For reference, we have already created a Dynatrace Support Ticket:
https://one.dynatrace.com/hc/en-us/requests/394230
The text was updated successfully, but these errors were encountered: