@lbrlabs/pulumi-dynatrace/alertingProfile.d.ts

A Pulumi package for creating and managing Dynatrace cloud resources.

import * as pulumi from "@pulumi/pulumi";
import * as inputs from "./types/input";
import * as outputs from "./types/output";
export declare class AlertingProfile extends pulumi.CustomResource {
    /**
     * Get an existing AlertingProfile resource's state with the given name, ID, and optional extra
     * properties used to qualify the lookup.
     *
     * @param name The _unique_ name of the resulting resource.
     * @param id The _unique_ provider ID of the resource to lookup.
     * @param state Any extra arguments used during the lookup.
     * @param opts Optional settings to control the behavior of the CustomResource.
     */
    static get(name: string, id: pulumi.Input<pulumi.ID>, state?: AlertingProfileState, opts?: pulumi.CustomResourceOptions): AlertingProfile;
    /**
     * Returns true if the given object is an instance of AlertingProfile.  This is designed to work even
     * when multiple copies of the Pulumi SDK have been loaded into the same process.
     */
    static isInstance(obj: any): obj is AlertingProfile;
    /**
     * The name of the alerting profile, displayed in the UI
     */
    readonly displayName: pulumi.Output<string>;
    /**
     * 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
     */
    readonly eventTypeFilters: pulumi.Output<outputs.AlertingProfileEventTypeFilter[] | undefined>;
    /**
     * `metadata` exists for backwards compatibility but shouldn't get specified anymore
     *
     * @deprecated `metadata` exists for backwards compatibility but shouldn't get specified anymore
     */
    readonly metadata: pulumi.Output<outputs.AlertingProfileMetadata | undefined>;
    /**
     * The ID of the management zone to which the alerting profile applies
     */
    readonly mzId: pulumi.Output<string | undefined>;
    /**
     * A list of rules for management zone usage.  Each rule is evaluated independently of all other rules
     */
    readonly rules: pulumi.Output<outputs.AlertingProfileRule[] | undefined>;
    /**
     * allows for configuring properties that are not explicitly supported by the current version of this provider
     */
    readonly unknowns: pulumi.Output<string | undefined>;
    /**
     * Create a AlertingProfile resource with the given unique name, arguments, and options.
     *
     * @param name The _unique_ name of the resource.
     * @param args The arguments to use to populate this resource's properties.
     * @param opts A bag of options that control this resource's behavior.
     */
    constructor(name: string, args: AlertingProfileArgs, opts?: pulumi.CustomResourceOptions);
}
/**
 * Input properties used for looking up and filtering AlertingProfile resources.
 */
export interface AlertingProfileState {
    /**
     * The name of the alerting profile, displayed in the UI
     */
    displayName?: pulumi.Input<string>;
    /**
     * 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
     */
    eventTypeFilters?: pulumi.Input<pulumi.Input<inputs.AlertingProfileEventTypeFilter>[]>;
    /**
     * `metadata` exists for backwards compatibility but shouldn't get specified anymore
     *
     * @deprecated `metadata` exists for backwards compatibility but shouldn't get specified anymore
     */
    metadata?: pulumi.Input<inputs.AlertingProfileMetadata>;
    /**
     * The ID of the management zone to which the alerting profile applies
     */
    mzId?: pulumi.Input<string>;
    /**
     * A list of rules for management zone usage.  Each rule is evaluated independently of all other rules
     */
    rules?: pulumi.Input<pulumi.Input<inputs.AlertingProfileRule>[]>;
    /**
     * allows for configuring properties that are not explicitly supported by the current version of this provider
     */
    unknowns?: pulumi.Input<string>;
}
/**
 * The set of arguments for constructing a AlertingProfile resource.
 */
export interface AlertingProfileArgs {
    /**
     * The name of the alerting profile, displayed in the UI
     */
    displayName: pulumi.Input<string>;
    /**
     * 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
     */
    eventTypeFilters?: pulumi.Input<pulumi.Input<inputs.AlertingProfileEventTypeFilter>[]>;
    /**
     * `metadata` exists for backwards compatibility but shouldn't get specified anymore
     *
     * @deprecated `metadata` exists for backwards compatibility but shouldn't get specified anymore
     */
    metadata?: pulumi.Input<inputs.AlertingProfileMetadata>;
    /**
     * The ID of the management zone to which the alerting profile applies
     */
    mzId?: pulumi.Input<string>;
    /**
     * A list of rules for management zone usage.  Each rule is evaluated independently of all other rules
     */
    rules?: pulumi.Input<pulumi.Input<inputs.AlertingProfileRule>[]>;
    /**
     * allows for configuring properties that are not explicitly supported by the current version of this provider
     */
    unknowns?: pulumi.Input<string>;
}