v1.22.1

• Fixed #210
• The -datasources argument for the export functionality wrongfully deleted generated module folders in certain cases
• Introduced the environment variable DYNATRACE_HTTP_ERROR_RESPONSE_HEADERS to allow for diagnosing the origin of BAD REQUEST responses.

v1.22.0

New Resources

• dynatrace_browser_monitor_outage introduces configuration for browser monitor outage handling (Certains field(s) of this resource has overlap with another, please refer to the resource docs for additional info)
• dynatrace_http_monitor_outage introduces configuration for HTTP monitor outage handling (Certains field(s) of this resource has overlap with another, please refer to the resource docs for additional info)
• dynatrace_cloudapp_workloaddetection merges processes of similar workloads into process groups, and consequently, services. Please note that fine-grained process detection rules will still be applied, while ignoring container or platform specific properties
• dynatrace_mainframe_transaction_monitoring covers additional monitoring settings for CICS and IMS transactions
• dynatrace_monitored_technologies_apache covers configuration to enable/disable Apache HTTP Server monitoring
• dynatrace_monitored_technologies_dotnet covers configuration to enable/disable .NET monitoring
• dynatrace_monitored_technologies_go covers configuration to enable/disable Golang monitoring
• dynatrace_monitored_technologies_iis covers configuration to enable/disable IIS monitoring
• dynatrace_monitored_technologies_java covers configuration to enable/disable Java monitoring
• dynatrace_monitored_technologies_nginx covers configuration to enable/disable Nginx monitoring
• dynatrace_monitored_technologies_nodejs covers configuration to enable/disable NodeJS monitoring
• dynatrace_monitored_technologies_opentracing covers configuration to enable/disable OpenTracing monitoring
• dynatrace_monitored_technologies_php covers configuration to enable/disable PHP monitoring
• dynatrace_monitored_technologies_varnish covers configuration to enable/disable Varnish monitoring
• dynatrace_monitored_technologies_wsmb covers configuration to enable/disable IBM Integration Bus | IBM App Connect Enterprise monitoring
• dynatrace_process_visibility covers configuration for process instance snapshots
• dynatrace_rum_host_headers covers configuration for identifying host names for real user monitoring
• dynatrace_rum_ip_determination covers configuration for identifying client IP addresses for real user monitoring
• dynatrace_mobile_app_request_errors covers configuration for mobile application request errors
• dynatrace_transaction_start_filters covers customization of CICS and IMS Monitoring
• dynatrace_oneagent_features allows for enabling and disabling OneAgent Features (Sensors, ...)
• dynatrace_rum_overload_prevention covers configuration for real user monitoring overload prevention
• dynatrace_rum_advanced_correlation covers configuration for real user monitoring advanced correlation
• dynatrace_web_app_beacon_origins covers configuration for web application beacon origin allowlist
• dynatrace_web_app_resource_types covers configuration for web application resource types
• dynatrace_generic_types covers configuration for custom topology generic types
• dynatrace_generic_relationships covers configuration for custom topology relationships

Improvements

• Attempting to delete a resource the REST API considers non-deletable doesn't lead to an error anymore
• #168 - Properties shared and sharing_details for resource dynatrace_dashboard are now deprecated (in favor of dynatrace_dashboard_sharing)
• #105 - Changing the metric key of calculated_service_metric now automatically re-creates the resource
• #89 - dynatrace_dashboard_sharing retries to create the resource in case the cluster is not yet fully aware of the existence of the dashboard referred to
• Clarified API Token requirements for resource dynatrace_credentials. Thanks to @paulmorar for contributing
• The data sources dynatrace_management_zone and dynatrace_alerting_profile now offer the attribute legacy_id so they can get referred to from resources with non Settings 2.0 scope
• Introduced the environment variables DYNATRACE_SOURCE_ENV_URL and DYNATRACE_SOURCE_API_TOKEN for the export functionality. The environment variables DYNATRACE_ENV_URL and DYNATRACE_API_TOKEN are still supported, but the new variable names are being preferred. This is meant to prevent unintentionally pushing resources that have just been exported into the same environment again.
• Introduced the option -datasources for the export functionality. When specified, dependencies of resources to dynatrace_management_zone, dynatrace_management_zone_v2,dynatrace_alerting_profile, dynatrace_alerting, dynatrace_request_attribute and dynatrace_web_application will generate data sources instead of exporting these resources.

