Dynatrace v0.0.2, Nov 1 22

dynatrace.Notification

Create Notification Resource

new Notification(name: string, args?: NotificationArgs, opts?: CustomResourceOptions);

@overload
def Notification(resource_name: str,
                 opts: Optional[ResourceOptions] = None,
                 ansible_tower: Optional[NotificationAnsibleTowerArgs] = None,
                 config: Optional[NotificationConfigArgs] = None,
                 email: Optional[NotificationEmailArgs] = None,
                 hipchat: Optional[NotificationHipchatArgs] = None,
                 jira: Optional[NotificationJiraArgs] = None,
                 ops_genie: Optional[NotificationOpsGenieArgs] = None,
                 pager_duty: Optional[NotificationPagerDutyArgs] = None,
                 service_now: Optional[NotificationServiceNowArgs] = None,
                 slack: Optional[NotificationSlackArgs] = None,
                 trello: Optional[NotificationTrelloArgs] = None,
                 victor_ops: Optional[NotificationVictorOpsArgs] = None,
                 web_hook: Optional[NotificationWebHookArgs] = None,
                 xmatters: Optional[NotificationXmattersArgs] = None)
@overload
def Notification(resource_name: str,
                 args: Optional[NotificationArgs] = None,
                 opts: Optional[ResourceOptions] = None)

func NewNotification(ctx *Context, name string, args *NotificationArgs, opts ...ResourceOption) (*Notification, error)

public Notification(string name, NotificationArgs? args = null, CustomResourceOptions? opts = null)

public Notification(String name, NotificationArgs args)
public Notification(String name, NotificationArgs args, CustomResourceOptions options)

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

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

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

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

Notification 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 Notification resource accepts the following input properties:

AnsibleTower Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
Config Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationConfigArgs: Configuration for Generic Notification
Email Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationEmailArgs: Configuration for Email Notification
Hipchat Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationHipchatArgs: Configuration for HipChat Notification
Jira Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationJiraArgs: Configuration for Jira Notification
OpsGenie Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationOpsGenieArgs: Configuration for OpsGenie Notification
PagerDuty Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationPagerDutyArgs: Configuration for PagerDuty Notification
ServiceNow Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationServiceNowArgs: Configuration for ServiceNow Notification
Slack Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationSlackArgs: Configuration for Slack Notification
Trello Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationTrelloArgs: Configuration for Trello Notification
VictorOps Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationVictorOpsArgs: Configuration for VictorOps Notification
WebHook Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationWebHookArgs: Configuration for WebHook Notification
Xmatters Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationXmattersArgs: Configuration for XMatters Notification

AnsibleTower NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
Config NotificationConfigArgs: Configuration for Generic Notification
Email NotificationEmailArgs: Configuration for Email Notification
Hipchat NotificationHipchatArgs: Configuration for HipChat Notification
Jira NotificationJiraArgs: Configuration for Jira Notification
OpsGenie NotificationOpsGenieArgs: Configuration for OpsGenie Notification
PagerDuty NotificationPagerDutyArgs: Configuration for PagerDuty Notification
ServiceNow NotificationServiceNowArgs: Configuration for ServiceNow Notification
Slack NotificationSlackArgs: Configuration for Slack Notification
Trello NotificationTrelloArgs: Configuration for Trello Notification
VictorOps NotificationVictorOpsArgs: Configuration for VictorOps Notification
WebHook NotificationWebHookArgs: Configuration for WebHook Notification
Xmatters NotificationXmattersArgs: Configuration for XMatters Notification

ansibleTower NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
config NotificationConfigArgs: Configuration for Generic Notification
email NotificationEmailArgs: Configuration for Email Notification
hipchat NotificationHipchatArgs: Configuration for HipChat Notification
jira NotificationJiraArgs: Configuration for Jira Notification
opsGenie NotificationOpsGenieArgs: Configuration for OpsGenie Notification
pagerDuty NotificationPagerDutyArgs: Configuration for PagerDuty Notification
serviceNow NotificationServiceNowArgs: Configuration for ServiceNow Notification
slack NotificationSlackArgs: Configuration for Slack Notification
trello NotificationTrelloArgs: Configuration for Trello Notification
victorOps NotificationVictorOpsArgs: Configuration for VictorOps Notification
webHook NotificationWebHookArgs: Configuration for WebHook Notification
xmatters NotificationXmattersArgs: Configuration for XMatters Notification

ansibleTower NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
config NotificationConfigArgs: Configuration for Generic Notification
email NotificationEmailArgs: Configuration for Email Notification
hipchat NotificationHipchatArgs: Configuration for HipChat Notification
jira NotificationJiraArgs: Configuration for Jira Notification
opsGenie NotificationOpsGenieArgs: Configuration for OpsGenie Notification
pagerDuty NotificationPagerDutyArgs: Configuration for PagerDuty Notification
serviceNow NotificationServiceNowArgs: Configuration for ServiceNow Notification
slack NotificationSlackArgs: Configuration for Slack Notification
trello NotificationTrelloArgs: Configuration for Trello Notification
victorOps NotificationVictorOpsArgs: Configuration for VictorOps Notification
webHook NotificationWebHookArgs: Configuration for WebHook Notification
xmatters NotificationXmattersArgs: Configuration for XMatters Notification

