Dynatrace v0.1.0, May 24 23

dynatrace.EmailNotification

Explore with Pulumi AI

Create EmailNotification Resource

new EmailNotification(name: string, args: EmailNotificationArgs, opts?: CustomResourceOptions);

@overload
def EmailNotification(resource_name: str,
                      opts: Optional[ResourceOptions] = None,
                      active: Optional[bool] = None,
                      bccs: Optional[Sequence[str]] = None,
                      body: Optional[str] = None,
                      ccs: Optional[Sequence[str]] = None,
                      legacy_id: Optional[str] = None,
                      name: Optional[str] = None,
                      notify_closed_problems: Optional[bool] = None,
                      profile: Optional[str] = None,
                      subject: Optional[str] = None,
                      tos: Optional[Sequence[str]] = None)
@overload
def EmailNotification(resource_name: str,
                      args: EmailNotificationArgs,
                      opts: Optional[ResourceOptions] = None)

func NewEmailNotification(ctx *Context, name string, args EmailNotificationArgs, opts ...ResourceOption) (*EmailNotification, error)

public EmailNotification(string name, EmailNotificationArgs args, CustomResourceOptions? opts = null)

public EmailNotification(String name, EmailNotificationArgs args)
public EmailNotification(String name, EmailNotificationArgs args, CustomResourceOptions options)

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

name string: The unique name of the resource.
args EmailNotificationArgs: 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 EmailNotificationArgs: 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 EmailNotificationArgs: The arguments to resource properties.
opts ResourceOption: Bag of options to control resource's behavior.

name string: The unique name of the resource.
args EmailNotificationArgs: The arguments to resource properties.
opts CustomResourceOptions: Bag of options to control resource's behavior.

name String: The unique name of the resource.
args EmailNotificationArgs: The arguments to resource properties.
options CustomResourceOptions: Bag of options to control resource's behavior.

EmailNotification Resource Properties

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

Inputs

The EmailNotification resource accepts the following input properties:

Body string: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
Profile string: The ID of the associated alerting profile
Subject string: The subject of the email notifications
Tos List<string>: The list of the email recipients
Active bool: The configuration is enabled (true) or disabled (false)
Bccs List<string>: The list of the email BCC-recipients
Ccs List<string>: The list of the email CC-recipients
LegacyId string: The ID of these settings when referred to from resources requiring the REST API V1 keys
Name string: The name of the notification configuration
NotifyClosedProblems bool: Send email if problem is closed

Body string: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
Profile string: The ID of the associated alerting profile
Subject string: The subject of the email notifications
Tos []string: The list of the email recipients
Active bool: The configuration is enabled (true) or disabled (false)
Bccs []string: The list of the email BCC-recipients
Ccs []string: The list of the email CC-recipients
LegacyId string: The ID of these settings when referred to from resources requiring the REST API V1 keys
Name string: The name of the notification configuration
NotifyClosedProblems bool: Send email if problem is closed

body String: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
profile String: The ID of the associated alerting profile
subject String: The subject of the email notifications
tos List<String>: The list of the email recipients
active Boolean: The configuration is enabled (true) or disabled (false)
bccs List<String>: The list of the email BCC-recipients
ccs List<String>: The list of the email CC-recipients
legacyId String: The ID of these settings when referred to from resources requiring the REST API V1 keys
name String: The name of the notification configuration
notifyClosedProblems Boolean: Send email if problem is closed

body string: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
profile string: The ID of the associated alerting profile
subject string: The subject of the email notifications
tos string[]: The list of the email recipients
active boolean: The configuration is enabled (true) or disabled (false)
bccs string[]: The list of the email BCC-recipients
ccs string[]: The list of the email CC-recipients
legacyId string: The ID of these settings when referred to from resources requiring the REST API V1 keys
name string: The name of the notification configuration
notifyClosedProblems boolean: Send email if problem is closed

body str: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
profile str: The ID of the associated alerting profile
subject str: The subject of the email notifications
tos Sequence[str]: The list of the email recipients
active bool: The configuration is enabled (true) or disabled (false)
bccs Sequence[str]: The list of the email BCC-recipients
ccs Sequence[str]: The list of the email CC-recipients
legacy_id str: The ID of these settings when referred to from resources requiring the REST API V1 keys
name str: The name of the notification configuration
notify_closed_problems bool: Send email if problem is closed

body String: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
profile String: The ID of the associated alerting profile
subject String: The subject of the email notifications
tos List<String>: The list of the email recipients
active Boolean: The configuration is enabled (true) or disabled (false)
bccs List<String>: The list of the email BCC-recipients
ccs List<String>: The list of the email CC-recipients
legacyId String: The ID of these settings when referred to from resources requiring the REST API V1 keys
name String: The name of the notification configuration
notifyClosedProblems Boolean: Send email if problem is closed