Bug Fixes

• Fixed #198 - Unable to modify the custom application configuration due to "IconType"
• Fixed #202 - non empty plans for dynatrace_json_dashboard with external JSON source
• Fixed #204 - Incorrect Bearer Token and Credential handling for resources dynatrace_iam_user and dynatrace_iam_group
• Fixed #207 - White Space changes in Entity Selectors of dynatrace_management_zone may lead to non empty plan
• The attributes of Data Sources generated by the export functionality are now getting properly escaped

v1.21.0

New Resources

• dynatrace_rum_provider_breakdown introduces configuration for provider breakdown rules for real user monitoring
• dynatrace_user_experience_score introduces configuration for real user monitoring user experience score
• dynatrace_web_app_resource_cleanup introduces configuration for resource URL cleanup rules for real user monitoring
• dynatrace_update_windows introduces configuration for maintenance windows for OneAgent updates
• dynatrace_process_group_detection_flags introduces configuration to enable or disable built-in process group detection rules
• dynatrace_process_group_monitoring introduces configuration to enable or disable monitoring for certain process groups
• dynatrace_process_group_simple_detection introduces configuration for process group simple detection rules
• dynatrace_log_metrics introduces configuration for log metrics
• dynatrace_browser_monitor_performance introduces configuration for browser monitor performance thresholds
• dynatrace_http_monitor_performance introduces configuration for HTTP monitor performance thresholds
• dynatrace_http_monitor_cookies introduces configuration for HTTP monitor cookies
• dynatrace_session_replay_web_privacy introduces configuration for Session Replay data privacy
• dynatrace_session_replay_resource_capture introduces configuration for Session Replay resource capture
• dynatrace_usability_analytics introduces detection of usability issues within your application
• dynatrace_synthetic_availability introduces synthetic maintenance window configuration

Bug Fixes

• Fixed #197 - dynatrace_synthetic_locations resolved issue with empty locations
• Fixed #199 - Resolved issue with shared cache folder across multiple providers running in parallel
• Fixed #200 - Updated dynatrace_aws_credentials ExternalID field to computed

v1.20.0

New Resources

• dynatrace_connectivity_alerts introduces configuration for process group connectivity alerts
• dynatrace_declarative_grouping introduces configuration for declarative process grouping
• dynatrace_host_monitoring introduces configuration for host monitoring
• dynatrace_rum_ip_locations introduces configuration for IP address mapping rules for real user monitoring
• dynatrace_process_group_rum introduces real user monitoring configuration for process groups
• dynatrace_web_app_enablement introduces configuration for web application enablement and cost control (Certains field(s) of this resource has overlap with another, please refer to the resource docs for additional info)
• dynatrace_mobile_app_enablement introduces configuration for mobile application enablement and cost control (Certains field(s) of this resource has overlap with another, please refer to the resource docs for additional info)
• dynatrace_custom_app_enablement introduces configuration for custom application enablement and cost control (Certains field(s) of this resource has overlap with another, please refer to the resource docs for additional info)

Additional Improvements

• dynatrace_custom_anomalies added Management Zone dependency

Bug Fixes

• Fixed #183 dynatrace_network_zone added the ability to set a custom name
• Fixed #186 dynatrace_environment fix for creating an environment when log monitoring is disabled
• Fixed #191 dynatrace_custom_service fix for error "unable to determine technology"
• Fixed #193 added improvements to resolve rate limiting challenges
• Fixed #194 dynatrace_application_data_privacy, dynatrace_application_error_rules resolved ID misalignment issues
• Fixed #195 dynatrace_api_token resolved issue with blank token
• dynatrace_management_zone_v2 fixed occasional non-empty plans during update

v1.19.0

New Resources