ansible_tower NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
config NotificationConfigArgs: Configuration for Generic Notification
email NotificationEmailArgs: Configuration for Email Notification
hipchat NotificationHipchatArgs: Configuration for HipChat Notification
jira NotificationJiraArgs: Configuration for Jira Notification
ops_genie NotificationOpsGenieArgs: Configuration for OpsGenie Notification
pager_duty NotificationPagerDutyArgs: Configuration for PagerDuty Notification
service_now NotificationServiceNowArgs: Configuration for ServiceNow Notification
slack NotificationSlackArgs: Configuration for Slack Notification
trello NotificationTrelloArgs: Configuration for Trello Notification
victor_ops NotificationVictorOpsArgs: Configuration for VictorOps Notification
web_hook NotificationWebHookArgs: Configuration for WebHook Notification
xmatters NotificationXmattersArgs: Configuration for XMatters Notification

ansibleTower Property Map: Configuration for Ansible Tower Notification
config Property Map: Configuration for Generic Notification
email Property Map: Configuration for Email Notification
hipchat Property Map: Configuration for HipChat Notification
jira Property Map: Configuration for Jira Notification
opsGenie Property Map: Configuration for OpsGenie Notification
pagerDuty Property Map: Configuration for PagerDuty Notification
serviceNow Property Map: Configuration for ServiceNow Notification
slack Property Map: Configuration for Slack Notification
trello Property Map: Configuration for Trello Notification
victorOps Property Map: Configuration for VictorOps Notification
webHook Property Map: Configuration for WebHook Notification
xmatters Property Map: Configuration for XMatters Notification

Outputs

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

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

@staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        ansible_tower: Optional[NotificationAnsibleTowerArgs] = None,
        config: Optional[NotificationConfigArgs] = None,
        email: Optional[NotificationEmailArgs] = None,
        hipchat: Optional[NotificationHipchatArgs] = None,
        jira: Optional[NotificationJiraArgs] = None,
        ops_genie: Optional[NotificationOpsGenieArgs] = None,
        pager_duty: Optional[NotificationPagerDutyArgs] = None,
        service_now: Optional[NotificationServiceNowArgs] = None,
        slack: Optional[NotificationSlackArgs] = None,
        trello: Optional[NotificationTrelloArgs] = None,
        victor_ops: Optional[NotificationVictorOpsArgs] = None,
        web_hook: Optional[NotificationWebHookArgs] = None,
        xmatters: Optional[NotificationXmattersArgs] = None) -> Notification

func GetNotification(ctx *Context, name string, id IDInput, state *NotificationState, opts ...ResourceOption) (*Notification, error)

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

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

AnsibleTower Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
Config Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationConfigArgs: Configuration for Generic Notification
Email Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationEmailArgs: Configuration for Email Notification
Hipchat Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationHipchatArgs: Configuration for HipChat Notification
Jira Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationJiraArgs: Configuration for Jira Notification
OpsGenie Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationOpsGenieArgs: Configuration for OpsGenie Notification
PagerDuty Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationPagerDutyArgs: Configuration for PagerDuty Notification
ServiceNow Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationServiceNowArgs: Configuration for ServiceNow Notification
Slack Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationSlackArgs: Configuration for Slack Notification
Trello Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationTrelloArgs: Configuration for Trello Notification
VictorOps Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationVictorOpsArgs: Configuration for VictorOps Notification
WebHook Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationWebHookArgs: Configuration for WebHook Notification
Xmatters Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationXmattersArgs: Configuration for XMatters Notification

AnsibleTower NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
Config NotificationConfigArgs: Configuration for Generic Notification
Email NotificationEmailArgs: Configuration for Email Notification
Hipchat NotificationHipchatArgs: Configuration for HipChat Notification
Jira NotificationJiraArgs: Configuration for Jira Notification
OpsGenie NotificationOpsGenieArgs: Configuration for OpsGenie Notification
PagerDuty NotificationPagerDutyArgs: Configuration for PagerDuty Notification
ServiceNow NotificationServiceNowArgs: Configuration for ServiceNow Notification
Slack NotificationSlackArgs: Configuration for Slack Notification
Trello NotificationTrelloArgs: Configuration for Trello Notification
VictorOps NotificationVictorOpsArgs: Configuration for VictorOps Notification
WebHook NotificationWebHookArgs: Configuration for WebHook Notification
Xmatters NotificationXmattersArgs: Configuration for XMatters Notification

