Skip to content

Commit 4bbb87e

Browse files
Reinhard-Pilz-DynatraceReinhard-Pilz-Dynatrace
committed
Release v1.30.0
1 parent 524d059 commit 4bbb87e

File tree

5 files changed

+271
-1
lines changed

5 files changed

+271
-1
lines changed

‎docs/resources/ownership_config.md‎

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
layout: ""
3+
page_title: dynatrace_ownership_config Resource - terraform-provider-dynatrace"
4+
description: |-
5+
The resource `dynatrace_ownership_config` covers configuration for ownership
6+
---
7+
8+
# dynatrace_ownership_config (Resource)
9+
10+
## Dynatrace Documentation
11+
12+
- Ownership - https://www.dynatrace.com/support/help/manage/ownership
13+
14+
- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:ownership.config`)
15+
16+
## Export Example Usage
17+
18+
- `terraform-provider-dynatrace -export dynatrace_ownership_config` downloads all existing ownership configuration
19+
20+
The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2).
21+
22+
## Resource Example Usage
23+
24+
```terraform
25+
resource "dynatrace_ownership_config" "#name#" {
26+
ownership_identifiers {
27+
ownership_identifier {
28+
enabled = true
29+
key = "dt.owner"
30+
}
31+
ownership_identifier {
32+
enabled = true
33+
key = "owner"
34+
}
35+
}
36+
}
37+
```
38+
39+
<!-- schema generated by tfplugindocs -->
40+
## Schema
41+
42+
### Required
43+
44+
- `ownership_identifiers` (Block List, Min: 1, Max: 1) Tags and metadata are key-value pairs. Define keys for tags and metadata that are considered for ownership. If a tag or any metadata starts with a key defined below, the value of the tag or metadata is considered a team identifier. (see [below for nested schema](#nestedblock--ownership_identifiers))
45+
46+
### Read-Only
47+
48+
- `id` (String) The ID of this resource.
49+
50+
<a id="nestedblock--ownership_identifiers"></a>
51+
### Nested Schema for `ownership_identifiers`
52+
53+
Required:
54+
55+
- `ownership_identifier` (Block List, Min: 1) (see [below for nested schema](#nestedblock--ownership_identifiers--ownership_identifier))
56+
57+
<a id="nestedblock--ownership_identifiers--ownership_identifier"></a>
58+
### Nested Schema for `ownership_identifiers.ownership_identifier`
59+
60+
Required:
61+
62+
- `enabled` (Boolean) This setting is enabled (`true`) or disabled (`false`)
63+
- `key` (String) Key for ownership metadata and tags
64+

‎docs/resources/web_app_key_performance_custom.md‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
layout: ""
3+
page_title: dynatrace_web_app_key_performance_custom Resource - terraform-provider-dynatrace"
4+
description: |-
5+
The resource `dynatrace_web_app_key_performance_custom` covers apdex threshold configuration for custom actions
6+
7+
---
8+
9+
# dynatrace_web_app_key_performance_custom (Resource)
10+
11+
-> **Settings 2.0** Certain field(s) of this resource has overlap with `dynatrace_web_application`, therefore it is excluded from the default export. To retrieve this resource via export, directly specify it as a command line argument.
12+
13+
## Dynatrace Documentation
14+
15+
- Adjust Apdex settings for web applications - https://www.dynatrace.com/support/help/platform-modules/digital-experience/web-applications/additional-configuration/configure-apdex-web
16+
17+
- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:rum.web.key-performance-metric-custom-actions`)
18+
19+
## Export Example Usage
20+
21+
- `terraform-provider-dynatrace -export dynatrace_web_app_key_performance_custom` downloads all existing apdex threshold configuration for custom actions
22+
23+
The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2).
24+
25+
## Resource Example Usage
26+
27+
```terraform
28+
resource "dynatrace_web_app_key_performance_custom" "#name#" {
29+
scope = "APPLICATION_METHOD-1234567890000000"
30+
thresholds {
31+
frustrating_threshold_seconds = 12
32+
tolerated_threshold_seconds = 3
33+
}
34+
}
35+
```
36+
37+
<!-- schema generated by tfplugindocs -->
38+
## Schema
39+
40+
### Required
41+
42+
- `scope` (String) The scope of this setting (APPLICATION_METHOD, APPLICATION)
43+
- `thresholds` (Block List, Min: 1, Max: 1) User action duration thresholds (see [below for nested schema](#nestedblock--thresholds))
44+
45+
### Read-Only
46+
47+
- `id` (String) The ID of this resource.
48+
49+
<a id="nestedblock--thresholds"></a>
50+
### Nested Schema for `thresholds`
51+
52+
Required:
53+
54+
- `frustrating_threshold_seconds` (Number) If **User action duration** is above this value, the action is assigned to the Frustrated performance zone.
55+
- `tolerated_threshold_seconds` (Number) If **User action duration** is below this value, the action is assigned to the Satisfied performance zone.
56+

‎docs/resources/web_app_key_performance_load.md‎

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
layout: ""
3+
page_title: dynatrace_web_app_key_performance_load Resource - terraform-provider-dynatrace"
4+
description: |-
5+
The resource `dynatrace_web_app_key_performance_load` covers apdex threshold configuration for load actions
6+
7+
---
8+
9+
# dynatrace_web_app_key_performance_load (Resource)
10+
11+
-> **Settings 2.0** Certain field(s) of this resource has overlap with `dynatrace_web_application`, therefore it is excluded from the default export. To retrieve this resource via export, directly specify it as a command line argument.
12+
13+
## Dynatrace Documentation
14+
15+
- Adjust Apdex settings for web applications - https://www.dynatrace.com/support/help/platform-modules/digital-experience/web-applications/additional-configuration/configure-apdex-web
16+
17+
- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:rum.web.key-performance-metric-load-actions`)
18+
19+
## Export Example Usage
20+
21+
- `terraform-provider-dynatrace -export dynatrace_web_app_key_performance_load` downloads all existing apdex threshold configuration for load actions
22+
23+
The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2).
24+
25+
## Resource Example Usage
26+
27+
```terraform
28+
resource "dynatrace_web_app_key_performance_load" "#name#" {
29+
kpm = "VISUALLY_COMPLETE"
30+
scope = "APPLICATION_METHOD-1234567890000000"
31+
fallback_thresholds {
32+
frustrating_fallback_threshold_seconds = 12
33+
tolerated_fallback_threshold_seconds = 3
34+
}
35+
thresholds {
36+
frustrating_threshold_seconds = 12
37+
tolerated_threshold_seconds = 3
38+
}
39+
}
40+
```
41+
42+
<!-- schema generated by tfplugindocs -->
43+
## Schema
44+
45+
### Required
46+
47+
- `kpm` (String) Possible Values: `CUMULATIVE_LAYOUT_SHIFT`, `DOM_INTERACTIVE`, `FIRST_INPUT_DELAY`, `LARGEST_CONTENTFUL_PAINT`, `LOAD_EVENT_END`, `LOAD_EVENT_START`, `RESPONSE_END`, `RESPONSE_START`, `SPEED_INDEX`, `USER_ACTION_DURATION`, `VISUALLY_COMPLETE`
48+
- `scope` (String) The scope of this setting (APPLICATION_METHOD, APPLICATION)
49+
- `thresholds` (Block List, Min: 1, Max: 1) Set the Tolerating and Frustrated performance thresholds for this action type. (see [below for nested schema](#nestedblock--thresholds))
50+
51+
### Optional
52+
53+
- `fallback_thresholds` (Block List, Max: 1) If the selected key performance metric is not detected, the **User action duration** metric is used instead. (see [below for nested schema](#nestedblock--fallback_thresholds))
54+
55+
### Read-Only
56+
57+
- `id` (String) The ID of this resource.
58+
59+
<a id="nestedblock--thresholds"></a>
60+
### Nested Schema for `thresholds`
61+
62+
Required:
63+
64+
- `frustrating_threshold_seconds` (Number) If the key performance metric is above this value, the action is assigned to the Frustrated performance zone.
65+
- `tolerated_threshold_seconds` (Number) If the key performance metric is below this value, the action is assigned to the Satisfied performance zone.
66+
67+
68+
<a id="nestedblock--fallback_thresholds"></a>
69+
### Nested Schema for `fallback_thresholds`
70+
71+
Required:
72+
73+
- `frustrating_fallback_threshold_seconds` (Number) If **User action duration** is above this value, the action is assigned to the Frustrated performance zone.
74+
- `tolerated_fallback_threshold_seconds` (Number) If **User action duration** is below this value, the action is assigned to the Satisfied performance zone.
75+

‎docs/resources/web_app_key_performance_xhr.md‎

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
---
2+
layout: ""
3+
page_title: dynatrace_web_app_key_performance_xhr Resource - terraform-provider-dynatrace"
4+
description: |-
5+
The resource `dynatrace_web_app_key_performance_xhr` covers apdex threshold configuration for XHR actions
6+
7+
---
8+
9+
# dynatrace_web_app_key_performance_xhr (Resource)
10+
11+
-> **Settings 2.0** Certain field(s) of this resource has overlap with `dynatrace_web_application`, therefore it is excluded from the default export. To retrieve this resource via export, directly specify it as a command line argument.
12+
13+
## Dynatrace Documentation
14+
15+
- Adjust Apdex settings for web applications - https://www.dynatrace.com/support/help/platform-modules/digital-experience/web-applications/additional-configuration/configure-apdex-web
16+
17+
- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:rum.web.key-performance-metric-xhr-actions`)
18+
19+
## Export Example Usage
20+
21+
- `terraform-provider-dynatrace -export dynatrace_web_app_key_performance_xhr` downloads all existing apdex threshold configuration for XHR actions
22+
23+
The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2).
24+
25+
## Resource Example Usage
26+
27+
```terraform
28+
resource "dynatrace_web_app_key_performance_xhr" "#name#" {
29+
kpm = "VISUALLY_COMPLETE"
30+
scope = "APPLICATION_METHOD-1234567890000000"
31+
fallback_thresholds {
32+
frustrating_fallback_threshold_seconds = 12
33+
tolerated_fallback_threshold_seconds = 3
34+
}
35+
thresholds {
36+
frustrating_threshold_seconds = 12
37+
tolerated_threshold_seconds = 3
38+
}
39+
}
40+
```
41+
42+
<!-- schema generated by tfplugindocs -->
43+
## Schema
44+
45+
### Required
46+
47+
- `kpm` (String) Possible Values: `RESPONSE_END`, `RESPONSE_START`, `USER_ACTION_DURATION`, `VISUALLY_COMPLETE`
48+
- `scope` (String) The scope of this setting (APPLICATION_METHOD, APPLICATION)
49+
- `thresholds` (Block List, Min: 1, Max: 1) Set the Tolerating and Frustrated performance thresholds for this action type. (see [below for nested schema](#nestedblock--thresholds))
50+
51+
### Optional
52+
53+
- `fallback_thresholds` (Block List, Max: 1) If the selected key performance metric is not detected, the **User action duration** metric is used instead. (see [below for nested schema](#nestedblock--fallback_thresholds))
54+
55+
### Read-Only
56+
57+
- `id` (String) The ID of this resource.
58+
59+
<a id="nestedblock--thresholds"></a>
60+
### Nested Schema for `thresholds`
61+
62+
Required:
63+
64+
- `frustrating_threshold_seconds` (Number) If the key performance metric is above this value, the action is assigned to the Frustrated performance zone.
65+
- `tolerated_threshold_seconds` (Number) If the key performance metric is below this value, the action is assigned to the Satisfied performance zone.
66+
67+
68+
<a id="nestedblock--fallback_thresholds"></a>
69+
### Nested Schema for `fallback_thresholds`
70+
71+
Required:
72+
73+
- `frustrating_fallback_threshold_seconds` (Number) If **User action duration** is above this value, the action is assigned to the Frustrated performance zone.
74+
- `tolerated_fallback_threshold_seconds` (Number) If **User action duration** is below this value, the action is assigned to the Satisfied performance zone.
75+

‎docs/resources/web_application.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ description: |-
77

88
# dynatrace_web_application (Resource)
99

10-
-> Certain field(s) of this resource has overlap with `dynatrace_web_app_enablement` and `dynatrace_session_replay_resource_capture`, please review the schema for additional information.
10+
-> Certain field(s) of this resource has overlap with `dynatrace_web_app_enablement`, `dynatrace_session_replay_resource_capture`, `dynatrace_web_app_key_performance_load`, `dynatrace_web_app_key_performance_xhr`, and `dynatrace_web_app_key_performance_custom`; please review the schema for additional information.
1111

1212
## Dynatrace Documentation
1313

0 commit comments

Comments
 (0)