dynatrace.DiskEdgeAnomalyDetectors

Disk filesystem will be included in this policy if any of the filters match. Disk filesystem has to match a required format.

• $match(ext*) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(fs) – Matches if fs appears anywhere in the filesystem type.
• $eq(ext4) – Matches if ext4 matches the filesystem type exactly.
• $prefix(ext) – Matches if ext matches the prefix of the filesystem type.
• $suffix(fs) – Matches if fs matches the suffix of the filesystem type.

Available logic operations:

• $not($eq(tmpfs)) – Matches if the filesystem type is different from tmpfs.
• $and($prefix(ext),$suffix(4)) – Matches if filesystem type starts with ext and ends with 4.
• $or($eq(xfs),$eq(btrfs)) – Matches if filesystem type equals xfs or btrfs.

Brackets ( and ) that are part of the matched filesystem type must be escaped with a tilde (~)

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.

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.

See Define tags and metadata for hosts.

Note: Starting from version 1.325 host resource attributes are supported in addition to host custom metadata.

Disk filesystem will be included in this policy if any of the filters match. Disk filesystem has to match a required format.

• $match(ext*) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(fs) – Matches if fs appears anywhere in the filesystem type.
• $eq(ext4) – Matches if ext4 matches the filesystem type exactly.
• $prefix(ext) – Matches if ext matches the prefix of the filesystem type.
• $suffix(fs) – Matches if fs matches the suffix of the filesystem type.

Available logic operations:

• $not($eq(tmpfs)) – Matches if the filesystem type is different from tmpfs.
• $and($prefix(ext),$suffix(4)) – Matches if filesystem type starts with ext and ends with 4.
• $or($eq(xfs),$eq(btrfs)) – Matches if filesystem type equals xfs or btrfs.

Brackets ( and ) that are part of the matched filesystem type must be escaped with a tilde (~)

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.

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.

See Define tags and metadata for hosts.

Note: Starting from version 1.325 host resource attributes are supported in addition to host custom metadata.

Disk filesystem will be included in this policy if any of the filters match. Disk filesystem has to match a required format.

• $match(ext*) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(fs) – Matches if fs appears anywhere in the filesystem type.
• $eq(ext4) – Matches if ext4 matches the filesystem type exactly.
• $prefix(ext) – Matches if ext matches the prefix of the filesystem type.
• $suffix(fs) – Matches if fs matches the suffix of the filesystem type.

Available logic operations:

• $not($eq(tmpfs)) – Matches if the filesystem type is different from tmpfs.
• $and($prefix(ext),$suffix(4)) – Matches if filesystem type starts with ext and ends with 4.
• $or($eq(xfs),$eq(btrfs)) – Matches if filesystem type equals xfs or btrfs.

Brackets ( and ) that are part of the matched filesystem type must be escaped with a tilde (~)

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.

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.

See Define tags and metadata for hosts.

Note: Starting from version 1.325 host resource attributes are supported in addition to host custom metadata.

Disk filesystem will be included in this policy if any of the filters match. Disk filesystem has to match a required format.

• $match(ext*) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(fs) – Matches if fs appears anywhere in the filesystem type.
• $eq(ext4) – Matches if ext4 matches the filesystem type exactly.
• $prefix(ext) – Matches if ext matches the prefix of the filesystem type.
• $suffix(fs) – Matches if fs matches the suffix of the filesystem type.

Available logic operations:

• $not($eq(tmpfs)) – Matches if the filesystem type is different from tmpfs.
• $and($prefix(ext),$suffix(4)) – Matches if filesystem type starts with ext and ends with 4.
• $or($eq(xfs),$eq(btrfs)) – Matches if filesystem type equals xfs or btrfs.

Brackets ( and ) that are part of the matched filesystem type must be escaped with a tilde (~)

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.

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.

See Define tags and metadata for hosts.

Note: Starting from version 1.325 host resource attributes are supported in addition to host custom metadata.

