Skip to content

Commit ac0bf04

Browse files
Reinhard-Pilz-DynatraceReinhard-Pilz-Dynatrace
committed
v1.33.0
1 parent 12fc042 commit ac0bf04

26 files changed

+370
-98
lines changed

‎docs/data-sources/aws_credentials.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
layout: ""
3+
page_title: "dynatrace_aws_credentials Data Source - terraform-provider-dynatrace"
4+
description: |-
5+
The data source `dynatrace_aws_credentials` covers queries for AWS credentials
6+
---
7+
8+
# dynatrace_aws_credentials (Data Source)
9+
10+
The `dynatrace_aws_credentials` data source allows the AWS credential ID to be retrieved by its label.
11+
12+
- `label` (String) - The label/name of the AWS credential
13+
14+
## Example Usage
15+
16+
```terraform
17+
data "dynatrace_aws_credentials" "Example" {
18+
name = "Terraform Example"
19+
}
20+
21+
output "id" {
22+
value = data.dynatrace_aws_credentials.Example.id
23+
}
24+
25+
```
26+
27+
<!-- schema generated by tfplugindocs -->
28+
## Schema
29+
30+
### Required
31+
32+
- `label` (String)
33+
34+
### Read-Only
35+
36+
- `id` (String) The ID of this resource.

‎docs/data-sources/azure_credentials.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
layout: ""
3+
page_title: "dynatrace_azure_credentials Data Source - terraform-provider-dynatrace"
4+
description: |-
5+
The data source `dynatrace_azure_credentials` covers queries for Azure credentials
6+
---
7+
8+
# dynatrace_azure_credentials (Data Source)
9+
10+
The `dynatrace_azure_credentials` data source allows the Azure credential ID to be retrieved by its label.
11+
12+
- `label` (String) - The label/name of the Azure credential
13+
14+
## Example Usage
15+
16+
```terraform
17+
data "dynatrace_azure_credentials" "Example" {
18+
name = "Terraform Example"
19+
}
20+
21+
output "id" {
22+
value = data.dynatrace_azure_credentials.Example.id
23+
}
24+
25+
```
26+
27+
<!-- schema generated by tfplugindocs -->
28+
## Schema
29+
30+
### Required
31+
32+
- `label` (String)
33+
34+
### Read-Only
35+
36+
- `id` (String) The ID of this resource.