• dynatrace_service_anomalies_v2 introduces configuration for service related performance anomalies
• dynatrace_database_anomalies_v2 introduces configuration for database related performance anomalies
• dynatrace_process_monitoring_rules introduces configuration for custom process monitoring rules
• dynatrace_disk_anomalies_v2 introduces configuration for disk related performance anomalies
• dynatrace_disk_specific_anomalies_v2 introduces configuration for specific disk level performance anomalies
• dynatrace_host_anomalies_v2 introduces configration for host related performance anomalies
• dynatrace_custom_app_anomalies introduces configuration for custom application related performance anomalies
• dynatrace_custom_app_crash_rate introduces configuration for custom application crash rate increase
• dynatrace_process_monitoring introduces configuration for process monitoring rules
• dynatrace_process_availability introduces configuration for monitoring availability of certain processes
• dynatrace_process_group_detection introduces configuration to adapt the detection logic for deep monitored processes
• dynatrace_mobile_app_anomalies introduces configuration for mobile application related performance anomalies
• dynatrace_mobile_app_crash_rate introduces configuration for mobile application crash rate increase
• dynatrace_web_app_anomalies introduces configuration for web application related performance anomalies
• dynatrace_muted_requests introduces configuration for specifying muted requests for a particular service

New Data Sources

• dynatrace_management_zones allows querying for all Management Zones

Additional Improvements

• The export utility has been updated to download all resources in parallel by default
• dynatrace_management_zone has been updated with unordered lists
• dynatrace_azure_credentials disabled the property "supporting_services" since it is now deprecated within the REST API
• dynatrace_dashboard introduced "auto_refresh_disabled" for dashboard tiles
• Thanks to @98christianp the dynatrace_service data source has added functionality for the contains and equals operator

Bug Fixes

• Fixed #184 - Dashboard sharing was reporting a status code error 204 (expected 201)
• Fixed #187 - Dashboard sharing permissions issue has been resolved

v1.18.1

New Resources

• dynatrace_pg_alerting introduces configuration for process group availability monitoring
• dynatrace_custom_tags introduces configuration for custom/manual tags

New Data Sources

• dynatrace_entity allows querying a specific entity by its name and type
• dynatrace_entities allows querying all entities by its type

Additional Improvements

• The full source code of this project is now contained within one repository.

• Certain resources required -parallelism=1 to be specified for terraform apply. This is not necessary anymore.

• The resource dynatrace_alerting, dynatrace_management_zone_v2, dynatrace_maintenance now offer a computed attributed legacy_id. These resources are using the new Settings 2.0 API Endpoint - which unfortunately produces IDs that cannot directly be used within settings based on the Configuration API. When e.g. configuring a resource dynatrace_notification (based on Configuration API) and want to refer to an Alerting Profile configured via dynatrace_alerting (Settings 2.0), you can now refer to the Alerting Profile using dynatrace_alerting.<resourcename>.legacy_id.

• Resources containing multi-line strings are now able to safely use Heredoc syntax without terraform plan acting up.

• terraform-provider-dynatrace -export downloads resources now in parallel

• terraform-provider-dynatrace -export generates direct references to resources instead of using data sources

• #176: dynatrace_aws_credentials now allows for managing Supported Services via WebUI only (Terraform ignores them)

• Improved dynatrace_http_monitor

  • Support for adapting request timeout
  • Client certificates
  • Request and Response Body aswell as Header Values are not getting stored during execution

Bug Fixes

• Fixed dynatrace_autotag, dynatrace_management_zone, dynatrace_mangement_zone_v2 where the order of rules led to non empty plans
• Fixed dynatrace_request_attribute is now able to handle the enabled property

v1.17.0

New Resources

• dynatrace_ddu_pool introduces configuration for DDU pools - define monthly or yearly limits for DDU consumption on a per-environment basis
• dynatrace_pg_anomalies introduces configuration for process group anomaly detection

New Data Sources

• dynatrace_entity allows querying a specific entity by its name and type
• dynatrace_entities allows querying all entities by its type

Additional Improvements

• IAM AccountID may now get specified with or without the urn:dtaccount: prefix

Bug Fixes

• Fixed #173 - dynatrace_network_zone fixed AltZones field type
• Fixed #108 - dynatrace_slo corrected JSON description field
• Fixed dynatrace_json_dashboard unmarshaling to avoid non-empty plans

v1.16.0

New Resources