Disk filesystem will be included in this policy if any of the filters match. Disk filesystem has to match a required format.

• $match(ext*) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(fs) – Matches if fs appears anywhere in the filesystem type.
• $eq(ext4) – Matches if ext4 matches the filesystem type exactly.
• $prefix(ext) – Matches if ext matches the prefix of the filesystem type.
• $suffix(fs) – Matches if fs matches the suffix of the filesystem type.

Available logic operations:

• $not($eq(tmpfs)) – Matches if the filesystem type is different from tmpfs.
• $and($prefix(ext),$suffix(4)) – Matches if filesystem type starts with ext and ends with 4.
• $or($eq(xfs),$eq(btrfs)) – Matches if filesystem type equals xfs or btrfs.

Brackets ( and ) that are part of the matched filesystem type must be escaped with a tilde (~)

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.

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.

See Define tags and metadata for hosts.

Note: Starting from version 1.325 host resource attributes are supported in addition to host custom metadata.

Disk filesystem will be included in this policy if any of the filters match. Disk filesystem has to match a required format.

• $match(ext*) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(fs) – Matches if fs appears anywhere in the filesystem type.
• $eq(ext4) – Matches if ext4 matches the filesystem type exactly.
• $prefix(ext) – Matches if ext matches the prefix of the filesystem type.
• $suffix(fs) – Matches if fs matches the suffix of the filesystem type.

Available logic operations:

• $not($eq(tmpfs)) – Matches if the filesystem type is different from tmpfs.
• $and($prefix(ext),$suffix(4)) – Matches if filesystem type starts with ext and ends with 4.
• $or($eq(xfs),$eq(btrfs)) – Matches if filesystem type equals xfs or btrfs.

Brackets ( and ) that are part of the matched filesystem type must be escaped with a tilde (~)

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.

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.

See Define tags and metadata for hosts.

Note: Starting from version 1.325 host resource attributes are supported in addition to host custom metadata.

Disk filesystem will be included in this policy if any of the filters match. Disk filesystem has to match a required format.

• $match(ext*) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(fs) – Matches if fs appears anywhere in the filesystem type.
• $eq(ext4) – Matches if ext4 matches the filesystem type exactly.
• $prefix(ext) – Matches if ext matches the prefix of the filesystem type.
• $suffix(fs) – Matches if fs matches the suffix of the filesystem type.

Available logic operations:

• $not($eq(tmpfs)) – Matches if the filesystem type is different from tmpfs.
• $and($prefix(ext),$suffix(4)) – Matches if filesystem type starts with ext and ends with 4.
• $or($eq(xfs),$eq(btrfs)) – Matches if filesystem type equals xfs or btrfs.

Brackets ( and ) that are part of the matched filesystem type must be escaped with a tilde (~)

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.

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.

See Define tags and metadata for hosts.

Note: Starting from version 1.325 host resource attributes are supported in addition to host custom metadata.

This string has to match a required format.

• $match(ver*_1.2.?) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(production) – Matches if production appears anywhere in the host metadata value.
• $eq(production) – Matches if production matches the host metadata value exactly.
• $prefix(production) – Matches if production matches the prefix of the host metadata value.
• $suffix(production) – Matches if production matches the suffix of the host metadata value.

Available logic operations:

• $not($eq(production)) – Matches if the host metadata value is different from production.
• $and($prefix(production),$suffix(main)) – Matches if host metadata value starts with production and ends with main.
• $or($prefix(production),$suffix(main)) – Matches if host metadata value starts with production or ends with main.

Brackets ( and ) that are part of the matched property must be escaped with a tilde (~)

This string has to match a required format.

• $match(ver*_1.2.?) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(production) – Matches if production appears anywhere in the host metadata value.
• $eq(production) – Matches if production matches the host metadata value exactly.
• $prefix(production) – Matches if production matches the prefix of the host metadata value.
• $suffix(production) – Matches if production matches the suffix of the host metadata value.