ansibleTower NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
config NotificationConfigArgs: Configuration for Generic Notification
email NotificationEmailArgs: Configuration for Email Notification
hipchat NotificationHipchatArgs: Configuration for HipChat Notification
jira NotificationJiraArgs: Configuration for Jira Notification
opsGenie NotificationOpsGenieArgs: Configuration for OpsGenie Notification
pagerDuty NotificationPagerDutyArgs: Configuration for PagerDuty Notification
serviceNow NotificationServiceNowArgs: Configuration for ServiceNow Notification
slack NotificationSlackArgs: Configuration for Slack Notification
trello NotificationTrelloArgs: Configuration for Trello Notification
victorOps NotificationVictorOpsArgs: Configuration for VictorOps Notification
webHook NotificationWebHookArgs: Configuration for WebHook Notification
xmatters NotificationXmattersArgs: Configuration for XMatters Notification

ansibleTower NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
config NotificationConfigArgs: Configuration for Generic Notification
email NotificationEmailArgs: Configuration for Email Notification
hipchat NotificationHipchatArgs: Configuration for HipChat Notification
jira NotificationJiraArgs: Configuration for Jira Notification
opsGenie NotificationOpsGenieArgs: Configuration for OpsGenie Notification
pagerDuty NotificationPagerDutyArgs: Configuration for PagerDuty Notification
serviceNow NotificationServiceNowArgs: Configuration for ServiceNow Notification
slack NotificationSlackArgs: Configuration for Slack Notification
trello NotificationTrelloArgs: Configuration for Trello Notification
victorOps NotificationVictorOpsArgs: Configuration for VictorOps Notification
webHook NotificationWebHookArgs: Configuration for WebHook Notification
xmatters NotificationXmattersArgs: Configuration for XMatters Notification

ansible_tower NotificationAnsibleTowerArgs: Configuration for Ansible Tower Notification
config NotificationConfigArgs: Configuration for Generic Notification
email NotificationEmailArgs: Configuration for Email Notification
hipchat NotificationHipchatArgs: Configuration for HipChat Notification
jira NotificationJiraArgs: Configuration for Jira Notification
ops_genie NotificationOpsGenieArgs: Configuration for OpsGenie Notification
pager_duty NotificationPagerDutyArgs: Configuration for PagerDuty Notification
service_now NotificationServiceNowArgs: Configuration for ServiceNow Notification
slack NotificationSlackArgs: Configuration for Slack Notification
trello NotificationTrelloArgs: Configuration for Trello Notification
victor_ops NotificationVictorOpsArgs: Configuration for VictorOps Notification
web_hook NotificationWebHookArgs: Configuration for WebHook Notification
xmatters NotificationXmattersArgs: Configuration for XMatters Notification

ansibleTower Property Map: Configuration for Ansible Tower Notification
config Property Map: Configuration for Generic Notification
email Property Map: Configuration for Email Notification
hipchat Property Map: Configuration for HipChat Notification
jira Property Map: Configuration for Jira Notification
opsGenie Property Map: Configuration for OpsGenie Notification
pagerDuty Property Map: Configuration for PagerDuty Notification
serviceNow Property Map: Configuration for ServiceNow Notification
slack Property Map: Configuration for Slack Notification
trello Property Map: Configuration for Trello Notification
victorOps Property Map: Configuration for VictorOps Notification
webHook Property Map: Configuration for WebHook Notification
xmatters Property Map: Configuration for XMatters Notification

Supporting Types

NotificationAnsibleTower

