Updated documentation prior to release 1.20.0

Author: kishikawa12

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.18.0"
+            version = "1.20.0"
             source = "dynatrace-oss/dynatrace"
         }
     }

docs/resources/api_token.md

@@ -7,9 +7,9 @@ description: |-
 
 # dynatrace_api_token (Resource)
 
-The token value can be retrieved with `dynatrace_api_token.<#name#>.token` after apply.
+-> The usage of `dynatrace_api_token` will introduce sensitive data within your Terraform state. The `token` property is flagged as `sensitive`, but the field will be stored as plain-text. More information can be found [here](https://developer.hashicorp.com/terraform/language/state/sensitive-data).
 
-WARNING: The usage of `dynatrace_api_token` will introduce sensitive data within your Terraform state. The `token` property is flagged as `sensitive`, but the field will be stored as plain-text. More information can be found [here](https://developer.hashicorp.com/terraform/language/state/sensitive-data).
+-> The token value can be retrieved with `dynatrace_api_token.<#name#>.token` after apply.
 
 ## Dynatrace Documentation
 

docs/resources/connectivity_alerts.md

@@ -0,0 +1,42 @@
+---
+layout: ""
+page_title: dynatrace_connectivity_alerts Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_connectivity_alerts` covers configuration for process group connectivity alerts
+---
+
+# dynatrace_connectivity_alerts (Resource)
+
+## Dynatrace Documentation
+
+- Process Groups - https://www.dynatrace.com/support/help/how-to-use-dynatrace/process-groups 
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:alerting.connectivity-alerts`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_connectivity_alerts` downloads all existing process group connectivity alerts
+
+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_connectivity_alerts" "PROCESS_GROUP-1234567890000000" {
+  connectivity_alerts = false
+  process_group_id    = "PROCESS_GROUP-1234567890000000"
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `connectivity_alerts` (Boolean) TCP connectivity problems
+- `process_group_id` (String) The scope of this settings
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+ 

docs/resources/custom_app_enablement.md

@@ -0,0 +1,58 @@
+---
+layout: ""
+page_title: "dynatrace_custom_app_enablement Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_custom_app_enablement` covers configuration for custom application enablement and cost control
+---
+
+# dynatrace_custom_app_enablement (Resource)
+
+-> **Settings 2.0** Certain field(s) of this resource has overlap with `dynatrace_mobile_application`, therefore it is excluded from the default export. To retrieve this resource via export, directly specify it as a command line argument. 
+
+## Dynatrace Documentation
+
+- Configure cost and traffic control for custom applications - https://www.dynatrace.com/support/help/how-to-use-dynatrace/real-user-monitoring/setup-and-configuration/custom-applications/configure-cost-and-traffic-control-custom
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:rum.custom.enablement`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_custom_app_enablement` downloads all existing custom application enablement and cost control 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_custom_app_enablement" "#name#" {
+  scope = "environment"
+  rum {
+    enabled                  = false
+    cost_and_traffic_control = 40
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `rum` (Block List, Min: 1, Max: 1) Capture and analyze all user actions within your application. Enable [Real User Monitoring (RUM)](https://dt-url.net/1n2b0prq) to monitor and improve your application's performance, identify errors, and gain insight into your user's behavior and experience. (see [below for nested schema](#nestedblock--rum))
+
+### Optional
+
+- `scope` (String) The scope of this setting (CUSTOM_APPLICATION). Omit this property if you want to cover the whole environment.
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+
+<a id="nestedblock--rum"></a>
+### Nested Schema for `rum`
+
+Required:
+
+- `cost_and_traffic_control` (Number) (Field has overlap with `dynatrace_mobile_application`) Percentage of user sessions captured and analyzed. By default, Dynatrace captures all user actions and user sessions for analysis. This approach ensures complete insight into your application’s performance and customer experience. You can optionally reduce the granularity of user-action and user-session analysis by capturing a lower percentage of user sessions. While this approach can reduce monitoring costs, it also results in lower visibility into how your customers are using your applications. For example, a setting of 10% results in Dynatrace analyzing only every tenth user session.
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+ 

docs/resources/declarative_grouping.md

@@ -0,0 +1,104 @@
+---
+layout: ""
+page_title: dynatrace_declarative_grouping Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_declarative_grouping` covers configuration for declarative process grouping
+---
+
+# dynatrace_declarative_grouping (Resource)
+
+## Dynatrace Documentation
+
+- Declarative process grouping - https://www.dynatrace.com/support/help/shortlink/process-groups#declare
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:declarativegrouping`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_declarative_grouping` downloads all existing declarative process grouping 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_declarative_grouping" "#name#" {
+  name    = "#name#"
+  enabled = true
+  scope   = "environment"
+  detection {
+    process_definition {
+      id                 = "PGIdentifierSample"
+      process_group_name = "PGDisplayNameSample"
+      report             = "always"
+      rules {
+        rule {
+          condition = "$contains(TFExecutableSample)"
+          property  = "executable"
+        }
+        rule {
+          condition = "$contains(TFCommandSample)"
+          property  = "commandLine"
+        }
+      }
+    }
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `detection` (Block List, Min: 1, Max: 1) Enter a descriptive process group display name and a unique identifier that Dynatrace can use to recognize this process group. (see [below for nested schema](#nestedblock--detection))
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+- `name` (String) Monitored technology name
+
+### Optional
+
+- `scope` (String) The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+
+<a id="nestedblock--detection"></a>
+### Nested Schema for `detection`
+
+Required:
+
+- `process_definition` (Block List, Min: 1) (see [below for nested schema](#nestedblock--detection--process_definition))
+
+<a id="nestedblock--detection--process_definition"></a>
+### Nested Schema for `detection.process_definition`
+
+Required:
+
+- `id` (String) Process group identifier
+- `process_group_name` (String) This identifier is used by Dynatrace to recognize this process group.
+- `report` (String) Possible Values: `Never`, `Always`, `HighResourceUsage`
+- `rules` (Block List, Min: 1, Max: 1) Define process detection rules by selecting a process property and a condition. Each process group can have multiple detection rules associated with it. (see [below for nested schema](#nestedblock--detection--process_definition--rules))
+
+<a id="nestedblock--detection--process_definition--rules"></a>
+### Nested Schema for `detection.process_definition.rules`
+
+Required:
+
+- `rule` (Block List, Min: 1) (see [below for nested schema](#nestedblock--detection--process_definition--rules--rule))
+
+<a id="nestedblock--detection--process_definition--rules--rule"></a>
+### Nested Schema for `detection.process_definition.rules.rule`
+
+Required:
+
+- `condition` (String) - $contains(svc) – Matches if svc appears anywhere in the process property value.
+- $eq(svc.exe) – Matches if svc.exe matches the process property value exactly.
+- $prefix(svc) – Matches if app matches the prefix of the process property value.
+- $suffix(svc.py) – Matches if svc.py matches the suffix of the process property value.
+
+For example, $suffix(svc.py) would detect processes named loyaltysvc.py and paymentssvc.py.
+
+For more details, see [Declarative process grouping](https://dt-url.net/j142w57).
+- `property` (String) Possible Values: `Executable`, `ExecutablePath`, `CommandLine`
+ 

docs/resources/environment.md

@@ -61,13 +61,16 @@ Optional:
 
 Required:
 
-- `logs` (Number) Log monitoring retention settings on environment level in days. Not editable when Log monitoring is not allowed by license or not configured on cluster level. Can be set to any value from 5 to 90 days
 - `rum` (Number) Real user monitoring retention settings on environment level in days. Can be set to any value from 1 to 35 days
 - `service_code_level` (Number) Service code level retention settings on environment level in days. Service code level retention time can't be greater than service request level retention time and both can't exceed one year
 - `service_request_level` (Number) Service request level retention settings on environment level in days. Service code level retention time can't be greater than service request level retention time and both can't exceed one year
 - `session_replay` (Number) Session replay retention settings on environment level in days. Can be set to any value from 1 to 35 days
 - `synthetic` (Number) Synthetic monitoring retention settings on environment level in days. Can be set to any value from 1 to 35 days
 
+Optional:
+
+- `logs` (Number) Log monitoring retention settings on environment level in days. Not editable when Log monitoring is not allowed by license or not configured on cluster level. Can be set to any value from 5 to 90 days
+
 
 
 <a id="nestedblock--quotas"></a>

docs/resources/host_monitoring.md

@@ -0,0 +1,52 @@
+---
+layout: ""
+page_title: dynatrace_host_monitoring Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_host_monitoring` covers configuration for host monitoring
+---
+
+# dynatrace_host_monitoring (Resource)
+
+## Dynatrace Documentation
+
+- Hosts - https://www.dynatrace.com/support/help/how-to-use-dynatrace/infrastructure-monitoring/hosts
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:host.monitoring`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_host_monitoring` downloads all existing host monitoring 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_host_monitoring" "#name#" {
+  enabled        = true
+  auto_injection = false
+  full_stack     = false
+  host_id        = "HOST-1234567890000000"
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `auto_injection` (Boolean) An auto-injection disabled with [oneagentctl](https://dt-url.net/oneagentctl) takes precedence over this setting and cannot be changed from the Dynatrace web UI.
+- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
+- `full_stack` (Boolean) Dynatrace uses full-stack monitoring by default, to monitor every aspect of your environment, including all processes, services, and applications detected on your hosts. 
+
+If you turn off full-stack monitoring, Dynatrace will only monitor your infrastructure. You will lose access to application performance, user experience data, code-level visibility and PurePath insights. 
+
+To learn more, visit [Infrastructure Monitoring mode](https://www.dynatrace.com/support/help/shortlink/infrastructure).
+
+Please note that changing the monitoring mode will impact the license consumption of this OneAgent. To learn more, visit [Host units](https://dt-url.net/hi03uns).
+- `host_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.
+ 

docs/resources/host_process_group_monitoring.md

@@ -0,0 +1,44 @@
+---
+layout: ""
+page_title: dynatrace_host_process_group_monitoring Resource - terraform-provider-dynatrace"
+description: |-
+  The resource `dynatrace_host_process_group_monitoring` covers configuration of host level process group monitoring rules
+---
+
+# dynatrace_host_process_group_monitoring (Resource)
+
+## Dynatrace Documentation
+
+- Set monitoring rules at host level - https://www.dynatrace.com/support/help/how-to-use-dynatrace/process-groups/configuration/pg-monitoring#set-monitoring-rules-at-host-level
+
+- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:host.process-groups.monitoring-state`)
+
+## Export Example Usage
+
+- `terraform-provider-dynatrace -export dynatrace_host_process_group_monitoring` downloads all existing host level process group monitoring 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_host_process_group_monitoring" "#name#" {
+  host_id          = "HOST-1234567890000000"
+  monitoring_state = "MONITORING_ON"
+  process_group    = "PROCESS_GROUP-1234567890000000"
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `host_id` (String) The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
+- `monitoring_state` (String) Possible Values: `DEFAULT`, `MONITORING_OFF`, `MONITORING_ON`
+- `process_group` (String) Process group
+
+### Read-Only
+
+- `id` (String) The ID of this resource.
+