|
| 1 | +--- |
| 2 | +layout: "" |
| 3 | +page_title: dynatrace_mobile_app_key_performance Resource - terraform-provider-dynatrace" |
| 4 | +subcategory: "Mobile & Custom Applications" |
| 5 | +description: |- |
| 6 | + The resource `dynatrace_mobile_app_key_performance` covers apdex threshold configuration for mobile/custom applications |
| 7 | +--- |
| 8 | + |
| 9 | +# dynatrace_mobile_app_key_performance (Resource) |
| 10 | + |
| 11 | +-> Configuration of the mobile/custom application scope overlaps with [dynatrace_mobile_application](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/resources/mobile_application), but this resource in addition provides an option for a key user action scope. |
| 12 | + |
| 13 | +-> This resource requires the API token scopes **Read settings** (`settings.read`) and **Write settings** (`settings.write`) |
| 14 | + |
| 15 | +## Dynatrace Documentation |
| 16 | + |
| 17 | +- Adjust Apdex settings for mobile applications - https://www.dynatrace.com/support/help/platform-modules/digital-experience/mobile-applications/additional-configuration/configure-apdex-mobile |
| 18 | + |
| 19 | +- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:rum.mobile.key-performance-metrics`) |
| 20 | + |
| 21 | +## Export Example Usage |
| 22 | + |
| 23 | +- `terraform-provider-dynatrace -export dynatrace_mobile_app_key_performance` downloads all existing apdex threshold configuration for mobile/custom applications |
| 24 | + |
| 25 | +The full documentation of the export feature is available [here](https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs/guides/export-v2). |
| 26 | + |
| 27 | +## Resource Example Usage |
| 28 | + |
| 29 | +```terraform |
| 30 | +resource "dynatrace_mobile_app_key_performance" "#name#" { |
| 31 | + frustrating_if_reported_or_web_request_error = true |
| 32 | + scope = "DEVICE_APPLICATION_METHOD-1234567890000000" |
| 33 | + thresholds { |
| 34 | + frustrating_threshold_seconds = 12 |
| 35 | + tolerable_threshold_seconds = 3 |
| 36 | + } |
| 37 | +} |
| 38 | +``` |
| 39 | + |
| 40 | +<!-- schema generated by tfplugindocs --> |
| 41 | +## Schema |
| 42 | + |
| 43 | +### Required |
| 44 | + |
| 45 | +- `frustrating_if_reported_or_web_request_error` (Boolean) Treat user actions with reported errors or web request errors as erroneous and rate their performance as Frustrating. Turn off this setting if errors should not affect the Apdex rate. |
| 46 | +- `scope` (String) The scope of this setting (DEVICE_APPLICATION_METHOD, MOBILE_APPLICATION, CUSTOM_APPLICATION) |
| 47 | +- `thresholds` (Block List, Min: 1, Max: 1) no documentation available (see [below for nested schema](#nestedblock--thresholds)) |
| 48 | + |
| 49 | +### Read-Only |
| 50 | + |
| 51 | +- `id` (String) The ID of this resource. |
| 52 | + |
| 53 | +<a id="nestedblock--thresholds"></a> |
| 54 | +### Nested Schema for `thresholds` |
| 55 | + |
| 56 | +Required: |
| 57 | + |
| 58 | +- `frustrating_threshold_seconds` (Number) If the action duration is above this value, the Apdex is considered to be **Frustrating**. |
| 59 | +- `tolerable_threshold_seconds` (Number) If the action duration is below this value, the Apdex is considered to be **Satisfactory**. |
| 60 | + |
0 commit comments