Outputs

All input properties are implicitly available as output properties. Additionally, the EmailNotification 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 EmailNotification Resource

Get an existing EmailNotification 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?: EmailNotificationState, opts?: CustomResourceOptions): EmailNotification

@staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        active: Optional[bool] = None,
        bccs: Optional[Sequence[str]] = None,
        body: Optional[str] = None,
        ccs: Optional[Sequence[str]] = None,
        legacy_id: Optional[str] = None,
        name: Optional[str] = None,
        notify_closed_problems: Optional[bool] = None,
        profile: Optional[str] = None,
        subject: Optional[str] = None,
        tos: Optional[Sequence[str]] = None) -> EmailNotification

func GetEmailNotification(ctx *Context, name string, id IDInput, state *EmailNotificationState, opts ...ResourceOption) (*EmailNotification, error)

public static EmailNotification Get(string name, Input<string> id, EmailNotificationState? state, CustomResourceOptions? opts = null)

public static EmailNotification get(String name, Output<String> id, EmailNotificationState 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:

Active bool: The configuration is enabled (true) or disabled (false)
Bccs List<string>: The list of the email BCC-recipients
Body string: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
Ccs List<string>: The list of the email CC-recipients
LegacyId string: The ID of these settings when referred to from resources requiring the REST API V1 keys
Name string: The name of the notification configuration
NotifyClosedProblems bool: Send email if problem is closed
Profile string: The ID of the associated alerting profile
Subject string: The subject of the email notifications
Tos List<string>: The list of the email recipients

Active bool: The configuration is enabled (true) or disabled (false)
Bccs []string: The list of the email BCC-recipients
Body string: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
Ccs []string: The list of the email CC-recipients
LegacyId string: The ID of these settings when referred to from resources requiring the REST API V1 keys
Name string: The name of the notification configuration
NotifyClosedProblems bool: Send email if problem is closed
Profile string: The ID of the associated alerting profile
Subject string: The subject of the email notifications
Tos []string: The list of the email recipients

active Boolean: The configuration is enabled (true) or disabled (false)
bccs List<String>: The list of the email BCC-recipients
body String: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
ccs List<String>: The list of the email CC-recipients
legacyId String: The ID of these settings when referred to from resources requiring the REST API V1 keys
name String: The name of the notification configuration
notifyClosedProblems Boolean: Send email if problem is closed
profile String: The ID of the associated alerting profile
subject String: The subject of the email notifications
tos List<String>: The list of the email recipients

active boolean: The configuration is enabled (true) or disabled (false)
bccs string[]: The list of the email BCC-recipients
body string: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
ccs string[]: The list of the email CC-recipients
legacyId string: The ID of these settings when referred to from resources requiring the REST API V1 keys
name string: The name of the notification configuration
notifyClosedProblems boolean: Send email if problem is closed
profile string: The ID of the associated alerting profile
subject string: The subject of the email notifications
tos string[]: The list of the email recipients

active bool: The configuration is enabled (true) or disabled (false)
bccs Sequence[str]: The list of the email BCC-recipients
body str: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
ccs Sequence[str]: The list of the email CC-recipients
legacy_id str: The ID of these settings when referred to from resources requiring the REST API V1 keys
name str: The name of the notification configuration
notify_closed_problems bool: Send email if problem is closed
profile str: The ID of the associated alerting profile
subject str: The subject of the email notifications
tos Sequence[str]: The list of the email recipients

active Boolean: The configuration is enabled (true) or disabled (false)
bccs List<String>: The list of the email BCC-recipients
body String: The template of the email notification. You can use the following placeholders: * {ImpactedEntities}: Details about the entities impacted by the problem in form of a JSON array. * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsHTML}: All problem event details, including root cause, as an HTML-formatted string. * {ProblemDetailsJSON}: All problem event details, including root cause, as a JSON object. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-formatted string. * {ProblemDetailsText}: All problem event details, including root cause, as a text-formatted string. * {ProblemID}: The display number of the reported problem. * {ProblemImpact}: The impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, and CUSTOM_ALERT. * {ProblemTitle}: A short description of the problem. * {ProblemURL}: The URL of the problem within Dynatrace. * {State}: The state of the problem. Possible values are OPEN and RESOLVED. * {Tags}: The list of tags that are defined for all impacted entities, separated by commas
ccs List<String>: The list of the email CC-recipients
legacyId String: The ID of these settings when referred to from resources requiring the REST API V1 keys
name String: The name of the notification configuration
notifyClosedProblems Boolean: Send email if problem is closed
profile String: The ID of the associated alerting profile
subject String: The subject of the email notifications
tos List<String>: The list of the email recipients

Package Details

Repository: dynatrace lbrlabs/pulumi-dynatrace
License: Apache-2.0
Notes: This Pulumi package is based on the dynatrace Terraform Provider.