Docs Home Pulumi IaC Pulumi ESC Pulumi Cloud Packages Tutorials
  1. Packages
  2. Dynatrace
  3. API Docs
  4. Alerting
Dynatrace v0.21.0 published on Sunday, Nov 17, 2024 by Pulumiverse
lbrlabs/pulumi-dynatrace

dynatrace.Alerting

Explore with Pulumi AI

dynatrace logo
Dynatrace v0.21.0 published on Sunday, Nov 17, 2024 by Pulumiverse
lbrlabs/pulumi-dynatrace

    Create Alerting Resource

    Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.

    Constructor syntax

    new Alerting(name: string, args?: AlertingArgs, opts?: CustomResourceOptions);
    @overload
def Alerting(resource_name: str,
             args: Optional[AlertingArgs] = None,
             opts: Optional[ResourceOptions] = None)

@overload
def Alerting(resource_name: str,
             opts: Optional[ResourceOptions] = None,
             filters: Optional[AlertingFiltersArgs] = None,
             legacy_id: Optional[str] = None,
             management_zone: Optional[str] = None,
             name: Optional[str] = None,
             rules: Optional[AlertingRulesArgs] = None)
    func NewAlerting(ctx *Context, name string, args *AlertingArgs, opts ...ResourceOption) (*Alerting, error)
    public Alerting(string name, AlertingArgs? args = null, CustomResourceOptions? opts = null)
    public Alerting(String name, AlertingArgs args)
public Alerting(String name, AlertingArgs args, CustomResourceOptions options)

    type: dynatrace:Alerting
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.

    Parameters

    name string
    The unique name of the resource.
    args AlertingArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    resource_name str
    The unique name of the resource.
    args AlertingArgs
    The arguments to resource properties.
    opts ResourceOptions
    Bag of options to control resource's behavior.
    ctx Context
    Context object for the current deployment.
    name string
    The unique name of the resource.
    args AlertingArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args AlertingArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args AlertingArgs
    The arguments to resource properties.
    options CustomResourceOptions
    Bag of options to control resource's behavior.

    Constructor example

    The following reference example uses placeholder values for all input properties.

    var alertingResource = new Dynatrace.Alerting("alertingResource", new()
{
    Filters = new Dynatrace.Inputs.AlertingFiltersArgs
    {
        Filters = new[]
        {
            new Dynatrace.Inputs.AlertingFiltersFilterArgs
            {
                Custom = new Dynatrace.Inputs.AlertingFiltersFilterCustomArgs
                {
                    Description = new Dynatrace.Inputs.AlertingFiltersFilterCustomDescriptionArgs
                    {
                        Operator = "string",
                        Value = "string",
                        CaseSensitive = false,
                        Enabled = false,
                        Negate = false,
                    },
                    Metadata = new Dynatrace.Inputs.AlertingFiltersFilterCustomMetadataArgs
                    {
                        Items = new Dynatrace.Inputs.AlertingFiltersFilterCustomMetadataItemsArgs
                        {
                            Filters = new[]
                            {
                                new Dynatrace.Inputs.AlertingFiltersFilterCustomMetadataItemsFilterArgs
                                {
                                    Key = "string",
                                    Value = "string",
                                    Negate = false,
                                },
                            },
                        },
                    },
                    Title = new Dynatrace.Inputs.AlertingFiltersFilterCustomTitleArgs
                    {
                        Operator = "string",
                        Value = "string",
                        CaseSensitive = false,
                        Enabled = false,
                        Negate = false,
                    },
                },
                Predefined = new Dynatrace.Inputs.AlertingFiltersFilterPredefinedArgs
                {
                    Type = "string",
                    Negate = false,
                },
            },
        },
    },
    LegacyId = "string",
    ManagementZone = "string",
    Name = "string",
    Rules = new Dynatrace.Inputs.AlertingRulesArgs
    {
        Rules = new[]
        {
            new Dynatrace.Inputs.AlertingRulesRuleArgs
            {
                DelayInMinutes = 0,
                IncludeMode = "string",
                SeverityLevel = "string",
                Tags = new[]
                {
                    "string",
                },
            },
        },
    },
});

    example, err := dynatrace.NewAlerting(ctx, "alertingResource", &dynatrace.AlertingArgs{
	Filters: &dynatrace.AlertingFiltersArgs{
		Filters: dynatrace.AlertingFiltersFilterArray{
			&dynatrace.AlertingFiltersFilterArgs{
				Custom: &dynatrace.AlertingFiltersFilterCustomArgs{
					Description: &dynatrace.AlertingFiltersFilterCustomDescriptionArgs{
						Operator:      pulumi.String("string"),
						Value:         pulumi.String("string"),
						CaseSensitive: pulumi.Bool(false),
						Enabled:       pulumi.Bool(false),
						Negate:        pulumi.Bool(false),
					},
					Metadata: &dynatrace.AlertingFiltersFilterCustomMetadataArgs{
						Items: &dynatrace.AlertingFiltersFilterCustomMetadataItemsArgs{
							Filters: dynatrace.AlertingFiltersFilterCustomMetadataItemsFilterArray{
								&dynatrace.AlertingFiltersFilterCustomMetadataItemsFilterArgs{
									Key:    pulumi.String("string"),
									Value:  pulumi.String("string"),
									Negate: pulumi.Bool(false),
								},
							},
						},
					},
					Title: &dynatrace.AlertingFiltersFilterCustomTitleArgs{
						Operator:      pulumi.String("string"),
						Value:         pulumi.String("string"),
						CaseSensitive: pulumi.Bool(false),
						Enabled:       pulumi.Bool(false),
						Negate:        pulumi.Bool(false),
					},
				},
				Predefined: &dynatrace.AlertingFiltersFilterPredefinedArgs{
					Type:   pulumi.String("string"),
					Negate: pulumi.Bool(false),
				},
			},
		},
	},
	LegacyId:       pulumi.String("string"),
	ManagementZone: pulumi.String("string"),
	Name:           pulumi.String("string"),
	Rules: &dynatrace.AlertingRulesArgs{
		Rules: dynatrace.AlertingRulesRuleArray{
			&dynatrace.AlertingRulesRuleArgs{
				DelayInMinutes: pulumi.Int(0),
				IncludeMode:    pulumi.String("string"),
				SeverityLevel:  pulumi.String("string"),
				Tags: pulumi.StringArray{
					pulumi.String("string"),
				},
			},
		},
	},
})

    var alertingResource = new Alerting("alertingResource", AlertingArgs.builder()
    .filters(AlertingFiltersArgs.builder()
        .filters(AlertingFiltersFilterArgs.builder()
            .custom(AlertingFiltersFilterCustomArgs.builder()
                .description(AlertingFiltersFilterCustomDescriptionArgs.builder()
                    .operator("string")
                    .value("string")
                    .caseSensitive(false)
                    .enabled(false)
                    .negate(false)
                    .build())
                .metadata(AlertingFiltersFilterCustomMetadataArgs.builder()
                    .items(AlertingFiltersFilterCustomMetadataItemsArgs.builder()
                        .filters(AlertingFiltersFilterCustomMetadataItemsFilterArgs.builder()
                            .key("string")
                            .value("string")
                            .negate(false)
                            .build())
                        .build())
                    .build())
                .title(AlertingFiltersFilterCustomTitleArgs.builder()
                    .operator("string")
                    .value("string")
                    .caseSensitive(false)
                    .enabled(false)
                    .negate(false)
                    .build())
                .build())
            .predefined(AlertingFiltersFilterPredefinedArgs.builder()
                .type("string")
                .negate(false)
                .build())
            .build())
        .build())
    .legacyId("string")
    .managementZone("string")
    .name("string")
    .rules(AlertingRulesArgs.builder()
        .rules(AlertingRulesRuleArgs.builder()
            .delayInMinutes(0)
            .includeMode("string")
            .severityLevel("string")
            .tags("string")
            .build())
        .build())
    .build());

    alerting_resource = dynatrace.Alerting("alertingResource",
    filters={
        "filters": [{
            "custom": {
                "description": {
                    "operator": "string",
                    "value": "string",
                    "case_sensitive": False,
                    "enabled": False,
                    "negate": False,
                },
                "metadata": {
                    "items": {
                        "filters": [{
                            "key": "string",
                            "value": "string",
                            "negate": False,
                        }],
                    },
                },
                "title": {
                    "operator": "string",
                    "value": "string",
                    "case_sensitive": False,
                    "enabled": False,
                    "negate": False,
                },
            },
            "predefined": {
                "type": "string",
                "negate": False,
            },
        }],
    },
    legacy_id="string",
    management_zone="string",
    name="string",
    rules={
        "rules": [{
            "delay_in_minutes": 0,
            "include_mode": "string",
            "severity_level": "string",
            "tags": ["string"],
        }],
    })

    const alertingResource = new dynatrace.Alerting("alertingResource", {
    filters: {
        filters: [{
            custom: {
                description: {
                    operator: "string",
                    value: "string",
                    caseSensitive: false,
                    enabled: false,
                    negate: false,
                },
                metadata: {
                    items: {
                        filters: [{
                            key: "string",
                            value: "string",
                            negate: false,
                        }],
                    },
                },
                title: {
                    operator: "string",
                    value: "string",
                    caseSensitive: false,
                    enabled: false,
                    negate: false,
                },
            },
            predefined: {
                type: "string",
                negate: false,
            },
        }],
    },
    legacyId: "string",
    managementZone: "string",
    name: "string",
    rules: {
        rules: [{
            delayInMinutes: 0,
            includeMode: "string",
            severityLevel: "string",
            tags: ["string"],
        }],
    },
});

    type: dynatrace:Alerting