AcceptAnyCertificate bool: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
CustomMessage string: The custom message of the notification. This message will be displayed in the extra variables Message field of your job template. 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. * {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
JobTemplateId int: The ID of the target Ansible Tower job template
JobTemplateUrl string: The URL of the target Ansible Tower job template
Name string: The name of the notification configuration
Username string: The username of the Ansible Tower account
Password string: The password for the Ansible Tower account
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

AcceptAnyCertificate bool: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
CustomMessage string: The custom message of the notification. This message will be displayed in the extra variables Message field of your job template. 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. * {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
JobTemplateId int: The ID of the target Ansible Tower job template
JobTemplateUrl string: The URL of the target Ansible Tower job template
Name string: The name of the notification configuration
Username string: The username of the Ansible Tower account
Password string: The password for the Ansible Tower account
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

acceptAnyCertificate Boolean: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
customMessage String: The custom message of the notification. This message will be displayed in the extra variables Message field of your job template. 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. * {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
jobTemplateId Integer: The ID of the target Ansible Tower job template
jobTemplateUrl String: The URL of the target Ansible Tower job template
name String: The name of the notification configuration
username String: The username of the Ansible Tower account
password String: The password for the Ansible Tower account
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

acceptAnyCertificate boolean: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
customMessage string: The custom message of the notification. This message will be displayed in the extra variables Message field of your job template. 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. * {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
jobTemplateId number: The ID of the target Ansible Tower job template
jobTemplateUrl string: The URL of the target Ansible Tower job template
name string: The name of the notification configuration
username string: The username of the Ansible Tower account
password string: The password for the Ansible Tower account
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

accept_any_certificate bool: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
custom_message str: The custom message of the notification. This message will be displayed in the extra variables Message field of your job template. 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. * {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
job_template_id int: The ID of the target Ansible Tower job template
job_template_url str: The URL of the target Ansible Tower job template
name str: The name of the notification configuration
username str: The username of the Ansible Tower account
password str: The password for the Ansible Tower account
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

acceptAnyCertificate Boolean: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
customMessage String: The custom message of the notification. This message will be displayed in the extra variables Message field of your job template. 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. * {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
jobTemplateId Number: The ID of the target Ansible Tower job template
jobTemplateUrl String: The URL of the target Ansible Tower job template
name String: The name of the notification configuration
username String: The username of the Ansible Tower account
password String: The password for the Ansible Tower account
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationConfig

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Name string: The name of the notification configuration
Type string: Defines the actual set of fields depending on the value. See one of the following objects: * EMAIL > EmailNotificationConfig * PAGER_DUTY > PagerDutyNotificationConfig * WEBHOOK > WebHookNotificationConfig * SLACK > SlackNotificationConfig * HIPCHAT > HipChatNotificationConfig * VICTOROPS > VictorOpsNotificationConfig * SERVICE_NOW > ServiceNowNotificationConfig * XMATTERS > XMattersNotificationConfig * ANSIBLETOWER > AnsibleTowerNotificationConfig * OPS_GENIE > OpsGenieNotificationConfig * JIRA > JiraNotificationConfig * TRELLO > TrelloNotificationConfig
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Name string: The name of the notification configuration
Type string: Defines the actual set of fields depending on the value. See one of the following objects: * EMAIL > EmailNotificationConfig * PAGER_DUTY > PagerDutyNotificationConfig * WEBHOOK > WebHookNotificationConfig * SLACK > SlackNotificationConfig * HIPCHAT > HipChatNotificationConfig * VICTOROPS > VictorOpsNotificationConfig * SERVICE_NOW > ServiceNowNotificationConfig * XMATTERS > XMattersNotificationConfig * ANSIBLETOWER > AnsibleTowerNotificationConfig * OPS_GENIE > OpsGenieNotificationConfig * JIRA > JiraNotificationConfig * TRELLO > TrelloNotificationConfig
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
name String: The name of the notification configuration
type String: Defines the actual set of fields depending on the value. See one of the following objects: * EMAIL > EmailNotificationConfig * PAGER_DUTY > PagerDutyNotificationConfig * WEBHOOK > WebHookNotificationConfig * SLACK > SlackNotificationConfig * HIPCHAT > HipChatNotificationConfig * VICTOROPS > VictorOpsNotificationConfig * SERVICE_NOW > ServiceNowNotificationConfig * XMATTERS > XMattersNotificationConfig * ANSIBLETOWER > AnsibleTowerNotificationConfig * OPS_GENIE > OpsGenieNotificationConfig * JIRA > JiraNotificationConfig * TRELLO > TrelloNotificationConfig
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
name string: The name of the notification configuration
type string: Defines the actual set of fields depending on the value. See one of the following objects: * EMAIL > EmailNotificationConfig * PAGER_DUTY > PagerDutyNotificationConfig * WEBHOOK > WebHookNotificationConfig * SLACK > SlackNotificationConfig * HIPCHAT > HipChatNotificationConfig * VICTOROPS > VictorOpsNotificationConfig * SERVICE_NOW > ServiceNowNotificationConfig * XMATTERS > XMattersNotificationConfig * ANSIBLETOWER > AnsibleTowerNotificationConfig * OPS_GENIE > OpsGenieNotificationConfig * JIRA > JiraNotificationConfig * TRELLO > TrelloNotificationConfig
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
name str: The name of the notification configuration
type str: Defines the actual set of fields depending on the value. See one of the following objects: * EMAIL > EmailNotificationConfig * PAGER_DUTY > PagerDutyNotificationConfig * WEBHOOK > WebHookNotificationConfig * SLACK > SlackNotificationConfig * HIPCHAT > HipChatNotificationConfig * VICTOROPS > VictorOpsNotificationConfig * SERVICE_NOW > ServiceNowNotificationConfig * XMATTERS > XMattersNotificationConfig * ANSIBLETOWER > AnsibleTowerNotificationConfig * OPS_GENIE > OpsGenieNotificationConfig * JIRA > JiraNotificationConfig * TRELLO > TrelloNotificationConfig
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
name String: The name of the notification configuration
type String: Defines the actual set of fields depending on the value. See one of the following objects: * EMAIL > EmailNotificationConfig * PAGER_DUTY > PagerDutyNotificationConfig * WEBHOOK > WebHookNotificationConfig * SLACK > SlackNotificationConfig * HIPCHAT > HipChatNotificationConfig * VICTOROPS > VictorOpsNotificationConfig * SERVICE_NOW > ServiceNowNotificationConfig * XMATTERS > XMattersNotificationConfig * ANSIBLETOWER > AnsibleTowerNotificationConfig * OPS_GENIE > OpsGenieNotificationConfig * JIRA > JiraNotificationConfig * TRELLO > TrelloNotificationConfig
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationEmail

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
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
Name string: The name of the notification configuration
Subject string: The subject of the email notifications
BccReceivers List<string>: The list of the email BCC-recipients
CcReceivers List<string>: The list of the email CC-recipients
Receivers List<string>: The list of the email recipients
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
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
Name string: The name of the notification configuration
Subject string: The subject of the email notifications
BccReceivers []string: The list of the email BCC-recipients
CcReceivers []string: The list of the email CC-recipients
Receivers []string: The list of the email recipients
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
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
name String: The name of the notification configuration
subject String: The subject of the email notifications
bccReceivers List<String>: The list of the email BCC-recipients
ccReceivers List<String>: The list of the email CC-recipients
receivers List<String>: The list of the email recipients
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
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
name string: The name of the notification configuration
subject string: The subject of the email notifications
bccReceivers string[]: The list of the email BCC-recipients
ccReceivers string[]: The list of the email CC-recipients
receivers string[]: The list of the email recipients
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
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
name str: The name of the notification configuration
subject str: The subject of the email notifications
bcc_receivers Sequence[str]: The list of the email BCC-recipients
cc_receivers Sequence[str]: The list of the email CC-recipients
receivers Sequence[str]: The list of the email recipients
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
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
name String: The name of the notification configuration
subject String: The subject of the email notifications
bccReceivers List<String>: The list of the email BCC-recipients
ccReceivers List<String>: The list of the email CC-recipients
receivers List<String>: The list of the email recipients
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationHipchat

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Message string: The content of the notification message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
Name string: The name of the notification configuration
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider
Url string: The URL of the HipChat WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Message string: The content of the notification message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
Name string: The name of the notification configuration
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider
Url string: The URL of the HipChat WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
message String: The content of the notification message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
name String: The name of the notification configuration
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider
url String: The URL of the HipChat WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
message string: The content of the notification message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
name string: The name of the notification configuration
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider
url string: The URL of the HipChat WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
message str: The content of the notification message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
name str: The name of the notification configuration
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider
url str: The URL of the HipChat WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
message String: The content of the notification message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
name String: The name of the notification configuration
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider
url String: The URL of the HipChat WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

NotificationJira

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Description string: The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
IssueType string: The type of the Jira issue to be created by this notification
Name string: The name of the notification configuration
ProjectKey string: The project key of the Jira issue to be created by this notification
Summary string: The summary of the Jira issue to be created by this notification. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
Url string: The URL of the Jira API endpoint
Username string: The username of the Jira profile
Password string: The password for the Jira profile
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Description string: The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
IssueType string: The type of the Jira issue to be created by this notification
Name string: The name of the notification configuration
ProjectKey string: The project key of the Jira issue to be created by this notification
Summary string: The summary of the Jira issue to be created by this notification. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
Url string: The URL of the Jira API endpoint
Username string: The username of the Jira profile
Password string: The password for the Jira profile
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
description String: The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
issueType String: The type of the Jira issue to be created by this notification
name String: The name of the notification configuration
projectKey String: The project key of the Jira issue to be created by this notification
summary String: The summary of the Jira issue to be created by this notification. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
url String: The URL of the Jira API endpoint
username String: The username of the Jira profile
password String: The password for the Jira profile
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
description string: The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
issueType string: The type of the Jira issue to be created by this notification
name string: The name of the notification configuration
projectKey string: The project key of the Jira issue to be created by this notification
summary string: The summary of the Jira issue to be created by this notification. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
url string: The URL of the Jira API endpoint
username string: The username of the Jira profile
password string: The password for the Jira profile
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
description str: The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
issue_type str: The type of the Jira issue to be created by this notification
name str: The name of the notification configuration
project_key str: The project key of the Jira issue to be created by this notification
summary str: The summary of the Jira issue to be created by this notification. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
url str: The URL of the Jira API endpoint
username str: The username of the Jira profile
password str: The password for the Jira profile
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
description String: The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
issueType String: The type of the Jira issue to be created by this notification
name String: The name of the notification configuration
projectKey String: The project key of the Jira issue to be created by this notification
summary String: The summary of the Jira issue to be created by this notification. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
url String: The URL of the Jira API endpoint
username String: The username of the Jira profile
password String: The password for the Jira profile
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationOpsGenie

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Domain string: The region domain of the OpsGenie
Message string: The content of the message. You can use the following placeholders: * {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
Name string: The name of the notification configuration
ApiKey string: The API key to access OpsGenie
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Domain string: The region domain of the OpsGenie
Message string: The content of the message. You can use the following placeholders: * {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
Name string: The name of the notification configuration
ApiKey string: The API key to access OpsGenie
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
domain String: The region domain of the OpsGenie
message String: The content of the message. You can use the following placeholders: * {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
name String: The name of the notification configuration
apiKey String: The API key to access OpsGenie
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
domain string: The region domain of the OpsGenie
message string: The content of the message. You can use the following placeholders: * {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
name string: The name of the notification configuration
apiKey string: The API key to access OpsGenie
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
domain str: The region domain of the OpsGenie
message str: The content of the message. You can use the following placeholders: * {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
name str: The name of the notification configuration
api_key str: The API key to access OpsGenie
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
domain String: The region domain of the OpsGenie
message String: The content of the message. You can use the following placeholders: * {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
name String: The name of the notification configuration
apiKey String: The API key to access OpsGenie
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationPagerDuty

Account string: The name of the PagerDuty account
Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Name string: The name of the notification configuration
ServiceName string: The name of the service
ServiceApiKey string: The API key to access PagerDuty
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

Account string: The name of the PagerDuty account
Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Name string: The name of the notification configuration
ServiceName string: The name of the service
ServiceApiKey string: The API key to access PagerDuty
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

account String: The name of the PagerDuty account
active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
name String: The name of the notification configuration
serviceName String: The name of the service
serviceApiKey String: The API key to access PagerDuty
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

account string: The name of the PagerDuty account
active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
name string: The name of the notification configuration
serviceName string: The name of the service
serviceApiKey string: The API key to access PagerDuty
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

account str: The name of the PagerDuty account
active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
name str: The name of the notification configuration
service_name str: The name of the service
service_api_key str: The API key to access PagerDuty
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

account String: The name of the PagerDuty account
active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
name String: The name of the notification configuration
serviceName String: The name of the service
serviceApiKey String: The API key to access PagerDuty
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationServiceNow

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Message string: The content of the ServiceNow description. You can use the following placeholders: * {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. * {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
Name string: The name of the notification configuration
SendEvents bool: Send events into ServiceNow ITOM (true)
SendIncidents bool: Send incidents into ServiceNow ITSM (true)
Username string: The username of the ServiceNow account. Make sure that your user account has the rest_service, web_request_admin, and x_dynat_ruxit.Integration roles
InstanceName string: The ServiceNow instance identifier. It refers to the first part of your own ServiceNow URL. This field is mutually exclusive with the url field. You can only use one of them
Password string: The username to the ServiceNow account
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider
Url string: The URL of the on-premise ServiceNow installation. This field is mutually exclusive with the instanceName field. You can only use one of them

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Message string: The content of the ServiceNow description. You can use the following placeholders: * {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. * {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
Name string: The name of the notification configuration
SendEvents bool: Send events into ServiceNow ITOM (true)
SendIncidents bool: Send incidents into ServiceNow ITSM (true)
Username string: The username of the ServiceNow account. Make sure that your user account has the rest_service, web_request_admin, and x_dynat_ruxit.Integration roles
InstanceName string: The ServiceNow instance identifier. It refers to the first part of your own ServiceNow URL. This field is mutually exclusive with the url field. You can only use one of them
Password string: The username to the ServiceNow account
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider
Url string: The URL of the on-premise ServiceNow installation. This field is mutually exclusive with the instanceName field. You can only use one of them

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
message String: The content of the ServiceNow description. You can use the following placeholders: * {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. * {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
name String: The name of the notification configuration
sendEvents Boolean: Send events into ServiceNow ITOM (true)
sendIncidents Boolean: Send incidents into ServiceNow ITSM (true)
username String: The username of the ServiceNow account. Make sure that your user account has the rest_service, web_request_admin, and x_dynat_ruxit.Integration roles
instanceName String: The ServiceNow instance identifier. It refers to the first part of your own ServiceNow URL. This field is mutually exclusive with the url field. You can only use one of them
password String: The username to the ServiceNow account
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider
url String: The URL of the on-premise ServiceNow installation. This field is mutually exclusive with the instanceName field. You can only use one of them

active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
message string: The content of the ServiceNow description. You can use the following placeholders: * {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. * {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
name string: The name of the notification configuration
sendEvents boolean: Send events into ServiceNow ITOM (true)
sendIncidents boolean: Send incidents into ServiceNow ITSM (true)
username string: The username of the ServiceNow account. Make sure that your user account has the rest_service, web_request_admin, and x_dynat_ruxit.Integration roles
instanceName string: The ServiceNow instance identifier. It refers to the first part of your own ServiceNow URL. This field is mutually exclusive with the url field. You can only use one of them
password string: The username to the ServiceNow account
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider
url string: The URL of the on-premise ServiceNow installation. This field is mutually exclusive with the instanceName field. You can only use one of them

active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
message str: The content of the ServiceNow description. You can use the following placeholders: * {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. * {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
name str: The name of the notification configuration
send_events bool: Send events into ServiceNow ITOM (true)
send_incidents bool: Send incidents into ServiceNow ITSM (true)
username str: The username of the ServiceNow account. Make sure that your user account has the rest_service, web_request_admin, and x_dynat_ruxit.Integration roles
instance_name str: The ServiceNow instance identifier. It refers to the first part of your own ServiceNow URL. This field is mutually exclusive with the url field. You can only use one of them
password str: The username to the ServiceNow account
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider
url str: The URL of the on-premise ServiceNow installation. This field is mutually exclusive with the instanceName field. You can only use one of them

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
message String: The content of the ServiceNow description. You can use the following placeholders: * {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. * {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
name String: The name of the notification configuration
sendEvents Boolean: Send events into ServiceNow ITOM (true)
sendIncidents Boolean: Send incidents into ServiceNow ITSM (true)
username String: The username of the ServiceNow account. Make sure that your user account has the rest_service, web_request_admin, and x_dynat_ruxit.Integration roles
instanceName String: The ServiceNow instance identifier. It refers to the first part of your own ServiceNow URL. This field is mutually exclusive with the url field. You can only use one of them
password String: The username to the ServiceNow account
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider
url String: The URL of the on-premise ServiceNow installation. This field is mutually exclusive with the instanceName field. You can only use one of them

NotificationSlack

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Channel string: The channel (for example, #general) or the user (for example, @john.smith) to send the message to
Name string: The name of the notification configuration
Title string: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider
Url string: The URL of the Slack WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Channel string: The channel (for example, #general) or the user (for example, @john.smith) to send the message to
Name string: The name of the notification configuration
Title string: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider
Url string: The URL of the Slack WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
channel String: The channel (for example, #general) or the user (for example, @john.smith) to send the message to
name String: The name of the notification configuration
title String: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider
url String: The URL of the Slack WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
channel string: The channel (for example, #general) or the user (for example, @john.smith) to send the message to
name string: The name of the notification configuration
title string: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider
url string: The URL of the Slack WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
channel str: The channel (for example, #general) or the user (for example, @john.smith) to send the message to
name str: The name of the notification configuration
title str: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider
url str: The URL of the Slack WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
channel String: The channel (for example, #general) or the user (for example, @john.smith) to send the message to
name String: The name of the notification configuration
title String: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {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
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider
url String: The URL of the Slack WebHook. This is confidential information, therefore GET requests return this field with the null value, and it is optional for PUT requests

NotificationTrello

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
ApplicationKey string: The application key for the Trello account
BoardId string: The Trello board to which the card should be assigned
Description string: The description of the Trello card. You can use same placeholders as in card text
ListId string: The Trello list to which the card should be assigned
Name string: The name of the notification configuration
ResolvedListId string: The Trello list to which the card of the resolved problem should be assigned
Text string: The text of the generated Trello card. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-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
AuthorizationToken string: The application token for the Trello account
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
ApplicationKey string: The application key for the Trello account
BoardId string: The Trello board to which the card should be assigned
Description string: The description of the Trello card. You can use same placeholders as in card text
ListId string: The Trello list to which the card should be assigned
Name string: The name of the notification configuration
ResolvedListId string: The Trello list to which the card of the resolved problem should be assigned
Text string: The text of the generated Trello card. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-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
AuthorizationToken string: The application token for the Trello account
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
applicationKey String: The application key for the Trello account
boardId String: The Trello board to which the card should be assigned
description String: The description of the Trello card. You can use same placeholders as in card text
listId String: The Trello list to which the card should be assigned
name String: The name of the notification configuration
resolvedListId String: The Trello list to which the card of the resolved problem should be assigned
text String: The text of the generated Trello card. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-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
authorizationToken String: The application token for the Trello account
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
applicationKey string: The application key for the Trello account
boardId string: The Trello board to which the card should be assigned
description string: The description of the Trello card. You can use same placeholders as in card text
listId string: The Trello list to which the card should be assigned
name string: The name of the notification configuration
resolvedListId string: The Trello list to which the card of the resolved problem should be assigned
text string: The text of the generated Trello card. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-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
authorizationToken string: The application token for the Trello account
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
application_key str: The application key for the Trello account
board_id str: The Trello board to which the card should be assigned
description str: The description of the Trello card. You can use same placeholders as in card text
list_id str: The Trello list to which the card should be assigned
name str: The name of the notification configuration
resolved_list_id str: The Trello list to which the card of the resolved problem should be assigned
text str: The text of the generated Trello card. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-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
authorization_token str: The application token for the Trello account
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
applicationKey String: The application key for the Trello account
boardId String: The Trello board to which the card should be assigned
description String: The description of the Trello card. You can use same placeholders as in card text
listId String: The Trello list to which the card should be assigned
name String: The name of the notification configuration
resolvedListId String: The Trello list to which the card of the resolved problem should be assigned
text String: The text of the generated Trello card. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {PID}: The ID of the reported problem. * {ProblemDetailsMarkdown}: All problem event details, including root cause, as a Markdown-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
authorizationToken String: The application token for the Trello account
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationVictorOps

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Message string: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {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
Name string: The name of the notification configuration
RoutingKey string: The routing key, defining the group to be notified
ApiKey string: The API key for the target VictorOps account
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Message string: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {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
Name string: The name of the notification configuration
RoutingKey string: The routing key, defining the group to be notified
ApiKey string: The API key for the target VictorOps account
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
message String: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {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
name String: The name of the notification configuration
routingKey String: The routing key, defining the group to be notified
apiKey String: The API key for the target VictorOps account
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
message string: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {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
name string: The name of the notification configuration
routingKey string: The routing key, defining the group to be notified
apiKey string: The API key for the target VictorOps account
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
message str: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {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
name str: The name of the notification configuration
routing_key str: The routing key, defining the group to be notified
api_key str: The API key for the target VictorOps account
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
message String: The content of the message. You can use the following placeholders: * {ImpactedEntity}: The entity impacted by the problem or X impacted entities. * {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
name String: The name of the notification configuration
routingKey String: The routing key, defining the group to be notified
apiKey String: The API key for the target VictorOps account
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationWebHook

AcceptAnyCertificate bool: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Name string: The name of the notification configuration
Payload string: The content of the notification message. 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
Url string: The URL of the WebHook endpoint
Headers List<Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationWebHookHeader>: A list of the additional HTTP headers
NotifyEventMerges bool: Call webhook if new events merge into existing problems
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

AcceptAnyCertificate bool: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Name string: The name of the notification configuration
Payload string: The content of the notification message. 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
Url string: The URL of the WebHook endpoint
Headers []NotificationWebHookHeader: A list of the additional HTTP headers
NotifyEventMerges bool: Call webhook if new events merge into existing problems
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

acceptAnyCertificate Boolean: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
name String: The name of the notification configuration
payload String: The content of the notification message. 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
url String: The URL of the WebHook endpoint
headers List<NotificationWebHookHeader>: A list of the additional HTTP headers
notifyEventMerges Boolean: Call webhook if new events merge into existing problems
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

acceptAnyCertificate boolean: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
name string: The name of the notification configuration
payload string: The content of the notification message. 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
url string: The URL of the WebHook endpoint
headers NotificationWebHookHeader[]: A list of the additional HTTP headers
notifyEventMerges boolean: Call webhook if new events merge into existing problems
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

accept_any_certificate bool: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
name str: The name of the notification configuration
payload str: The content of the notification message. 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
url str: The URL of the WebHook endpoint
headers Sequence[NotificationWebHookHeader]: A list of the additional HTTP headers
notify_event_merges bool: Call webhook if new events merge into existing problems
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

acceptAnyCertificate Boolean: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
name String: The name of the notification configuration
payload String: The content of the notification message. 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
url String: The URL of the WebHook endpoint
headers List<Property Map>: A list of the additional HTTP headers
notifyEventMerges Boolean: Call webhook if new events merge into existing problems
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationWebHookHeader

Name string
Value string

Name string
Value string

name String
value String

name string
value string

name str
value str

name String
value String

NotificationXmatters

AcceptAnyCertificate bool: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Name string: The name of the notification configuration
Payload string: The content of the notification message. 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
Url string: The URL of the xMatters WebHook
Headers List<Lbrlabs.PulumiPackage.Dynatrace.Inputs.NotificationXmattersHeader>: A list of the additional HTTP headers
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

AcceptAnyCertificate bool: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
Active bool: The configuration is enabled (true) or disabled (false)
AlertingProfile string: The ID of the associated alerting profile
Name string: The name of the notification configuration
Payload string: The content of the notification message. 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
Url string: The URL of the xMatters WebHook
Headers []NotificationXmattersHeader: A list of the additional HTTP headers
Unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

acceptAnyCertificate Boolean: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
name String: The name of the notification configuration
payload String: The content of the notification message. 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
url String: The URL of the xMatters WebHook
headers List<NotificationXmattersHeader>: A list of the additional HTTP headers
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

acceptAnyCertificate boolean: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active boolean: The configuration is enabled (true) or disabled (false)
alertingProfile string: The ID of the associated alerting profile
name string: The name of the notification configuration
payload string: The content of the notification message. 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
url string: The URL of the xMatters WebHook
headers NotificationXmattersHeader[]: A list of the additional HTTP headers
unknowns string: allows for configuring properties that are not explicitly supported by the current version of this provider

accept_any_certificate bool: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active bool: The configuration is enabled (true) or disabled (false)
alerting_profile str: The ID of the associated alerting profile
name str: The name of the notification configuration
payload str: The content of the notification message. 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
url str: The URL of the xMatters WebHook
headers Sequence[NotificationXmattersHeader]: A list of the additional HTTP headers
unknowns str: allows for configuring properties that are not explicitly supported by the current version of this provider

acceptAnyCertificate Boolean: Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates
active Boolean: The configuration is enabled (true) or disabled (false)
alertingProfile String: The ID of the associated alerting profile
name String: The name of the notification configuration
payload String: The content of the notification message. 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
url String: The URL of the xMatters WebHook
headers List<Property Map>: A list of the additional HTTP headers
unknowns String: allows for configuring properties that are not explicitly supported by the current version of this provider

NotificationXmattersHeader

Name string
Value string

Name string
Value string

name String
value String

name string
value string

name str
value str

name String
value String

Package Details

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