‎docs/data-sources/entities.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,10 @@ Optional:
4848
- `tags` (Block List) A set of tags assigned to the entity. (see [below for nested schema](#nestedblock--entities--tags))
4949
- `type` (String) The type of the entity.
5050

51+
Read-Only:
52+
53+
- `properties` (Map of String) Properties defining the entity.
54+
5155
<a id="nestedblock--entities--tags"></a>
5256
### Nested Schema for `entities.tags`
5357

‎docs/data-sources/entity.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,4 +38,5 @@ output "id" {
3838

3939
### Read-Only
4040

41-
- `id` (String) The ID of this resource.
41+
- `id` (String) The ID of this resource.
42+
- `properties` (Map of String) Properties defining the entity.

‎docs/data-sources/failure_detection_parameters.md‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
layout: ""
3+
page_title: "dynatrace_failure_detection_parameters Data Source - terraform-provider-dynatrace"
4+
description: |-
5+
The data source `dynatrace_failure_detection_parameters` covers queries for failure detection parameters
6+
---
7+
8+
# dynatrace_failure_detection_parameters (Data Source)
9+
10+
The `dynatrace_failure_detection_parameters` data source allows the failure detection parameter ID to be retrieved by its name.
11+
12+
- `name` (String) - The name of the failure detection parameter
13+
14+
If multiple services match the given criteria, the first result will be retrieved.
15+
16+
## Example Usage
17+
18+
```terraform
19+
data "dynatrace_failure_detection_parameters" "Example" {
20+
name = "Terraform Example"
21+
}
22+
23+
output "id" {
24+
value = data.dynatrace_failure_detection_parameters.Example.id
25+
}
26+
27+
```
28+
29+
<!-- schema generated by tfplugindocs -->
30+
## Schema
31+
32+
### Required
33+
34+
- `name` (String)
35+
36+
### Read-Only
37+
38+
- `id` (String) The ID of this resource.

‎docs/data-sources/update_windows.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
layout: ""
3+
page_title: "dynatrace_update_windows Data Source - terraform-provider-dynatrace"
4+
description: |-
5+
The data source `dynatrace_update_windows` covers queries for maintenance windows for OneAgent updates
6+
---
7+
8+
# dynatrace_update_windows (Data Source)
9+
10+
The `dynatrace_update_windows` data source allows the OneAgent update maintenance window ID to be retrieved by its name.
11+
12+
- `name` (String) - The name of the OneAgent update maintenance window
13+
14+
## Example Usage
15+
16+
```terraform
17+
data "dynatrace_update_windows" "Example" {
18+
name = "Terraform Example"
19+
}
20+
21+
output "id" {
22+
value = data.dynatrace_update_windows.Example.id
23+
}
24+
25+
```
26+
27+
<!-- schema generated by tfplugindocs -->
28+
## Schema
29+
30+
### Required
31+
32+
- `name` (String)
33+
34+
### Read-Only
35+
36+
- `id` (String) The ID of this resource.

‎docs/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Use the links to the left to learn about the available resources, data sources,
1818
terraform {
1919
required_providers {
2020
dynatrace = {
21-
version = "1.32.0"
21+
version = "1.33.0"
2222
source = "dynatrace-oss/dynatrace"
2323
}
2424
}

‎docs/resources/application_detection_rule.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The full documentation of the export feature is available [here](https://registr
2929

3030
### Optional
3131

32-
- `name` (String) The unique name of the Application detection rule
32+
- `name` (String, Deprecated) The unique name of the Application detection rule
3333
- `order` (String) The order of the rule in the rules list
3434

3535
### Read-Only

‎docs/resources/builtin_process_monitoring.md‎

Lines changed: 115 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
---
2+
layout: ""
3+
page_title: "dynatrace_builtin_process_monitoring Resource - terraform-provider-dynatrace"
4+
description: |-
5+
The resource `dynatrace_builtin_process_monitoring` covers configuration for built-in process monitoring rules
6+
---
7+
8+
# dynatrace_builtin_process_monitoring (Resource)
9+
10+
## Dynatrace Documentation
11+
12+
- Process deep monitoring - https://www.dynatrace.com/support/help/platform-modules/infrastructure-monitoring/process-groups/configuration/pg-monitoring
13+
14+
- Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId: `builtin:process.built-in-process-monitoring-rule`)
15+
16+
## Export Example Usage
17+
18+
- `terraform-provider-dynatrace -export dynatrace_builtin_process_monitoring` downloads all existing built-in process monitoring rules
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_builtin_process_monitoring" "#name#" {
26+
host_group_id = "environment"
27+
aspnetcore = false
28+
cf_appsmanagerjs = false
29+
container = false
30+
docker_pauseamd64 = false
31+
exe_bbs = false
32+
exe_caddy = false
33+
exe_schedular = false
34+
exe_silkdaemon = false
35+
go_static = false
36+
node_nodegyp = false
37+
}
38+
```
39+
40+
<!-- schema generated by tfplugindocs -->
41+
## Schema
42+
43+
### Optional
44+
45+
- `aspnetcore` (Boolean) Rule id: 3 - Do monitor processes if ASP.NET Core application path exists
46+
- `aspnetcore_agentlistener` (Boolean) Rule id: 64 - Do not monitor processes if ASP.NET Core application DLL contains 'Agent.Listener'
47+
- `aspnetcore_agentworker` (Boolean) Rule id: 62 - Do not monitor processes if ASP.NET Core application DLL contains 'Agent.Worker'
48+
- `cf` (Boolean) Rule id: 37 - Do monitor processes if Cloud Foundry application exists
49+
- `cf_appsmanagerjs` (Boolean) Do not monitor processes if Cloud Foundry application begins with 'apps-manager-js'
50+
- `container` (Boolean) Rule id: 41 - Do monitor processes if container name exists
51+
- `docker_pauseamd64` (Boolean) Rule id: 39 - Do not monitor processes if Docker stripped image contains 'pause-amd64'
52+
- `exe_adapter` (Boolean) Rule id: 7 - Do monitor processes if EXE name equals 'adapter'
53+
- `exe_agentlistener` (Boolean) Rule id: 63 - Do not monitor processes if EXE name contains 'Agent.Listener'
54+
- `exe_agentworker` (Boolean) Rule id: 61 - Do not monitor processes if EXE name contains 'Agent.Worker'
55+
- `exe_auctioneer` (Boolean) Rule id: 8 - Do monitor processes if EXE name equals 'auctioneer'
56+
- `exe_auditbeat` (Boolean) Rule id: 52 - Do not monitor processes if EXE name equals 'auditbeat'
57+
- `exe_bbs` (Boolean) Rule id: 9 - Do monitor processes if EXE name equals 'bbs'
58+
- `exe_caddy` (Boolean) Rule id: 5 - Do monitor processes if EXE name equals 'caddy'
59+
- `exe_caliconode` (Boolean) Rule id: 58 - Do not monitor processes if EXE name equals 'calico-node'
60+
- `exe_casclient` (Boolean) Rule id: 59 - Do not monitor processes if EXE name equals 'casclient.exe'
61+
- `exe_ccuploader` (Boolean) Rule id: 10 - Do monitor processes if EXE name equals 'cc-uploader'
62+
- `exe_doppler` (Boolean) Rule id: 11 - Do monitor processes if EXE name equals 'doppler'
63+
- `exe_filebeat` (Boolean) Rule id: 49 - Do not monitor processes if EXE name equals 'filebeat'
64+
- `exe_flexnetjobexecutorservice` (Boolean) Rule id: 65 - Do not monitor processes if EXE name equals 'FlexNetJobExecutorService'
65+
- `exe_flexnetmaintenanceremotingservice` (Boolean) Rule id: 66 - Do not monitor processes if EXE name equals 'FlexNetMaintenanceRemotingService'
66+
- `exe_functionbeat` (Boolean) Rule id: 54 - Do not monitor processes if EXE name equals 'functionbeat'
67+
- `exe_gorouter` (Boolean) Rule id: 12 - Do monitor processes if EXE name equals 'gorouter'
68+
- `exe_grootfs` (Boolean) Rule id: 55 - Do not monitor processes if EXE name equals 'grootfs'
69+
- `exe_heartbeat` (Boolean) Rule id: 53 - Do not monitor processes if EXE name equals 'heartbeat'
70+
- `exe_influxd` (Boolean) Rule id: 6 - Do monitor processes if EXE name equals 'influxd'
71+
- `exe_locket` (Boolean) Rule id: 13 - Do monitor processes if EXE name equals 'locket'
72+
- `exe_metricbeat` (Boolean) Rule id: 50 - Do not monitor processes if EXE name equals 'metricbeat'
73+
- `exe_metron` (Boolean) Rule id: 14 - Do monitor processes if EXE name equals 'metron'
74+
- `exe_mqsi` (Boolean) Rule id: 48 - Do not monitor processes if EXE name begins with 'mqsi'
75+
- `exe_oc` (Boolean) Rule id: 44 - Do not monitor processes if EXE name equals 'oc'
76+
- `exe_optcnibinhostlocal` (Boolean) Rule id: 46 - Do not monitor processes if EXE path equals '/opt/cni/bin/host-local'
77+
- `exe_packetbeat` (Boolean) Rule id: 51 - Do not monitor processes if EXE name equals 'packetbeat'
78+
- `exe_phpcgi` (Boolean) Rule id: 2 - Do not monitor processes if EXE name equals 'php-cgi'
79+
- `exe_rep` (Boolean) Rule id: 16 - Do monitor processes if EXE name equals 'rep'
80+
- `exe_routeemitter` (Boolean) Rule id: 17 - Do monitor processes if EXE name equals 'route-emitter'
81+
- `exe_routeregistrar` (Boolean) Rule id: 18 - Do monitor processes if EXE name equals 'route-registrar'
82+
- `exe_routingapi` (Boolean) Rule id: 19 - Do monitor processes if EXE name equals 'routing-api'
83+
- `exe_schedular` (Boolean) Rule id: 20 - Do monitor processes if EXE name equals 'scheduler'
84+
- `exe_silkdaemon` (Boolean) Rule id: 21 - Do monitor processes if EXE name equals 'silk-daemon'
85+
- `exe_switchboard` (Boolean) Rule id: 22 - Do monitor processes if EXE name equals 'switchboard'
86+
- `exe_syslogdrainbinder` (Boolean) Rule id: 23 - Do monitor processes if EXE name equals 'syslog_drain_binder'
87+
- `exe_tardis` (Boolean) Rule id: 56 - Do not monitor processes if EXE name equals 'tardis'
88+
- `exe_tmpbuildpacks` (Boolean) Rule id: 43 - Do not monitor processes if EXE path begins with '/tmp/buildpacks/'
89+
- `exe_tpswatcher` (Boolean) Rule id: 24 - Do monitor processes if EXE name equals 'tps-watcher'
90+
- `exe_trafficcontroller` (Boolean) Rule id: 25 - Do monitor processes if EXE name equals 'trafficcontroller'
91+
- `exe_uipath` (Boolean) Rule id: 70 - Do not monitor processes if EXE name contains 'UiPath'
92+
- `exe_userbinpiper` (Boolean) Rule id: 67 - Do not monitor processes if EXE path equals '/usr/bin/piper'
93+
- `exe_w3wp` (Boolean) Rule id: 4 - Do monitor processes if EXE name equals 'w3wp.exe'
94+
- `go_static` (Boolean) Rule id: 47 - Do not monitor processes if Go Binary Linkage equals 'static'
95+
- `host_group_id` (String) The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
96+
- `jar_dtibmmqconnector` (Boolean) Rule id: 60 - Do not monitor processes if JAR file name equals 'dynatrace_ibm_mq_connector.jar'
97+
- `jar_eclipseequinox` (Boolean) Rule id: 57 - Do not monitor processes if Java JAR file begins with 'org.eclipse.equinox.launcher'
98+
- `k8s_cassandraoperator` (Boolean) Rule id: 69 - Do not monitor processes if Kubernetes container name equals 'cassandra-operator'
99+
- `k8s_containerpod` (Boolean) Rule id: 38 - Do not monitor processes if Kubernetes container name equals 'POD'
100+
- `k8s_namespace` (Boolean) Rule id: 40 - Do monitor processes if Kubernetes namespace exists
101+
- `node_binpm2` (Boolean) Do not monitor processes if Node.js script equals 'bin/pm2'
102+
- `node_corepack` (Boolean) Rule id: 68 - Do not monitor processes if Node.js application equals 'corepack'
103+
- `node_grunt` (Boolean) Rule id: 28 - Do not monitor processes if Node.js application base directory ends with '/node_modules/grunt'
104+
- `node_gulpcli` (Boolean) Do not monitor processes if Node.js application base directory ends with '/node_modules/gulp-cli'
105+
- `node_nodegyp` (Boolean) Rule id: 33 - Do not monitor processes if Node.js application base directory ends with '/node_modules/node-gyp'
106+
- `node_nodepregyp` (Boolean) Rule id: 32 - Do not monitor processes if Node.js application base directory ends with '/node_modules/node-pre-gyp'
107+
- `node_npm` (Boolean) Rule id: 27 - Do not monitor processes if Node.js application base directory ends with '/node_modules/npm'
108+
- `node_prebuildinstall` (Boolean) Rule id: 26 - Do not monitor processes if Node.js application base directory ends with '/node_modules/prebuild-install'
109+
- `node_typescript` (Boolean) Rule id: 29 - Do not monitor processes if Node.js application base directory ends with '/node_modules/typescript'
110+
- `node_yarn` (Boolean) Rule id: 45 - Do not monitor processes if Node.js application equals 'yarn'
111+
112+
### Read-Only
113+
114+
- `id` (String) The ID of this resource.
115+

‎docs/resources/data_privacy.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,10 +47,10 @@ resource "dynatrace_data_privacy" "#name#" {
4747

4848
### Required
4949

50-
- `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))
51-
- `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))
52-
- `masking` (Block List, Min: 1, Max: 1) (Field has overlap with `dynatrace_application_data_privacy`) (see [below for nested schema](#nestedblock--masking))
53-
- `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))
50+
- `data_collection` (Block List, Min: 1, Max: 1) 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))
51+
- `do_not_track` (Block List, Min: 1, Max: 1) 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))
52+
- `masking` (Block List, Min: 1, Max: 1) no documentation available (see [below for nested schema](#nestedblock--masking))
53+
- `user_tracking` (Block List, Min: 1, Max: 1) User tracking (see [below for nested schema](#nestedblock--user_tracking))
5454

5555
### Optional
5656

0 commit comments

Comments
 (0)