properties:
    filters:
        filters:
            - custom:
                description:
                    caseSensitive: false
                    enabled: false
                    negate: false
                    operator: string
                    value: string
                metadata:
                    items:
                        filters:
                            - key: string
                              negate: false
                              value: string
                title:
                    caseSensitive: false
                    enabled: false
                    negate: false
                    operator: string
                    value: string
              predefined:
                negate: false
                type: string
    legacyId: string
    managementZone: string
    name: string
    rules:
        rules:
            - delayInMinutes: 0
              includeMode: string
              severityLevel: string
              tags:
                - string

    Alerting Resource Properties

    To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.

    Inputs

    In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.

    The Alerting resource accepts the following input properties:

    Filters Pulumiverse.Dynatrace.Inputs.AlertingFilters
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    LegacyId string
    The ID of this setting when referred to by the Config REST API V1
    ManagementZone string
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    Name string
    The name of the alerting profile, displayed in the UI
    Rules Pulumiverse.Dynatrace.Inputs.AlertingRules
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    Filters AlertingFiltersArgs
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    LegacyId string
    The ID of this setting when referred to by the Config REST API V1
    ManagementZone string
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    Name string
    The name of the alerting profile, displayed in the UI
    Rules AlertingRulesArgs
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    filters AlertingFilters
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    legacyId String
    The ID of this setting when referred to by the Config REST API V1
    managementZone String
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    name String
    The name of the alerting profile, displayed in the UI
    rules AlertingRules
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    filters AlertingFilters
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    legacyId string
    The ID of this setting when referred to by the Config REST API V1
    managementZone string
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    name string
    The name of the alerting profile, displayed in the UI
    rules AlertingRules
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    filters AlertingFiltersArgs
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    legacy_id str
    The ID of this setting when referred to by the Config REST API V1
    management_zone str
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    name str
    The name of the alerting profile, displayed in the UI
    rules AlertingRulesArgs
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    filters Property Map
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    legacyId String
    The ID of this setting when referred to by the Config REST API V1
    managementZone String
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    name String
    The name of the alerting profile, displayed in the UI
    rules Property Map
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules

    Outputs

    All input properties are implicitly available as output properties. Additionally, the Alerting resource produces the following output properties:

    Id string
    The provider-assigned unique ID for this managed resource.
    Id string
    The provider-assigned unique ID for this managed resource.
    id String
    The provider-assigned unique ID for this managed resource.
    id string
    The provider-assigned unique ID for this managed resource.
    id str
    The provider-assigned unique ID for this managed resource.
    id String
    The provider-assigned unique ID for this managed resource.

    Look up Existing Alerting Resource

    Get an existing Alerting resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.

    public static get(name: string, id: Input<ID>, state?: AlertingState, opts?: CustomResourceOptions): Alerting
    @staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        filters: Optional[AlertingFiltersArgs] = None,
        legacy_id: Optional[str] = None,
        management_zone: Optional[str] = None,
        name: Optional[str] = None,
        rules: Optional[AlertingRulesArgs] = None) -> Alerting
    func GetAlerting(ctx *Context, name string, id IDInput, state *AlertingState, opts ...ResourceOption) (*Alerting, error)
    public static Alerting Get(string name, Input<string> id, AlertingState? state, CustomResourceOptions? opts = null)
    public static Alerting get(String name, Output<String> id, AlertingState state, CustomResourceOptions options)
    Resource lookup is not supported in YAML
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    resource_name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    The following state arguments are supported:
    Filters Pulumiverse.Dynatrace.Inputs.AlertingFilters
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    LegacyId string
    The ID of this setting when referred to by the Config REST API V1
    ManagementZone string
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    Name string
    The name of the alerting profile, displayed in the UI
    Rules Pulumiverse.Dynatrace.Inputs.AlertingRules
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    Filters AlertingFiltersArgs
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    LegacyId string
    The ID of this setting when referred to by the Config REST API V1
    ManagementZone string
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    Name string
    The name of the alerting profile, displayed in the UI
    Rules AlertingRulesArgs
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    filters AlertingFilters
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    legacyId String
    The ID of this setting when referred to by the Config REST API V1
    managementZone String
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    name String
    The name of the alerting profile, displayed in the UI
    rules AlertingRules
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    filters AlertingFilters
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    legacyId string
    The ID of this setting when referred to by the Config REST API V1
    managementZone string
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    name string
    The name of the alerting profile, displayed in the UI
    rules AlertingRules
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    filters AlertingFiltersArgs
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    legacy_id str
    The ID of this setting when referred to by the Config REST API V1
    management_zone str
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    name str
    The name of the alerting profile, displayed in the UI
    rules AlertingRulesArgs
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules
    filters Property Map
    The list of event filters. For all filters that are negated inside of these event filters, that is all Predefined as well as Custom (Title and/or Description) ones the AND logic applies. For all non-negated ones the OR logic applies. Between these two groups, negated and non-negated, the AND logic applies. If you specify both severity rule and event filter, the AND logic applies
    legacyId String
    The ID of this setting when referred to by the Config REST API V1
    managementZone String
    Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
    name String
    The name of the alerting profile, displayed in the UI
    rules Property Map
    A list of rules for management zone usage. Each rule is evaluated independently of all other rules

    Supporting Types

    AlertingFilters, AlertingFiltersArgs

    Filters []AlertingFiltersFilter
    A conditions for the metric usage
    filters List<AlertingFiltersFilter>
    A conditions for the metric usage
    filters AlertingFiltersFilter[]
    A conditions for the metric usage
    filters Sequence[AlertingFiltersFilter]
    A conditions for the metric usage
    filters List<Property Map>
    A conditions for the metric usage

    AlertingFiltersFilter, AlertingFiltersFilterArgs

    Custom Pulumiverse.Dynatrace.Inputs.AlertingFiltersFilterCustom
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    Predefined Pulumiverse.Dynatrace.Inputs.AlertingFiltersFilterPredefined
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    Custom AlertingFiltersFilterCustom
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    Predefined AlertingFiltersFilterPredefined
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    custom AlertingFiltersFilterCustom
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    predefined AlertingFiltersFilterPredefined
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    custom AlertingFiltersFilterCustom
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    predefined AlertingFiltersFilterPredefined
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    custom AlertingFiltersFilterCustom
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    predefined AlertingFiltersFilterPredefined
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    custom Property Map
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies
    predefined Property Map
    Configuration of a custom event filter. Filters custom events by title or description. If both specified, the AND logic applies

    AlertingFiltersFilterCustom, AlertingFiltersFilterCustomArgs

    Description AlertingFiltersFilterCustomDescription
    Configuration of a matching filter
    Metadata AlertingFiltersFilterCustomMetadata
    Configuration of a matching filter
    Title AlertingFiltersFilterCustomTitle
    Configuration of a matching filter
    description AlertingFiltersFilterCustomDescription
    Configuration of a matching filter
    metadata AlertingFiltersFilterCustomMetadata
    Configuration of a matching filter
    title AlertingFiltersFilterCustomTitle
    Configuration of a matching filter
    description AlertingFiltersFilterCustomDescription
    Configuration of a matching filter
    metadata AlertingFiltersFilterCustomMetadata
    Configuration of a matching filter
    title AlertingFiltersFilterCustomTitle
    Configuration of a matching filter
    description AlertingFiltersFilterCustomDescription
    Configuration of a matching filter
    metadata AlertingFiltersFilterCustomMetadata
    Configuration of a matching filter
    title AlertingFiltersFilterCustomTitle
    Configuration of a matching filter
    description Property Map
    Configuration of a matching filter
    metadata Property Map
    Configuration of a matching filter
    title Property Map
    Configuration of a matching filter

    AlertingFiltersFilterCustomDescription, AlertingFiltersFilterCustomDescriptionArgs

    Operator string
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    Value string
    The value to compare to
    CaseSensitive bool
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    Enabled bool
    The filter is enabled (true) or disabled (false)
    Negate bool
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    Operator string
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    Value string
    The value to compare to
    CaseSensitive bool
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    Enabled bool
    The filter is enabled (true) or disabled (false)
    Negate bool
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    operator String
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    value String
    The value to compare to
    caseSensitive Boolean
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    enabled Boolean
    The filter is enabled (true) or disabled (false)
    negate Boolean
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    operator string
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    value string
    The value to compare to
    caseSensitive boolean
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    enabled boolean
    The filter is enabled (true) or disabled (false)
    negate boolean
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    operator str
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    value str
    The value to compare to
    case_sensitive bool
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    enabled bool
    The filter is enabled (true) or disabled (false)
    negate bool
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    operator String
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    value String
    The value to compare to
    caseSensitive Boolean
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    enabled Boolean
    The filter is enabled (true) or disabled (false)
    negate Boolean
    Reverses the comparison operator. For example it turns the begins with into does not begin with

    AlertingFiltersFilterCustomMetadata, AlertingFiltersFilterCustomMetadataArgs

    Items Pulumiverse.Dynatrace.Inputs.AlertingFiltersFilterCustomMetadataItems
    Define filters for event properties. A maximum of 20 properties is allowed.
    Items AlertingFiltersFilterCustomMetadataItems
    Define filters for event properties. A maximum of 20 properties is allowed.
    items AlertingFiltersFilterCustomMetadataItems
    Define filters for event properties. A maximum of 20 properties is allowed.
    items AlertingFiltersFilterCustomMetadataItems
    Define filters for event properties. A maximum of 20 properties is allowed.
    items AlertingFiltersFilterCustomMetadataItems
    Define filters for event properties. A maximum of 20 properties is allowed.
    items Property Map
    Define filters for event properties. A maximum of 20 properties is allowed.

    AlertingFiltersFilterCustomMetadataItems, AlertingFiltersFilterCustomMetadataItemsArgs

    AlertingFiltersFilterCustomMetadataItemsFilter, AlertingFiltersFilterCustomMetadataItemsFilterArgs

    Key string
    GET /api/v2/eventProperties for list of available keys
    Value string
    Value
    Negate bool
    no documentation available
    Key string
    GET /api/v2/eventProperties for list of available keys
    Value string
    Value
    Negate bool
    no documentation available
    key String
    GET /api/v2/eventProperties for list of available keys
    value String
    Value
    negate Boolean
    no documentation available
    key string
    GET /api/v2/eventProperties for list of available keys
    value string
    Value
    negate boolean
    no documentation available
    key str
    GET /api/v2/eventProperties for list of available keys
    value str
    Value
    negate bool
    no documentation available
    key String
    GET /api/v2/eventProperties for list of available keys
    value String
    Value
    negate Boolean
    no documentation available

    AlertingFiltersFilterCustomTitle, AlertingFiltersFilterCustomTitleArgs

    Operator string
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    Value string
    The value to compare to
    CaseSensitive bool
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    Enabled bool
    The filter is enabled (true) or disabled (false)
    Negate bool
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    Operator string
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    Value string
    The value to compare to
    CaseSensitive bool
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    Enabled bool
    The filter is enabled (true) or disabled (false)
    Negate bool
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    operator String
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    value String
    The value to compare to
    caseSensitive Boolean
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    enabled Boolean
    The filter is enabled (true) or disabled (false)
    negate Boolean
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    operator string
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    value string
    The value to compare to
    caseSensitive boolean
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    enabled boolean
    The filter is enabled (true) or disabled (false)
    negate boolean
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    operator str
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    value str
    The value to compare to
    case_sensitive bool
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    enabled bool
    The filter is enabled (true) or disabled (false)
    negate bool
    Reverses the comparison operator. For example it turns the begins with into does not begin with
    operator String
    Operator of the comparison. You can reverse it by setting negate to true. Possible values are BEGINS_WITH, CONTAINS, REGEX_MATCHES, ENDS_WITH and STRING_EQUALS
    value String
    The value to compare to
    caseSensitive Boolean
    The condition is case sensitive (false) or case insensitive (true). If not set, then false is used, making the condition case sensitive
    enabled Boolean
    The filter is enabled (true) or disabled (false)
    negate Boolean
    Reverses the comparison operator. For example it turns the begins with into does not begin with

    AlertingFiltersFilterPredefined, AlertingFiltersFilterPredefinedArgs

    Type string
    The type of the predefined event. Possible values are APPLICATION_ERROR_RATE_INCREASED, APPLICATION_SLOWDOWN, APPLICATION_UNEXPECTED_HIGH_LOAD, APPLICATION_UNEXPECTED_LOW_LOAD, AWS_LAMBDA_HIGH_ERROR_RATE, CUSTOM_APPLICATION_ERROR_RATE_INCREASED, CUSTOM_APPLICATION_SLOWDOWN, CUSTOM_APPLICATION_UNEXPECTED_HIGH_LOAD, CUSTOM_APPLICATION_UNEXPECTED_LOW_LOAD, CUSTOM_APP_CRASH_RATE_INCREASED, DATABASE_CONNECTION_FAILURE, DATA_CENTER_SERVICE_PERFORMANCE_DEGRADATION, DATA_CENTER_SERVICE_UNAVAILABLE, EBS_VOLUME_HIGH_LATENCY, EC2_HIGH_CPU, ELB_HIGH_BACKEND_ERROR_RATE, ENTERPRICE_APPLICATION_PERFORMANCE_DEGRADATION, ENTERPRISE_APPLICATION_UNAVAILABLE, ESXI_GUEST_ACTIVE_SWAP_WAIT, ESXI_GUEST_CPU_LIMIT_REACHED, ESXI_HOST_CPU_SATURATION, ESXI_HOST_DATASTORE_LOW_DISK_SPACE, ESXI_HOST_DISK_QUEUE_SLOW, ESXI_HOST_DISK_SLOW, ESXI_HOST_MEMORY_SATURATION, ESXI_HOST_NETWORK_PROBLEMS, ESXI_HOST_OVERLOADED_STORAGE, ESXI_VM_IMPACT_HOST_CPU_SATURATION, ESXI_VM_IMPACT_HOST_MEMORY_SATURATION, EXTERNAL_SYNTHETIC_TEST_OUTAGE, EXTERNAL_SYNTHETIC_TEST_SLOWDOWN, HOST_OF_SERVICE_UNAVAILABLE, HTTP_CHECK_GLOBAL_OUTAGE, HTTP_CHECK_LOCAL_OUTAGE, HTTP_CHECK_TEST_LOCATION_SLOWDOWN, MOBILE_APPLICATION_ERROR_RATE_INCREASED, MOBILE_APPLICATION_SLOWDOWN, MOBILE_APPLICATION_UNEXPECTED_HIGH_LOAD, MOBILE_APPLICATION_UNEXPECTED_LOW_LOAD, MOBILE_APP_CRASH_RATE_INCREASED, MONITORING_UNAVAILABLE, OSI_DISK_LOW_INODES, OSI_GRACEFULLY_SHUTDOWN, OSI_HIGH_CPU, OSI_HIGH_MEMORY, OSI_LOW_DISK_SPACE, OSI_NIC_DROPPED_PACKETS_HIGH, OSI_NIC_ERRORS_HIGH, OSI_NIC_UTILIZATION_HIGH, OSI_SLOW_DISK, OSI_UNEXPECTEDLY_UNAVAILABLE, PGI_OF_SERVICE_UNAVAILABLE, PGI_UNAVAILABLE, PG_LOW_INSTANCE_COUNT, PROCESS_CRASHED, PROCESS_HIGH_GC_ACTIVITY, PROCESS_MEMORY_RESOURCE_EXHAUSTED, PROCESS_NA_HIGH_CONN_FAIL_RATE, PROCESS_NA_HIGH_LOSS_RATE, PROCESS_THREADS_RESOURCE_EXHAUSTED, RDS_HIGH_CPU, RDS_HIGH_LATENCY, RDS_LOW_MEMORY, RDS_LOW_STORAGE_SPACE, RDS_OF_SERVICE_UNAVAILABLE, RDS_RESTART_SEQUENCE, SERVICE_ERROR_RATE_INCREASED, SERVICE_SLOWDOWN, SERVICE_UNEXPECTED_HIGH_LOAD, SERVICE_UNEXPECTED_LOW_LOAD, SYNTHETIC_GLOBAL_OUTAGE, SYNTHETIC_LOCAL_OUTAGE, SYNTHETIC_NODE_OUTAGE, SYNTHETIC_PRIVATE_LOCATION_OUTAGE and SYNTHETIC_TEST_LOCATION_SLOWDOWN
    Negate bool
    The alert triggers when the problem of specified severity arises while the specified event is happening (false) or while the specified event is not happening (true). For example, if you chose the Slowdown (PERFORMANCE) severity and Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event with negate set to true, the alerting profile will trigger only when the slowdown problem is raised while there is no unexpected high traffic event. Consider the following use case as an example. The Slowdown (PERFORMANCE) severity rule is set. Depending on the configuration of the event filter (Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event is used as an example), the options of the alerting profile is one of the following:* **negate** is set to false: The alert triggers when the slowdown problem is raised while unexpected high traffic event is happening. * **negate** is set to true: The alert triggers when the slowdown problem is raised while there is no unexpected high traffic event. * no event rule is set: The alert triggers when the slowdown problem is raised, regardless of any events
    Type string
    The type of the predefined event. Possible values are APPLICATION_ERROR_RATE_INCREASED, APPLICATION_SLOWDOWN, APPLICATION_UNEXPECTED_HIGH_LOAD, APPLICATION_UNEXPECTED_LOW_LOAD, AWS_LAMBDA_HIGH_ERROR_RATE, CUSTOM_APPLICATION_ERROR_RATE_INCREASED, CUSTOM_APPLICATION_SLOWDOWN, CUSTOM_APPLICATION_UNEXPECTED_HIGH_LOAD, CUSTOM_APPLICATION_UNEXPECTED_LOW_LOAD, CUSTOM_APP_CRASH_RATE_INCREASED, DATABASE_CONNECTION_FAILURE, DATA_CENTER_SERVICE_PERFORMANCE_DEGRADATION, DATA_CENTER_SERVICE_UNAVAILABLE, EBS_VOLUME_HIGH_LATENCY, EC2_HIGH_CPU, ELB_HIGH_BACKEND_ERROR_RATE, ENTERPRICE_APPLICATION_PERFORMANCE_DEGRADATION, ENTERPRISE_APPLICATION_UNAVAILABLE, ESXI_GUEST_ACTIVE_SWAP_WAIT, ESXI_GUEST_CPU_LIMIT_REACHED, ESXI_HOST_CPU_SATURATION, ESXI_HOST_DATASTORE_LOW_DISK_SPACE, ESXI_HOST_DISK_QUEUE_SLOW, ESXI_HOST_DISK_SLOW, ESXI_HOST_MEMORY_SATURATION, ESXI_HOST_NETWORK_PROBLEMS, ESXI_HOST_OVERLOADED_STORAGE, ESXI_VM_IMPACT_HOST_CPU_SATURATION, ESXI_VM_IMPACT_HOST_MEMORY_SATURATION, EXTERNAL_SYNTHETIC_TEST_OUTAGE, EXTERNAL_SYNTHETIC_TEST_SLOWDOWN, HOST_OF_SERVICE_UNAVAILABLE, HTTP_CHECK_GLOBAL_OUTAGE, HTTP_CHECK_LOCAL_OUTAGE, HTTP_CHECK_TEST_LOCATION_SLOWDOWN, MOBILE_APPLICATION_ERROR_RATE_INCREASED, MOBILE_APPLICATION_SLOWDOWN, MOBILE_APPLICATION_UNEXPECTED_HIGH_LOAD, MOBILE_APPLICATION_UNEXPECTED_LOW_LOAD, MOBILE_APP_CRASH_RATE_INCREASED, MONITORING_UNAVAILABLE, OSI_DISK_LOW_INODES, OSI_GRACEFULLY_SHUTDOWN, OSI_HIGH_CPU, OSI_HIGH_MEMORY, OSI_LOW_DISK_SPACE, OSI_NIC_DROPPED_PACKETS_HIGH, OSI_NIC_ERRORS_HIGH, OSI_NIC_UTILIZATION_HIGH, OSI_SLOW_DISK, OSI_UNEXPECTEDLY_UNAVAILABLE, PGI_OF_SERVICE_UNAVAILABLE, PGI_UNAVAILABLE, PG_LOW_INSTANCE_COUNT, PROCESS_CRASHED, PROCESS_HIGH_GC_ACTIVITY, PROCESS_MEMORY_RESOURCE_EXHAUSTED, PROCESS_NA_HIGH_CONN_FAIL_RATE, PROCESS_NA_HIGH_LOSS_RATE, PROCESS_THREADS_RESOURCE_EXHAUSTED, RDS_HIGH_CPU, RDS_HIGH_LATENCY, RDS_LOW_MEMORY, RDS_LOW_STORAGE_SPACE, RDS_OF_SERVICE_UNAVAILABLE, RDS_RESTART_SEQUENCE, SERVICE_ERROR_RATE_INCREASED, SERVICE_SLOWDOWN, SERVICE_UNEXPECTED_HIGH_LOAD, SERVICE_UNEXPECTED_LOW_LOAD, SYNTHETIC_GLOBAL_OUTAGE, SYNTHETIC_LOCAL_OUTAGE, SYNTHETIC_NODE_OUTAGE, SYNTHETIC_PRIVATE_LOCATION_OUTAGE and SYNTHETIC_TEST_LOCATION_SLOWDOWN
    Negate bool
    The alert triggers when the problem of specified severity arises while the specified event is happening (false) or while the specified event is not happening (true). For example, if you chose the Slowdown (PERFORMANCE) severity and Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event with negate set to true, the alerting profile will trigger only when the slowdown problem is raised while there is no unexpected high traffic event. Consider the following use case as an example. The Slowdown (PERFORMANCE) severity rule is set. Depending on the configuration of the event filter (Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event is used as an example), the options of the alerting profile is one of the following:* **negate** is set to false: The alert triggers when the slowdown problem is raised while unexpected high traffic event is happening. * **negate** is set to true: The alert triggers when the slowdown problem is raised while there is no unexpected high traffic event. * no event rule is set: The alert triggers when the slowdown problem is raised, regardless of any events
    type String
    The type of the predefined event. Possible values are APPLICATION_ERROR_RATE_INCREASED, APPLICATION_SLOWDOWN, APPLICATION_UNEXPECTED_HIGH_LOAD, APPLICATION_UNEXPECTED_LOW_LOAD, AWS_LAMBDA_HIGH_ERROR_RATE, CUSTOM_APPLICATION_ERROR_RATE_INCREASED, CUSTOM_APPLICATION_SLOWDOWN, CUSTOM_APPLICATION_UNEXPECTED_HIGH_LOAD, CUSTOM_APPLICATION_UNEXPECTED_LOW_LOAD, CUSTOM_APP_CRASH_RATE_INCREASED, DATABASE_CONNECTION_FAILURE, DATA_CENTER_SERVICE_PERFORMANCE_DEGRADATION, DATA_CENTER_SERVICE_UNAVAILABLE, EBS_VOLUME_HIGH_LATENCY, EC2_HIGH_CPU, ELB_HIGH_BACKEND_ERROR_RATE, ENTERPRICE_APPLICATION_PERFORMANCE_DEGRADATION, ENTERPRISE_APPLICATION_UNAVAILABLE, ESXI_GUEST_ACTIVE_SWAP_WAIT, ESXI_GUEST_CPU_LIMIT_REACHED, ESXI_HOST_CPU_SATURATION, ESXI_HOST_DATASTORE_LOW_DISK_SPACE, ESXI_HOST_DISK_QUEUE_SLOW, ESXI_HOST_DISK_SLOW, ESXI_HOST_MEMORY_SATURATION, ESXI_HOST_NETWORK_PROBLEMS, ESXI_HOST_OVERLOADED_STORAGE, ESXI_VM_IMPACT_HOST_CPU_SATURATION, ESXI_VM_IMPACT_HOST_MEMORY_SATURATION, EXTERNAL_SYNTHETIC_TEST_OUTAGE, EXTERNAL_SYNTHETIC_TEST_SLOWDOWN, HOST_OF_SERVICE_UNAVAILABLE, HTTP_CHECK_GLOBAL_OUTAGE, HTTP_CHECK_LOCAL_OUTAGE, HTTP_CHECK_TEST_LOCATION_SLOWDOWN, MOBILE_APPLICATION_ERROR_RATE_INCREASED, MOBILE_APPLICATION_SLOWDOWN, MOBILE_APPLICATION_UNEXPECTED_HIGH_LOAD, MOBILE_APPLICATION_UNEXPECTED_LOW_LOAD, MOBILE_APP_CRASH_RATE_INCREASED, MONITORING_UNAVAILABLE, OSI_DISK_LOW_INODES, OSI_GRACEFULLY_SHUTDOWN, OSI_HIGH_CPU, OSI_HIGH_MEMORY, OSI_LOW_DISK_SPACE, OSI_NIC_DROPPED_PACKETS_HIGH, OSI_NIC_ERRORS_HIGH, OSI_NIC_UTILIZATION_HIGH, OSI_SLOW_DISK, OSI_UNEXPECTEDLY_UNAVAILABLE, PGI_OF_SERVICE_UNAVAILABLE, PGI_UNAVAILABLE, PG_LOW_INSTANCE_COUNT, PROCESS_CRASHED, PROCESS_HIGH_GC_ACTIVITY, PROCESS_MEMORY_RESOURCE_EXHAUSTED, PROCESS_NA_HIGH_CONN_FAIL_RATE, PROCESS_NA_HIGH_LOSS_RATE, PROCESS_THREADS_RESOURCE_EXHAUSTED, RDS_HIGH_CPU, RDS_HIGH_LATENCY, RDS_LOW_MEMORY, RDS_LOW_STORAGE_SPACE, RDS_OF_SERVICE_UNAVAILABLE, RDS_RESTART_SEQUENCE, SERVICE_ERROR_RATE_INCREASED, SERVICE_SLOWDOWN, SERVICE_UNEXPECTED_HIGH_LOAD, SERVICE_UNEXPECTED_LOW_LOAD, SYNTHETIC_GLOBAL_OUTAGE, SYNTHETIC_LOCAL_OUTAGE, SYNTHETIC_NODE_OUTAGE, SYNTHETIC_PRIVATE_LOCATION_OUTAGE and SYNTHETIC_TEST_LOCATION_SLOWDOWN
    negate Boolean
    The alert triggers when the problem of specified severity arises while the specified event is happening (false) or while the specified event is not happening (true). For example, if you chose the Slowdown (PERFORMANCE) severity and Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event with negate set to true, the alerting profile will trigger only when the slowdown problem is raised while there is no unexpected high traffic event. Consider the following use case as an example. The Slowdown (PERFORMANCE) severity rule is set. Depending on the configuration of the event filter (Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event is used as an example), the options of the alerting profile is one of the following:* **negate** is set to false: The alert triggers when the slowdown problem is raised while unexpected high traffic event is happening. * **negate** is set to true: The alert triggers when the slowdown problem is raised while there is no unexpected high traffic event. * no event rule is set: The alert triggers when the slowdown problem is raised, regardless of any events
    type string
    The type of the predefined event. Possible values are APPLICATION_ERROR_RATE_INCREASED, APPLICATION_SLOWDOWN, APPLICATION_UNEXPECTED_HIGH_LOAD, APPLICATION_UNEXPECTED_LOW_LOAD, AWS_LAMBDA_HIGH_ERROR_RATE, CUSTOM_APPLICATION_ERROR_RATE_INCREASED, CUSTOM_APPLICATION_SLOWDOWN, CUSTOM_APPLICATION_UNEXPECTED_HIGH_LOAD, CUSTOM_APPLICATION_UNEXPECTED_LOW_LOAD, CUSTOM_APP_CRASH_RATE_INCREASED, DATABASE_CONNECTION_FAILURE, DATA_CENTER_SERVICE_PERFORMANCE_DEGRADATION, DATA_CENTER_SERVICE_UNAVAILABLE, EBS_VOLUME_HIGH_LATENCY, EC2_HIGH_CPU, ELB_HIGH_BACKEND_ERROR_RATE, ENTERPRICE_APPLICATION_PERFORMANCE_DEGRADATION, ENTERPRISE_APPLICATION_UNAVAILABLE, ESXI_GUEST_ACTIVE_SWAP_WAIT, ESXI_GUEST_CPU_LIMIT_REACHED, ESXI_HOST_CPU_SATURATION, ESXI_HOST_DATASTORE_LOW_DISK_SPACE, ESXI_HOST_DISK_QUEUE_SLOW, ESXI_HOST_DISK_SLOW, ESXI_HOST_MEMORY_SATURATION, ESXI_HOST_NETWORK_PROBLEMS, ESXI_HOST_OVERLOADED_STORAGE, ESXI_VM_IMPACT_HOST_CPU_SATURATION, ESXI_VM_IMPACT_HOST_MEMORY_SATURATION, EXTERNAL_SYNTHETIC_TEST_OUTAGE, EXTERNAL_SYNTHETIC_TEST_SLOWDOWN, HOST_OF_SERVICE_UNAVAILABLE, HTTP_CHECK_GLOBAL_OUTAGE, HTTP_CHECK_LOCAL_OUTAGE, HTTP_CHECK_TEST_LOCATION_SLOWDOWN, MOBILE_APPLICATION_ERROR_RATE_INCREASED, MOBILE_APPLICATION_SLOWDOWN, MOBILE_APPLICATION_UNEXPECTED_HIGH_LOAD, MOBILE_APPLICATION_UNEXPECTED_LOW_LOAD, MOBILE_APP_CRASH_RATE_INCREASED, MONITORING_UNAVAILABLE, OSI_DISK_LOW_INODES, OSI_GRACEFULLY_SHUTDOWN, OSI_HIGH_CPU, OSI_HIGH_MEMORY, OSI_LOW_DISK_SPACE, OSI_NIC_DROPPED_PACKETS_HIGH, OSI_NIC_ERRORS_HIGH, OSI_NIC_UTILIZATION_HIGH, OSI_SLOW_DISK, OSI_UNEXPECTEDLY_UNAVAILABLE, PGI_OF_SERVICE_UNAVAILABLE, PGI_UNAVAILABLE, PG_LOW_INSTANCE_COUNT, PROCESS_CRASHED, PROCESS_HIGH_GC_ACTIVITY, PROCESS_MEMORY_RESOURCE_EXHAUSTED, PROCESS_NA_HIGH_CONN_FAIL_RATE, PROCESS_NA_HIGH_LOSS_RATE, PROCESS_THREADS_RESOURCE_EXHAUSTED, RDS_HIGH_CPU, RDS_HIGH_LATENCY, RDS_LOW_MEMORY, RDS_LOW_STORAGE_SPACE, RDS_OF_SERVICE_UNAVAILABLE, RDS_RESTART_SEQUENCE, SERVICE_ERROR_RATE_INCREASED, SERVICE_SLOWDOWN, SERVICE_UNEXPECTED_HIGH_LOAD, SERVICE_UNEXPECTED_LOW_LOAD, SYNTHETIC_GLOBAL_OUTAGE, SYNTHETIC_LOCAL_OUTAGE, SYNTHETIC_NODE_OUTAGE, SYNTHETIC_PRIVATE_LOCATION_OUTAGE and SYNTHETIC_TEST_LOCATION_SLOWDOWN
    negate boolean
    The alert triggers when the problem of specified severity arises while the specified event is happening (false) or while the specified event is not happening (true). For example, if you chose the Slowdown (PERFORMANCE) severity and Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event with negate set to true, the alerting profile will trigger only when the slowdown problem is raised while there is no unexpected high traffic event. Consider the following use case as an example. The Slowdown (PERFORMANCE) severity rule is set. Depending on the configuration of the event filter (Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event is used as an example), the options of the alerting profile is one of the following:* **negate** is set to false: The alert triggers when the slowdown problem is raised while unexpected high traffic event is happening. * **negate** is set to true: The alert triggers when the slowdown problem is raised while there is no unexpected high traffic event. * no event rule is set: The alert triggers when the slowdown problem is raised, regardless of any events
    type str
    The type of the predefined event. Possible values are APPLICATION_ERROR_RATE_INCREASED, APPLICATION_SLOWDOWN, APPLICATION_UNEXPECTED_HIGH_LOAD, APPLICATION_UNEXPECTED_LOW_LOAD, AWS_LAMBDA_HIGH_ERROR_RATE, CUSTOM_APPLICATION_ERROR_RATE_INCREASED, CUSTOM_APPLICATION_SLOWDOWN, CUSTOM_APPLICATION_UNEXPECTED_HIGH_LOAD, CUSTOM_APPLICATION_UNEXPECTED_LOW_LOAD, CUSTOM_APP_CRASH_RATE_INCREASED, DATABASE_CONNECTION_FAILURE, DATA_CENTER_SERVICE_PERFORMANCE_DEGRADATION, DATA_CENTER_SERVICE_UNAVAILABLE, EBS_VOLUME_HIGH_LATENCY, EC2_HIGH_CPU, ELB_HIGH_BACKEND_ERROR_RATE, ENTERPRICE_APPLICATION_PERFORMANCE_DEGRADATION, ENTERPRISE_APPLICATION_UNAVAILABLE, ESXI_GUEST_ACTIVE_SWAP_WAIT, ESXI_GUEST_CPU_LIMIT_REACHED, ESXI_HOST_CPU_SATURATION, ESXI_HOST_DATASTORE_LOW_DISK_SPACE, ESXI_HOST_DISK_QUEUE_SLOW, ESXI_HOST_DISK_SLOW, ESXI_HOST_MEMORY_SATURATION, ESXI_HOST_NETWORK_PROBLEMS, ESXI_HOST_OVERLOADED_STORAGE, ESXI_VM_IMPACT_HOST_CPU_SATURATION, ESXI_VM_IMPACT_HOST_MEMORY_SATURATION, EXTERNAL_SYNTHETIC_TEST_OUTAGE, EXTERNAL_SYNTHETIC_TEST_SLOWDOWN, HOST_OF_SERVICE_UNAVAILABLE, HTTP_CHECK_GLOBAL_OUTAGE, HTTP_CHECK_LOCAL_OUTAGE, HTTP_CHECK_TEST_LOCATION_SLOWDOWN, MOBILE_APPLICATION_ERROR_RATE_INCREASED, MOBILE_APPLICATION_SLOWDOWN, MOBILE_APPLICATION_UNEXPECTED_HIGH_LOAD, MOBILE_APPLICATION_UNEXPECTED_LOW_LOAD, MOBILE_APP_CRASH_RATE_INCREASED, MONITORING_UNAVAILABLE, OSI_DISK_LOW_INODES, OSI_GRACEFULLY_SHUTDOWN, OSI_HIGH_CPU, OSI_HIGH_MEMORY, OSI_LOW_DISK_SPACE, OSI_NIC_DROPPED_PACKETS_HIGH, OSI_NIC_ERRORS_HIGH, OSI_NIC_UTILIZATION_HIGH, OSI_SLOW_DISK, OSI_UNEXPECTEDLY_UNAVAILABLE, PGI_OF_SERVICE_UNAVAILABLE, PGI_UNAVAILABLE, PG_LOW_INSTANCE_COUNT, PROCESS_CRASHED, PROCESS_HIGH_GC_ACTIVITY, PROCESS_MEMORY_RESOURCE_EXHAUSTED, PROCESS_NA_HIGH_CONN_FAIL_RATE, PROCESS_NA_HIGH_LOSS_RATE, PROCESS_THREADS_RESOURCE_EXHAUSTED, RDS_HIGH_CPU, RDS_HIGH_LATENCY, RDS_LOW_MEMORY, RDS_LOW_STORAGE_SPACE, RDS_OF_SERVICE_UNAVAILABLE, RDS_RESTART_SEQUENCE, SERVICE_ERROR_RATE_INCREASED, SERVICE_SLOWDOWN, SERVICE_UNEXPECTED_HIGH_LOAD, SERVICE_UNEXPECTED_LOW_LOAD, SYNTHETIC_GLOBAL_OUTAGE, SYNTHETIC_LOCAL_OUTAGE, SYNTHETIC_NODE_OUTAGE, SYNTHETIC_PRIVATE_LOCATION_OUTAGE and SYNTHETIC_TEST_LOCATION_SLOWDOWN
    negate bool
    The alert triggers when the problem of specified severity arises while the specified event is happening (false) or while the specified event is not happening (true). For example, if you chose the Slowdown (PERFORMANCE) severity and Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event with negate set to true, the alerting profile will trigger only when the slowdown problem is raised while there is no unexpected high traffic event. Consider the following use case as an example. The Slowdown (PERFORMANCE) severity rule is set. Depending on the configuration of the event filter (Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event is used as an example), the options of the alerting profile is one of the following:* **negate** is set to false: The alert triggers when the slowdown problem is raised while unexpected high traffic event is happening. * **negate** is set to true: The alert triggers when the slowdown problem is raised while there is no unexpected high traffic event. * no event rule is set: The alert triggers when the slowdown problem is raised, regardless of any events
    type String
    The type of the predefined event. Possible values are APPLICATION_ERROR_RATE_INCREASED, APPLICATION_SLOWDOWN, APPLICATION_UNEXPECTED_HIGH_LOAD, APPLICATION_UNEXPECTED_LOW_LOAD, AWS_LAMBDA_HIGH_ERROR_RATE, CUSTOM_APPLICATION_ERROR_RATE_INCREASED, CUSTOM_APPLICATION_SLOWDOWN, CUSTOM_APPLICATION_UNEXPECTED_HIGH_LOAD, CUSTOM_APPLICATION_UNEXPECTED_LOW_LOAD, CUSTOM_APP_CRASH_RATE_INCREASED, DATABASE_CONNECTION_FAILURE, DATA_CENTER_SERVICE_PERFORMANCE_DEGRADATION, DATA_CENTER_SERVICE_UNAVAILABLE, EBS_VOLUME_HIGH_LATENCY, EC2_HIGH_CPU, ELB_HIGH_BACKEND_ERROR_RATE, ENTERPRICE_APPLICATION_PERFORMANCE_DEGRADATION, ENTERPRISE_APPLICATION_UNAVAILABLE, ESXI_GUEST_ACTIVE_SWAP_WAIT, ESXI_GUEST_CPU_LIMIT_REACHED, ESXI_HOST_CPU_SATURATION, ESXI_HOST_DATASTORE_LOW_DISK_SPACE, ESXI_HOST_DISK_QUEUE_SLOW, ESXI_HOST_DISK_SLOW, ESXI_HOST_MEMORY_SATURATION, ESXI_HOST_NETWORK_PROBLEMS, ESXI_HOST_OVERLOADED_STORAGE, ESXI_VM_IMPACT_HOST_CPU_SATURATION, ESXI_VM_IMPACT_HOST_MEMORY_SATURATION, EXTERNAL_SYNTHETIC_TEST_OUTAGE, EXTERNAL_SYNTHETIC_TEST_SLOWDOWN, HOST_OF_SERVICE_UNAVAILABLE, HTTP_CHECK_GLOBAL_OUTAGE, HTTP_CHECK_LOCAL_OUTAGE, HTTP_CHECK_TEST_LOCATION_SLOWDOWN, MOBILE_APPLICATION_ERROR_RATE_INCREASED, MOBILE_APPLICATION_SLOWDOWN, MOBILE_APPLICATION_UNEXPECTED_HIGH_LOAD, MOBILE_APPLICATION_UNEXPECTED_LOW_LOAD, MOBILE_APP_CRASH_RATE_INCREASED, MONITORING_UNAVAILABLE, OSI_DISK_LOW_INODES, OSI_GRACEFULLY_SHUTDOWN, OSI_HIGH_CPU, OSI_HIGH_MEMORY, OSI_LOW_DISK_SPACE, OSI_NIC_DROPPED_PACKETS_HIGH, OSI_NIC_ERRORS_HIGH, OSI_NIC_UTILIZATION_HIGH, OSI_SLOW_DISK, OSI_UNEXPECTEDLY_UNAVAILABLE, PGI_OF_SERVICE_UNAVAILABLE, PGI_UNAVAILABLE, PG_LOW_INSTANCE_COUNT, PROCESS_CRASHED, PROCESS_HIGH_GC_ACTIVITY, PROCESS_MEMORY_RESOURCE_EXHAUSTED, PROCESS_NA_HIGH_CONN_FAIL_RATE, PROCESS_NA_HIGH_LOSS_RATE, PROCESS_THREADS_RESOURCE_EXHAUSTED, RDS_HIGH_CPU, RDS_HIGH_LATENCY, RDS_LOW_MEMORY, RDS_LOW_STORAGE_SPACE, RDS_OF_SERVICE_UNAVAILABLE, RDS_RESTART_SEQUENCE, SERVICE_ERROR_RATE_INCREASED, SERVICE_SLOWDOWN, SERVICE_UNEXPECTED_HIGH_LOAD, SERVICE_UNEXPECTED_LOW_LOAD, SYNTHETIC_GLOBAL_OUTAGE, SYNTHETIC_LOCAL_OUTAGE, SYNTHETIC_NODE_OUTAGE, SYNTHETIC_PRIVATE_LOCATION_OUTAGE and SYNTHETIC_TEST_LOCATION_SLOWDOWN
    negate Boolean
    The alert triggers when the problem of specified severity arises while the specified event is happening (false) or while the specified event is not happening (true). For example, if you chose the Slowdown (PERFORMANCE) severity and Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event with negate set to true, the alerting profile will trigger only when the slowdown problem is raised while there is no unexpected high traffic event. Consider the following use case as an example. The Slowdown (PERFORMANCE) severity rule is set. Depending on the configuration of the event filter (Unexpected high traffic (APPLICATION_UNEXPECTED_HIGH_LOAD) event is used as an example), the options of the alerting profile is one of the following:* **negate** is set to false: The alert triggers when the slowdown problem is raised while unexpected high traffic event is happening. * **negate** is set to true: The alert triggers when the slowdown problem is raised while there is no unexpected high traffic event. * no event rule is set: The alert triggers when the slowdown problem is raised, regardless of any events

    AlertingRules, AlertingRulesArgs

    Rules []AlertingRulesRule
    A conditions for the metric usage
    rules List<AlertingRulesRule>
    A conditions for the metric usage
    rules AlertingRulesRule[]
    A conditions for the metric usage
    rules Sequence[AlertingRulesRule]
    A conditions for the metric usage
    rules List<Property Map>
    A conditions for the metric usage

    AlertingRulesRule, AlertingRulesRuleArgs

    DelayInMinutes int
    Send a notification if a problem remains open longer than X minutes
    IncludeMode string
    The filtering mode: * INCLUDE_ANY: The rule applies to monitored entities that have at least one of the specified tags. You can specify up to 100 tags. * INCLUDE_ALL: The rule applies to monitored entities that have all of the specified tags. You can specify up to 10 tags. * NONE: The rule applies to all monitored entities
    SeverityLevel string
    The severity level to trigger the alert. Possible values are AVAILABILITY, CUSTOM_ALERT, ERRORS,MONITORING_UNAVAILABLE,PERFORMANCE and RESOURCE_CONTENTION.
    Tags List<string>
    Entities which contain any/all of the configured tags will match this alerting profile. It is recommended to use manual tags.
    DelayInMinutes int
    Send a notification if a problem remains open longer than X minutes
    IncludeMode string
    The filtering mode: * INCLUDE_ANY: The rule applies to monitored entities that have at least one of the specified tags. You can specify up to 100 tags. * INCLUDE_ALL: The rule applies to monitored entities that have all of the specified tags. You can specify up to 10 tags. * NONE: The rule applies to all monitored entities
    SeverityLevel string
    The severity level to trigger the alert. Possible values are AVAILABILITY, CUSTOM_ALERT, ERRORS,MONITORING_UNAVAILABLE,PERFORMANCE and RESOURCE_CONTENTION.
    Tags []string
    Entities which contain any/all of the configured tags will match this alerting profile. It is recommended to use manual tags.
    delayInMinutes Integer
    Send a notification if a problem remains open longer than X minutes
    includeMode String
    The filtering mode: * INCLUDE_ANY: The rule applies to monitored entities that have at least one of the specified tags. You can specify up to 100 tags. * INCLUDE_ALL: The rule applies to monitored entities that have all of the specified tags. You can specify up to 10 tags. * NONE: The rule applies to all monitored entities
    severityLevel String
    The severity level to trigger the alert. Possible values are AVAILABILITY, CUSTOM_ALERT, ERRORS,MONITORING_UNAVAILABLE,PERFORMANCE and RESOURCE_CONTENTION.
    tags List<String>
    Entities which contain any/all of the configured tags will match this alerting profile. It is recommended to use manual tags.
    delayInMinutes number
    Send a notification if a problem remains open longer than X minutes
    includeMode string
    The filtering mode: * INCLUDE_ANY: The rule applies to monitored entities that have at least one of the specified tags. You can specify up to 100 tags. * INCLUDE_ALL: The rule applies to monitored entities that have all of the specified tags. You can specify up to 10 tags. * NONE: The rule applies to all monitored entities
    severityLevel string
    The severity level to trigger the alert. Possible values are AVAILABILITY, CUSTOM_ALERT, ERRORS,MONITORING_UNAVAILABLE,PERFORMANCE and RESOURCE_CONTENTION.
    tags string[]
    Entities which contain any/all of the configured tags will match this alerting profile. It is recommended to use manual tags.
    delay_in_minutes int
    Send a notification if a problem remains open longer than X minutes
    include_mode str
    The filtering mode: * INCLUDE_ANY: The rule applies to monitored entities that have at least one of the specified tags. You can specify up to 100 tags. * INCLUDE_ALL: The rule applies to monitored entities that have all of the specified tags. You can specify up to 10 tags. * NONE: The rule applies to all monitored entities
    severity_level str
    The severity level to trigger the alert. Possible values are AVAILABILITY, CUSTOM_ALERT, ERRORS,MONITORING_UNAVAILABLE,PERFORMANCE and RESOURCE_CONTENTION.
    tags Sequence[str]
    Entities which contain any/all of the configured tags will match this alerting profile. It is recommended to use manual tags.
    delayInMinutes Number
    Send a notification if a problem remains open longer than X minutes
    includeMode String
    The filtering mode: * INCLUDE_ANY: The rule applies to monitored entities that have at least one of the specified tags. You can specify up to 100 tags. * INCLUDE_ALL: The rule applies to monitored entities that have all of the specified tags. You can specify up to 10 tags. * NONE: The rule applies to all monitored entities
    severityLevel String
    The severity level to trigger the alert. Possible values are AVAILABILITY, CUSTOM_ALERT, ERRORS,MONITORING_UNAVAILABLE,PERFORMANCE and RESOURCE_CONTENTION.
    tags List<String>
    Entities which contain any/all of the configured tags will match this alerting profile. It is recommended to use manual tags.

    Package Details

    Repository
    dynatrace pulumiverse/pulumi-dynatrace
    License
    Apache-2.0
    Notes
    This Pulumi package is based on the dynatrace Terraform Provider.
    dynatrace logo
    Dynatrace v0.21.0 published on Sunday, Nov 17, 2024 by Pulumiverse
    lbrlabs/pulumi-dynatrace