Available logic operations:

• $not($eq(production)) – Matches if the host metadata value is different from production.
• $and($prefix(production),$suffix(main)) – Matches if host metadata value starts with production and ends with main.
• $or($prefix(production),$suffix(main)) – Matches if host metadata value starts with production or ends with main.

Brackets ( and ) that are part of the matched property must be escaped with a tilde (~)

This string has to match a required format.

• $match(ver*_1.2.?) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(production) – Matches if production appears anywhere in the host metadata value.
• $eq(production) – Matches if production matches the host metadata value exactly.
• $prefix(production) – Matches if production matches the prefix of the host metadata value.
• $suffix(production) – Matches if production matches the suffix of the host metadata value.

Available logic operations:

• $not($eq(production)) – Matches if the host metadata value is different from production.
• $and($prefix(production),$suffix(main)) – Matches if host metadata value starts with production and ends with main.
• $or($prefix(production),$suffix(main)) – Matches if host metadata value starts with production or ends with main.

Brackets ( and ) that are part of the matched property must be escaped with a tilde (~)

This string has to match a required format.

• $match(ver*_1.2.?) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(production) – Matches if production appears anywhere in the host metadata value.
• $eq(production) – Matches if production matches the host metadata value exactly.
• $prefix(production) – Matches if production matches the prefix of the host metadata value.
• $suffix(production) – Matches if production matches the suffix of the host metadata value.

Available logic operations:

• $not($eq(production)) – Matches if the host metadata value is different from production.
• $and($prefix(production),$suffix(main)) – Matches if host metadata value starts with production and ends with main.
• $or($prefix(production),$suffix(main)) – Matches if host metadata value starts with production or ends with main.

Brackets ( and ) that are part of the matched property must be escaped with a tilde (~)

This string has to match a required format.

• $match(ver*_1.2.?) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(production) – Matches if production appears anywhere in the host metadata value.
• $eq(production) – Matches if production matches the host metadata value exactly.
• $prefix(production) – Matches if production matches the prefix of the host metadata value.
• $suffix(production) – Matches if production matches the suffix of the host metadata value.

Available logic operations:

• $not($eq(production)) – Matches if the host metadata value is different from production.
• $and($prefix(production),$suffix(main)) – Matches if host metadata value starts with production and ends with main.
• $or($prefix(production),$suffix(main)) – Matches if host metadata value starts with production or ends with main.

Brackets ( and ) that are part of the matched property must be escaped with a tilde (~)

This string has to match a required format.

• $match(ver*_1.2.?) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(production) – Matches if production appears anywhere in the host metadata value.
• $eq(production) – Matches if production matches the host metadata value exactly.
• $prefix(production) – Matches if production matches the prefix of the host metadata value.
• $suffix(production) – Matches if production matches the suffix of the host metadata value.

Available logic operations:

• $not($eq(production)) – Matches if the host metadata value is different from production.
• $and($prefix(production),$suffix(main)) – Matches if host metadata value starts with production and ends with main.
• $or($prefix(production),$suffix(main)) – Matches if host metadata value starts with production or ends with main.

Brackets ( and ) that are part of the matched property must be escaped with a tilde (~)

This string has to match a required format.

• $match(ver*_1.2.?) – Matches string with wildcards: * any number (including zero) of characters and ? exactly one character.
• $contains(production) – Matches if production appears anywhere in the host metadata value.
• $eq(production) – Matches if production matches the host metadata value exactly.
• $prefix(production) – Matches if production matches the prefix of the host metadata value.
• $suffix(production) – Matches if production matches the suffix of the host metadata value.

Available logic operations:

• $not($eq(production)) – Matches if the host metadata value is different from production.
• $and($prefix(production),$suffix(main)) – Matches if host metadata value starts with production and ends with main.
• $or($prefix(production),$suffix(main)) – Matches if host metadata value starts with production or ends with main.

Brackets ( and ) that are part of the matched property must be escaped with a tilde (~)