• dynatrace_network_zone allows for configuring network zones. The resource dynatrace_network_zones introduced in an earlier release just allowed for enabling or disabling them.
• dynatrace_metric_events covers configuration for custom metric events based on the Settings 2.0 REST API.
• dynatrace_json_dashboard introduces an alternative to dynatrace_dashboard. It enables you to manage dashboards as JSON code instead of using the HCL syntax. Dashboards represent the one resource that can get downloaded via WebUI directly - as JSON code. Hence a lot of demand from the community to be able to directly create resources via JSON content.
• dynatrace_management_zone_v2 covers configuration of Management Zones based on the Settings 2.0 REST API. The resource dynatrace_management_zone, which is based on the Configuration REST API is still available as an alternative. Just be aware of the fact, that the ID of this resource only makes sense to get referred to by resources that are also based on the Settings 2.0 API.
• dynatrace_iam_user and dynatrace_iam_group introduces user and group management for SaaS Accounts. In order to use these resources you need to configure an OAuth Client. Further details about that can be found within the documentation of both resources. The current implementation does not yet support configuration of Policies. We will take care of that with the next release.
• dynatrace_api_token allows for creating API Tokens. Please be aware that this resource will introduce sensitive data within your Terraform State as plain text.

New Data Source

• dynatrace_calculated_service_metric allows querying a specific calculated service metric by name

Additional Improvements

• dynatrace_http_monitor and dynatrace_browser_monitor are now offering the ability to configure the number of consecutive runs via global_outage_policy block. Thanks to @tshortess for contributing.

Bug Fixes

• -export didn't properly escape variables for JSON encoded strings

v1.15.0

Exportv2

A new and improved version of the export utility is now available, the detailed documentation is available on the Terraform Registry

• Data source references automatically generated in resources
• Data source blocks created for dependencies in data_source.tf file(s)
• Creation of all resources required based off of dependencies
• Resources organized in modules with preconfigured main.tf based on output
• Pre-populated providers.tf file in the parent folder and all modules
• Option to include ID as a commented line in generated resources
• Option to include/exclude specific resource IDs from export

New Resources

• dynatrace_credentials allows creating credentials in the vault
• dynatrace_synthetic_location allows configuring a private synthetic location

New Data Source

• dynatrace_calculated_service_metric allows querying a specific calculated service metric by name

Additional Improvements

• Introduced retry functionality for dynatrace_calculated_service_metric
• Updated dynatrace_span_attribute resource to ignore create on keys that already exist
• Updated dynatrace_credentials delete to destroy HTTP monitor used for external vaults
• dynatrace_span_attribute that already existed upon create will not get deleted by terraform destroy
• Introduced properties name and index for dimensions in resource dynatrace_custom_anomalies
• Introduced the attribute application_type for resource dynatrace_mobile_application
• Updated schema for dynatrace_span_capture_rule
• Introduced retry functionality with suggested alternative for metric_selector when applying dynatrace_custom_anomalies
• Updated schema for dynatrace_resource_attributes

Bug Fixes

• #152 Crash when adding exported dynatrace_request_attribute to another tenant
• Technology field was missing in dynatrace_custom_service
• Applying dynatrace_custom_service fails when file matchers are empty
• Applying empty permissions for dynatrace_dashboard_sharing and deleting never worked
• dynatrace_synthetic_location never matched against existing values
• #163 dynatrace_maintenance failed to apply with disable_synthetic = false or when omitted
• dynatrace_web_application contained flawed attribute block browserRestrictions (instead of restrictions) upon export
• Comparisons of kind boolean within resource dynatrace_calculated_service_metric are now required attributes
• Updated optional fields within resource dynatrace_mobile_application
• Fixed handling of mobile, touch_enabled and masked in dynatrace_browser_monitor

v1.14.1

Improved Resources

• The rules within dynatrace_autotag and the conditions within these rules are no longer required to be an ordered list. The decision for that change got triggered by #132. Any existing .tf files or states will not be affected and will continue to work as expected. You will however notice a different behavior when using terraform plan.
• The resource dynatrace_dashboard allows for configuring the attribute preset within the dashboard_metadata section. Although that attribute is also configurable via resource dynatrace_dashboard_sharing, the Dynatrace REST API also evaluates that flag when updating dashboards specifcally. In order to prevent contradictions as seen in #150 allowing for configuration in both places was unavoidable on short notice.