You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The description of some fields escaped their indentation, which incorrectly showed them as other required/optional fields instead of being a sub-bullet point list of the current field.
Copy file name to clipboardExpand all lines: dynatrace/api/builtin/infrastructure/diskedge/anomalydetectors/settings/host_metadata_condition.go
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -23,22 +23,22 @@ import (
23
23
)
24
24
25
25
typeHostMetadataConditionstruct {
26
-
KeyMustExistbool`json:"keyMustExist"`// When enabled, the condition requires a metadata key to exist and match the constraints; when disabled, the key is optional but must still match the constrains if it is present.
27
-
MetadataConditionstring`json:"metadataCondition"`// This string has to match a required format.\n\n- `$contains(production)` – Matches if `production` appears anywhere in the host metadata value.\n- `$eq(production)` – Matches if `production` matches the host metadata value exactly.\n- `$prefix(production)` – Matches if `production` matches the prefix of the host metadata value.\n- `$suffix(production)` – Matches if `production` matches the suffix of the host metadata value.\n\nAvailable logic operations:\n- `$not($eq(production))` – Matches if the host metadata value is different from `production`.\n- `$and($prefix(production),$suffix(main))` – Matches if host metadata value starts with `production` and ends with `main`.\n- `$or($prefix(production),$suffix(main))` – Matches if host metadata value starts with `production` or ends with `main`.\n\nBrackets **(** and **)** that are part of the matched property **must be escaped with a tilde (~)**
26
+
KeyMustExistbool`json:"keyMustExist"`// When enabled, the condition requires a resource attribute to exist and match the constraints; when disabled, the key is optional but must still match the constrains if it is present.
27
+
MetadataConditionstring`json:"metadataCondition"`// This string has to match a required format.\n\n - `$match(ver*_1.2.?)` – Matches string with wildcards: `*` any number (including zero) of characters and `?` exactly one character.\n - `$contains(production)` – Matches if `production` appears anywhere in the host metadata value.\n - `$eq(production)` – Matches if `production` matches the host metadata value exactly.\n - `$prefix(production)` – Matches if `production` matches the prefix of the host metadata value.\n - `$suffix(production)` – Matches if `production` matches the suffix of the host metadata value.\n\n Available logic operations:\n - `$not($eq(production))` – Matches if the host metadata value is different from `production`.\n - `$and($prefix(production),$suffix(main))` – Matches if host metadata value starts with `production` and ends with `main`.\n - `$or($prefix(production),$suffix(main))` – Matches if host metadata value starts with `production` or ends with `main`.\n\n Brackets **(** and **)** that are part of the matched property **must be escaped with a tilde (~)**
Description: "When enabled, the condition requires a metadata key to exist and match the constraints; when disabled, the key is optional but must still match the constrains if it is present.",
35
+
Description: "When enabled, the condition requires a resource attribute to exist and match the constraints; when disabled, the key is optional but must still match the constrains if it is present.",
36
36
Optional: true,
37
37
Default: true,
38
38
},
39
39
"metadata_condition": {
40
40
Type: schema.TypeString,
41
-
Description: "This string has to match a required format.\n\n- `$contains(production)` – Matches if `production` appears anywhere in the host metadata value.\n- `$eq(production)` – Matches if `production` matches the host metadata value exactly.\n- `$prefix(production)` – Matches if `production` matches the prefix of the host metadata value.\n- `$suffix(production)` – Matches if `production` matches the suffix of the host metadata value.\n\nAvailable logic operations:\n- `$not($eq(production))` – Matches if the host metadata value is different from `production`.\n- `$and($prefix(production),$suffix(main))` – Matches if host metadata value starts with `production` and ends with `main`.\n- `$or($prefix(production),$suffix(main))` – Matches if host metadata value starts with `production` or ends with `main`.\n\nBrackets **(** and **)** that are part of the matched property **must be escaped with a tilde (~)**",
41
+
Description: "This string has to match a required format.\n\n - `$match(ver*_1.2.?)` – Matches string with wildcards: `*` any number (including zero) of characters and `?` exactly one character.\n - `$contains(production)` – Matches if `production` appears anywhere in the host metadata value.\n - `$eq(production)` – Matches if `production` matches the host metadata value exactly.\n - `$prefix(production)` – Matches if `production` matches the prefix of the host metadata value.\n - `$suffix(production)` – Matches if `production` matches the suffix of the host metadata value.\n\n Available logic operations:\n - `$not($eq(production))` – Matches if the host metadata value is different from `production`.\n - `$and($prefix(production),$suffix(main))` – Matches if host metadata value starts with `production` and ends with `main`.\n - `$or($prefix(production),$suffix(main))` – Matches if host metadata value starts with `production` or ends with `main`.\n\n Brackets **(** and **)** that are part of the matched property **must be escaped with a tilde (~)**",
Copy file name to clipboardExpand all lines: dynatrace/api/builtin/infrastructure/diskedge/anomalydetectors/settings/settings.go
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -27,8 +27,8 @@ type Settings struct {
27
27
DiskNameFilters []string`json:"diskNameFilters,omitempty"`// Disk will be included in this policy if **any** of the filters match
28
28
Enabledbool`json:"enabled"`// This setting is enabled (`true`) or disabled (`false`)
29
29
EventPropertiesMetadataItems`json:"eventProperties,omitempty"`// Set of additional key-value properties to be attached to the triggered event. You can retrieve the available property keys using the [Events API v2](https://dt-url.net/9622g1w). Additionally any Host resource attribute can be dynamically substituted (agent 1.325+)
30
-
HostMetadataConditionsHostMetadataConditionTypes`json:"hostMetadataConditions,omitempty"`// The policy will be enabled if **all** conditions are met
31
-
OperatingSystem []EoperatingSystem`json:"operatingSystem,omitempty"`// Select the operating systems on which policy should be applied
30
+
HostMetadataConditionsHostMetadataConditionTypes`json:"hostMetadataConditions,omitempty"`// Host resource attributes are dimensions enriching the host including custom metadata which are user-defined key-value pairs that you can assign to hosts monitored by Dynatrace.\n\n By defining custom metadata, you can enrich the monitoring data with context specific to your organization's needs, such as environment names, team ownership, application versions, or any other relevant details.\n\n See [Define tags and metadata for hosts](https://dt-url.net/w3hv0kbw).\n\n Note: Starting from version 1.325 host resource attributes are supported in addition to host custom metadata.
31
+
OperatingSystem []EoperatingSystem`json:"operatingSystem,omitempty"`// Select the operating systems on which policy should be applied. Possible values: `AIX`, `LINUX`, `WINDOWS`
32
32
PolicyNamestring`json:"policyName"`// Policy name
33
33
Scope*string`json:"-" scope:"scope"`// The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
Description: "The policy will be enabled if **all** conditions are met",
75
+
Description: "Host resource attributes are dimensions enriching the host including custom metadata which are user-defined key-value pairs that you can assign to hosts monitored by Dynatrace.\n\n By defining custom metadata, you can enrich the monitoring data with context specific to your organization's needs, such as environment names, team ownership, application versions, or any other relevant details.\n\n See [Define tags and metadata for hosts](https://dt-url.net/w3hv0kbw).\n\n Note: Starting from version 1.325 host resource attributes are supported in addition to host custom metadata.",
0 commit comments