DocUpdate for v1.22.1

Author: Reinhard-Pilz-Dynatrace

docs/index.md

@@ -18,7 +18,7 @@ Use the links to the left to learn about the available resources and data source
 terraform {
     required_providers {
         dynatrace = {
-            version = "1.22.0"
+            version = "1.22.1"
             source = "dynatrace-oss/dynatrace"
         }
     }

docs/resources/application_data_privacy.md

@@ -7,7 +7,7 @@ description: |-
 
 # dynatrace_application_data_privacy (Resource)
 
--> Certain field(s) of this resource has overlap with `dynatrace_session_replay_web_privacy`, please review the schema for additional information.
+-> Certain field(s) of this resource has overlap with `dynatrace_data_privacy`, please review the schema for additional information.
 
 ## Dynatrace Documentation
 
@@ -26,18 +26,18 @@ The full documentation of the export feature is available [here](https://registr
 
 ### Required
 
-- `do_not_track_behaviour` (String) How to handle the "Do Not Track" header: 
+- `do_not_track_behaviour` (String) (Field has overlap with `dynatrace_data_privacy`) How to handle the "Do Not Track" header: 
 
 * `IGNORE_DO_NOT_TRACK`: ignore the header and capture the data. 
 * `CAPTURE_ANONYMIZED`: capture the data but do not tie it to the user. 
 * `DO_NOT_CAPTURE`: respect the header and do not capture.
-- `session_replay_data_privacy` (Block List, Min: 1, Max: 1) Data privacy settings for Session Replay (see [below for nested schema](#nestedblock--session_replay_data_privacy))
+- `session_replay_data_privacy` (Block List, Min: 1, Max: 1) (Field has overlap with `dynatrace_session_replay_web_privacy`) Data privacy settings for Session Replay (see [below for nested schema](#nestedblock--session_replay_data_privacy))
 - `web_application_id` (String) Dynatrace entity ID of the web application
 
 ### Optional
 
-- `data_capture_opt_in` (Boolean) Set to `true` to disable data capture and cookies until JavaScriptAPI `dtrum.enable()` is called
-- `persistent_cookie_for_user_tracking` (Boolean) Set to `true` to set persistent cookie in order to recognize returning devices
+- `data_capture_opt_in` (Boolean) (Field has overlap with `dynatrace_data_privacy`) Set to `true` to disable data capture and cookies until JavaScriptAPI `dtrum.enable()` is called
+- `persistent_cookie_for_user_tracking` (Boolean) (Field has overlap with `dynatrace_data_privacy`) Set to `true` to set persistent cookie in order to recognize returning devices
 
 ### Read-Only
 

docs/resources/data_privacy.md

@@ -0,0 +1,122 @@
+---
+layout: ""
+page_title: "dynatrace_data_privacy Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_data_privacy` covers configuration for end users' data privacy
+---
+
+# dynatrace_data_privacy (Resource)
+
+-> **Settings 2.0** Certain field(s) of this resource has overlap with `dynatrace_application_data_privacy`, therefore it is excluded from the default export. To retrieve this resource via export, directly specify it as a command line argument. 
+
+## Dynatrace Documentation
+
+- Data privacy and security - https://www.dynatrace.com/support/help/manage/data-privacy-and-security
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:preferences.privacy`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_data_privacy` downloads all existing end users' data privacy configuration
+
+The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2).
+
+## Resource Example Usage
+
+```terraform
+resource "dynatrace_data_privacy" "#name#" {
+  application_id = "environment"
+  data_collection {
+    opt_in_mode_enabled = true
+  }
+  do_not_track {
+    comply_with_do_not_track = false
+  }
+  masking {
+    ip_address_masking                = "public"
+    ip_address_masking_enabled        = true
+    personal_data_uri_masking_enabled = true
+    user_action_masking_enabled       = true
+  }
+  user_tracking {
+    persistent_cookie_enabled = true
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `data_collection` (Block List, Min: 1, Max: 1) (Field has overlap with `dynatrace_application_data_privacy`) To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode. (see [below for nested schema](#nestedblock--data_collection))
+- `do_not_track` (Block List, Min: 1, Max: 1) (Field has overlap with `dynatrace_application_data_privacy`) Most modern web browsers have a privacy feature called ["Do Not Track"](https://dt-url.net/sb3n0pnl) that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting. (see [below for nested schema](#nestedblock--do_not_track))
+- `masking` (Block List, Min: 1, Max: 1) (Field has overlap with `dynatrace_application_data_privacy`) (see [below for nested schema](#nestedblock--masking))
+- `user_tracking` (Block List, Min: 1, Max: 1) (Field has overlap with `dynatrace_application_data_privacy`) User tracking (see [below for nested schema](#nestedblock--user_tracking))
+
+### Optional
+
+- `application_id` (String) The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+
+<a id="nestedblock--data_collection"></a>
+### Nested Schema for `data_collection`
+
+Required:
+
+- `opt_in_mode_enabled` (Boolean) With [Data-collection and opt-in mode](https://dt-url.net/7l3p0p3h) enabled, Real User Monitoring data isn't captured until dtrum.enable() is called for specific user sessions.
+
+
+<a id="nestedblock--do_not_track"></a>
+### Nested Schema for `do_not_track`
+
+Required:
+
+- `comply_with_do_not_track` (Boolean) Comply with "Do Not Track" browser settings
+
+Optional:
+
+- `do_not_track` (String) Possible Values: `Anonymous`, `Disable_rum`
+
+
+<a id="nestedblock--masking"></a>
+### Nested Schema for `masking`
+
+Required:
+
+- `ip_address_masking_enabled` (Boolean) Dynatrace captures the IP addresses of your end-users to determine the regions from which they access your application. To learn more, visit [Mask IPs and GPS coordinates](https://dt-url.net/mask-end-users-ip-addresses).. Dynatrace also captures GPS data from mobile apps that provide their users with the option of sharing geolocation data. On the server side, Dynatrace captures IP addresses to enable detailed troubleshooting for Dynatrace service calls.
+
+Once enabled, IP address masking sets the last octet of monitored IPv4 addresses and the last 80 bits of IPv6 addresses to zeroes. GPS coordinates are rounded up to 1 decimal place (~10 km). This masking occurs in memory. Full IP addresses are never written to disk. Location lookups are made using anonymized IP addresses and GPS coordinates.
+- `personal_data_uri_masking_enabled` (Boolean) Dynatrace captures the URIs and request headers sent from desktop and mobile browsers. Dynatrace also captures full URIs on the server-side to enable detailed performance analysis of your applications. For complete details, visit [Mask personal data in URIs](https://dt-url.net/mask-personal-data-in-URIs).. URIs and request headers contain personal data. When this setting is enabled, Dynatrace automatically detects UUIDs, credit card numbers, email addresses, IP addresses, and other IDs and replaces those values with placeholders. The personal data is then masked in PurePath analysis, error analysis, user action naming for RUM, and elsewhere in Dynatrace.
+- `user_action_masking_enabled` (Boolean) When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action. To learn more about masking user actions, visit [Mask user actions](https://dt-url.net/mask-user-action).. When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action, it constructs a name for the user action based on:
+
+- User event type (click on..., loading of page..., or keypress on...)
+- Title, caption, label, value, ID, className, or other available property of the related HTML element (for example, an image, button, checkbox, or text input field).
+
+In most instances, the default approach to user-action naming works well, resulting in user-action names such as:
+
+- click on "Search" on page /search.html
+- keypress on "Feedback" on page /contact.html
+- touch on "Homescreen" of page /list.jsf
+
+In rare circumstances, confidential data (for example, email addresses, usernames, or account numbers) can be unintentionally included in user action names because the confidential data itself is included in an HTML element label, attribute, or other value (for example, click on "my Account Number: 1231231"...). If such confidential data appears in your application's user action names, enable the Mask user action names setting. This setting replaces specific HTML element names and values with generic HTML element names. With user-action name masking enabled, the user action names listed above appear as:
+
+- click on INPUT on page /search.html
+- keypress on TEXTAREA on page /contact.html
+- touch on DIV of page /list.jsf
+
+Optional:
+
+- `ip_address_masking` (String) Possible Values: `All`, `Public`
+
+
+<a id="nestedblock--user_tracking"></a>
+### Nested Schema for `user_tracking`
+
+Required:
+
+- `persistent_cookie_enabled` (Boolean) When enabled, Dynatrace places a [persistent cookie](https://dt-url.net/313o0p4n) on all end-user devices to identify returning users.
+ 

docs/resources/service_failure.md

@@ -0,0 +1,172 @@
+---
+layout: ""
+page_title: dynatrace_service_failure Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_service_failure` covers configuration for service-level general failure detection parameters
+---
+
+# dynatrace_service_failure (Resource)
+
+## Dynatrace Documentation
+
+- Configure service failure detection - https://www.dynatrace.com/support/help/platform-modules/applications-and-microservices/services/service-monitoring-settings/configure-service-failure-detection
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:failure-detection.service.general-parameters`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_service_failure` downloads all existing service-level general failure detection parameters
+
+The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2).
+
+## Resource Example Usage
+
+```terraform
+resource "dynatrace_service_failure" "#name#" {
+  enabled    = true
+  service_id = "SERVICE-1234567890000000"
+  exception_rules {
+    ignore_all_exceptions         = false
+    ignore_span_failure_detection = true
+    custom_error_rules {
+      custom_error_rule {
+        request_attribute = "00000000-0000-0000-0000-000000000000"
+        condition {
+          compare_operation_type = "STRING_EXISTS"
+        }
+      }
+    }
+    custom_handled_exceptions {
+      custom_handled_exception {
+        class_pattern   = "ClassPatternExample"
+        message_pattern = "ExceptionMessagePatternExample"
+      }
+    }
+    ignored_exceptions {
+      custom_handled_exception {
+        class_pattern   = "ClassPatternExample"
+        message_pattern = "ExceptionMessagePatternExample"
+      }
+    }
+    success_forcing_exceptions {
+      custom_handled_exception {
+        class_pattern   = "ClassPatternExample"
+        message_pattern = "ExceptionMessagePatternExample"
+      }
+    }
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+- `service_id` (String) The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
+
+### Optional
+
+- `exception_rules` (Block List, Max: 1) Customize failure detection for specific exceptions and errors (see [below for nested schema](#nestedblock--exception_rules))
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+
+<a id="nestedblock--exception_rules"></a>
+### Nested Schema for `exception_rules`
+
+Required:
+
+- `ignore_all_exceptions` (Boolean) Ignore all exceptions
+- `ignore_span_failure_detection` (Boolean) Ignore span failure detection
+
+Optional:
+
+- `custom_error_rules` (Block List, Max: 1) Some custom error situations are only detectable via a return value or other means. To support such cases, [define a request attribute](https://dt-url.net/ys5k0p4y) that captures the required data. Then define a custom error rule that determines if the request has failed based on the value of the request attribute. (see [below for nested schema](#nestedblock--exception_rules--custom_error_rules))
+- `custom_handled_exceptions` (Block List, Max: 1) There may be situations where your application code handles exceptions gracefully in a manner that these failures aren't detected by Dynatrace. Use this setting to define specific gracefully-handled exceptions that should be treated as service failures. (see [below for nested schema](#nestedblock--exception_rules--custom_handled_exceptions))
+- `ignored_exceptions` (Block List, Max: 1) Some exceptions that are thrown by legacy or 3rd-party code indicate a specific response, not an error. Use this setting to instruct Dynatrace to treat such exceptions as non-failed requests.. If an exception matching any of the defined patterns occurs in a request, it will not be considered as a failure. Other exceptions occurring at the same request might still mark the request as failed. (see [below for nested schema](#nestedblock--exception_rules--ignored_exceptions))
+- `success_forcing_exceptions` (Block List, Max: 1) Define exceptions which indicate that a service call should not be considered as failed. E.g. an exception indicating that the client aborted the operation.. If an exception matching any of the defined patterns occurs on the entry node of the service, it will be considered successful. Compared to ignored exceptions, the request will be considered successful even if other exceptions occur in the same request. (see [below for nested schema](#nestedblock--exception_rules--success_forcing_exceptions))
+
+<a id="nestedblock--exception_rules--custom_error_rules"></a>
+### Nested Schema for `exception_rules.custom_error_rules`
+
+Required:
+
+- `custom_error_rule` (Block Set, Min: 1) (see [below for nested schema](#nestedblock--exception_rules--custom_error_rules--custom_error_rule))
+
+<a id="nestedblock--exception_rules--custom_error_rules--custom_error_rule"></a>
+### Nested Schema for `exception_rules.custom_error_rules.custom_error_rule`
+
+Required:
+
+- `condition` (Block List, Min: 1, Max: 1) Request attribute condition (see [below for nested schema](#nestedblock--exception_rules--custom_error_rules--custom_error_rule--condition))
+- `request_attribute` (String) Request attribute
+
+<a id="nestedblock--exception_rules--custom_error_rules--custom_error_rule--condition"></a>
+### Nested Schema for `exception_rules.custom_error_rules.custom_error_rule.condition`
+
+Required:
+
+- `compare_operation_type` (String) Apply this comparison
+
+Optional:
+
+- `case_sensitive` (Boolean) Case sensitive
+- `double_value` (Number) Value
+- `int_value` (Number) Value
+- `text_value` (String) Value
+
+
+
+
+<a id="nestedblock--exception_rules--custom_handled_exceptions"></a>
+### Nested Schema for `exception_rules.custom_handled_exceptions`
+
+Required:
+
+- `custom_handled_exception` (Block Set, Min: 1) (see [below for nested schema](#nestedblock--exception_rules--custom_handled_exceptions--custom_handled_exception))
+
+<a id="nestedblock--exception_rules--custom_handled_exceptions--custom_handled_exception"></a>
+### Nested Schema for `exception_rules.custom_handled_exceptions.custom_handled_exception`
+
+Optional:
+
+- `class_pattern` (String) The pattern will match if it is contained within the actual class name.
+- `message_pattern` (String) Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
+
+
+
+<a id="nestedblock--exception_rules--ignored_exceptions"></a>
+### Nested Schema for `exception_rules.ignored_exceptions`
+
+Required:
+
+- `custom_handled_exception` (Block Set, Min: 1) (see [below for nested schema](#nestedblock--exception_rules--ignored_exceptions--custom_handled_exception))
+
+<a id="nestedblock--exception_rules--ignored_exceptions--custom_handled_exception"></a>
+### Nested Schema for `exception_rules.ignored_exceptions.custom_handled_exception`
+
+Optional:
+
+- `class_pattern` (String) The pattern will match if it is contained within the actual class name.
+- `message_pattern` (String) Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
+
+
+
+<a id="nestedblock--exception_rules--success_forcing_exceptions"></a>
+### Nested Schema for `exception_rules.success_forcing_exceptions`
+
+Required:
+
+- `custom_handled_exception` (Block Set, Min: 1) (see [below for nested schema](#nestedblock--exception_rules--success_forcing_exceptions--custom_handled_exception))
+
+<a id="nestedblock--exception_rules--success_forcing_exceptions--custom_handled_exception"></a>
+### Nested Schema for `exception_rules.success_forcing_exceptions.custom_handled_exception`
+
+Optional:
+
+- `class_pattern` (String) The pattern will match if it is contained within the actual class name.
+- `message_pattern` (String) Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
+ 

docs/resources/slo_normalization.md

@@ -0,0 +1,40 @@
+---
+layout: ""
+page_title: "dynatrace_slo_normalization Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_slo_normalization` covers configuration for service-level objective setup
+---
+
+# dynatrace_slo_normalization (Resource)
+
+## Dynatrace Documentation
+
+- Normalize error budget - https://www.dynatrace.com/support/help/platform-modules/cloud-automation/service-level-objectives/configure-and-monitor-slo#normalize-error-budget
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:monitoring.slo.normalization`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_slo_normalization` downloads all existing service-level objective setup configuration
+
+The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2).
+
+## Resource Example Usage
+
+```terraform
+resource "dynatrace_slo_normalization" "#name#" {
+  normalize = true
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `normalize` (Boolean) When set to true, the error budget left will be shown in percent of the total error budget. For more details see [SLO normalization help](https://dt-url.net/slo-normalize-error-budget).
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+ 

provider/version/version.go

@@ -17,4 +17,4 @@
 
 package version
 
-const Current = "1.22.0"
+const Current = "1.22.1"

templates/index.md.tmpl

@@ -18,7 +18,7 @@ Use the links to the left to learn about the available resources and data source
 terraform {
     required_providers {
         dynatrace = {
-            version = "1.22.0"
+            version = "1.22.1"
             source = "dynatrace-oss/dynatrace"
         }
     }