import * as pulumi from "@pulumi/pulumi";
import * as inputs from "./types/input";
import * as outputs from "./types/output";
export declare class Alerting extends pulumi.CustomResource {
    /**
     * Get an existing Alerting 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?: AlertingState, opts?: pulumi.CustomResourceOptions): Alerting;
    /**
     * Returns true if the given object is an instance of Alerting.  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 Alerting;
    /**
     * 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 filters: pulumi.Output<outputs.AlertingFilters | undefined>;
    /**
     * The ID of this setting when referred to by the Config REST API V1
     */
    readonly legacyId: pulumi.Output<string>;
    /**
     * Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
     */
    readonly managementZone: pulumi.Output<string | undefined>;
    /**
     * The name of the alerting profile, displayed in the UI
     */
    readonly name: pulumi.Output<string>;
    /**
     * A list of rules for management zone usage.  Each rule is evaluated independently of all other rules
     */
    readonly rules: pulumi.Output<outputs.AlertingRules | undefined>;
    /**
     * Create a Alerting 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?: AlertingArgs, opts?: pulumi.CustomResourceOptions);
}
/**
 * Input properties used for looking up and filtering Alerting resources.
 */
export interface AlertingState {
    /**
     * 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
     */
    filters?: pulumi.Input<inputs.AlertingFilters>;
    /**
     * The ID of this setting when referred to by the Config REST API V1
     */
    legacyId?: pulumi.Input<string>;
    /**
     * Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
     */
    managementZone?: pulumi.Input<string>;
    /**
     * The name of the alerting profile, displayed in the UI
     */
    name?: pulumi.Input<string>;
    /**
     * A list of rules for management zone usage.  Each rule is evaluated independently of all other rules
     */
    rules?: pulumi.Input<inputs.AlertingRules>;
}
/**
 * The set of arguments for constructing a Alerting resource.
 */
export interface AlertingArgs {
    /**
     * 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
     */
    filters?: pulumi.Input<inputs.AlertingFilters>;
    /**
     * The ID of this setting when referred to by the Config REST API V1
     */
    legacyId?: pulumi.Input<string>;
    /**
     * Entities which are part of the configured management zones will match this alerting profile. It is recommended to use manual tags instead.
     */
    managementZone?: pulumi.Input<string>;
    /**
     * The name of the alerting profile, displayed in the UI
     */
    name?: pulumi.Input<string>;
    /**
     * A list of rules for management zone usage.  Each rule is evaluated independently of all other rules
     */
    rules?: pulumi.Input<inputs.AlertingRules>;
}