dynatrace.Notification
Explore with Pulumi AI
Create Notification Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new Notification(name: string, args?: NotificationArgs, opts?: CustomResourceOptions);@overload
def Notification(resource_name: str,
                 args: Optional[NotificationArgs] = None,
                 opts: Optional[ResourceOptions] = None)
@overload
def Notification(resource_name: str,
                 opts: Optional[ResourceOptions] = None,
                 ansible_tower: Optional[NotificationAnsibleTowerArgs] = None,
                 config: Optional[NotificationConfigArgs] = None,
                 email: Optional[NotificationEmailArgs] = 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)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.
Parameters
- 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.
Constructor example
The following reference example uses placeholder values for all input properties.
var notificationResource = new Dynatrace.Notification("notificationResource", new()
{
    AnsibleTower = new Dynatrace.Inputs.NotificationAnsibleTowerArgs
    {
        AcceptAnyCertificate = false,
        Active = false,
        AlertingProfile = "string",
        CustomMessage = "string",
        JobTemplateId = 0,
        JobTemplateUrl = "string",
        Name = "string",
        Username = "string",
        Password = "string",
        Unknowns = "string",
    },
    Config = new Dynatrace.Inputs.NotificationConfigArgs
    {
        Active = false,
        AlertingProfile = "string",
        Name = "string",
        Type = "string",
        Unknowns = "string",
    },
    Email = new Dynatrace.Inputs.NotificationEmailArgs
    {
        Active = false,
        AlertingProfile = "string",
        Body = "string",
        Name = "string",
        Subject = "string",
        BccReceivers = new[]
        {
            "string",
        },
        CcReceivers = new[]
        {
            "string",
        },
        Receivers = new[]
        {
            "string",
        },
        Unknowns = "string",
    },
    Jira = new Dynatrace.Inputs.NotificationJiraArgs
    {
        Active = false,
        AlertingProfile = "string",
        Description = "string",
        IssueType = "string",
        Name = "string",
        ProjectKey = "string",
        Summary = "string",
        Url = "string",
        Username = "string",
        Password = "string",
        Unknowns = "string",
    },
    OpsGenie = new Dynatrace.Inputs.NotificationOpsGenieArgs
    {
        Active = false,
        AlertingProfile = "string",
        Domain = "string",
        Message = "string",
        Name = "string",
        ApiKey = "string",
        Unknowns = "string",
    },
    PagerDuty = new Dynatrace.Inputs.NotificationPagerDutyArgs
    {
        Account = "string",
        Active = false,
        AlertingProfile = "string",
        Name = "string",
        ServiceName = "string",
        ServiceApiKey = "string",
        Unknowns = "string",
    },
    ServiceNow = new Dynatrace.Inputs.NotificationServiceNowArgs
    {
        Active = false,
        AlertingProfile = "string",
        Message = "string",
        Name = "string",
        SendEvents = false,
        SendIncidents = false,
        Username = "string",
        InstanceName = "string",
        Password = "string",
        Unknowns = "string",
        Url = "string",
    },
    Slack = new Dynatrace.Inputs.NotificationSlackArgs
    {
        Active = false,
        AlertingProfile = "string",
        Channel = "string",
        Name = "string",
        Title = "string",
        Unknowns = "string",
        Url = "string",
    },
    Trello = new Dynatrace.Inputs.NotificationTrelloArgs
    {
        Active = false,
        AlertingProfile = "string",
        ApplicationKey = "string",
        BoardId = "string",
        Description = "string",
        ListId = "string",
        Name = "string",
        ResolvedListId = "string",
        Text = "string",
        AuthorizationToken = "string",
        Unknowns = "string",
    },
    VictorOps = new Dynatrace.Inputs.NotificationVictorOpsArgs
    {
        Active = false,
        AlertingProfile = "string",
        Message = "string",
        Name = "string",
        RoutingKey = "string",
        ApiKey = "string",
        Unknowns = "string",
    },
    WebHook = new Dynatrace.Inputs.NotificationWebHookArgs
    {
        AcceptAnyCertificate = false,
        Active = false,
        AlertingProfile = "string",
        Name = "string",
        Payload = "string",
        Url = "string",
        Headers = new[]
        {
            new Dynatrace.Inputs.NotificationWebHookHeaderArgs
            {
                Name = "string",
                Value = "string",
            },
        },
        NotifyEventMerges = false,
        Unknowns = "string",
    },
    Xmatters = new Dynatrace.Inputs.NotificationXmattersArgs
    {
        AcceptAnyCertificate = false,
        Active = false,
        AlertingProfile = "string",
        Name = "string",
        Payload = "string",
        Url = "string",
        Headers = new[]
        {
            new Dynatrace.Inputs.NotificationXmattersHeaderArgs
            {
                Name = "string",
                Value = "string",
            },
        },
        Unknowns = "string",
    },
});
example, err := dynatrace.NewNotification(ctx, "notificationResource", &dynatrace.NotificationArgs{
	AnsibleTower: &dynatrace.NotificationAnsibleTowerArgs{
		AcceptAnyCertificate: pulumi.Bool(false),
		Active:               pulumi.Bool(false),
		AlertingProfile:      pulumi.String("string"),
		CustomMessage:        pulumi.String("string"),
		JobTemplateId:        pulumi.Int(0),
		JobTemplateUrl:       pulumi.String("string"),
		Name:                 pulumi.String("string"),
		Username:             pulumi.String("string"),
		Password:             pulumi.String("string"),
		Unknowns:             pulumi.String("string"),
	},
	Config: &dynatrace.NotificationConfigArgs{
		Active:          pulumi.Bool(false),
		AlertingProfile: pulumi.String("string"),
		Name:            pulumi.String("string"),
		Type:            pulumi.String("string"),
		Unknowns:        pulumi.String("string"),
	},
	Email: &dynatrace.NotificationEmailArgs{
		Active:          pulumi.Bool(false),
		AlertingProfile: pulumi.String("string"),
		Body:            pulumi.String("string"),
		Name:            pulumi.String("string"),
		Subject:         pulumi.String("string"),
		BccReceivers: pulumi.StringArray{
			pulumi.String("string"),
		},
		CcReceivers: pulumi.StringArray{
			pulumi.String("string"),
		},
		Receivers: pulumi.StringArray{
			pulumi.String("string"),
		},
		Unknowns: pulumi.String("string"),
	},
	Jira: &dynatrace.NotificationJiraArgs{
		Active:          pulumi.Bool(false),
		AlertingProfile: pulumi.String("string"),
		Description:     pulumi.String("string"),
		IssueType:       pulumi.String("string"),
		Name:            pulumi.String("string"),
		ProjectKey:      pulumi.String("string"),
		Summary:         pulumi.String("string"),
		Url:             pulumi.String("string"),
		Username:        pulumi.String("string"),
		Password:        pulumi.String("string"),
		Unknowns:        pulumi.String("string"),
	},
	OpsGenie: &dynatrace.NotificationOpsGenieArgs{
		Active:          pulumi.Bool(false),
		AlertingProfile: pulumi.String("string"),
		Domain:          pulumi.String("string"),
		Message:         pulumi.String("string"),
		Name:            pulumi.String("string"),
		ApiKey:          pulumi.String("string"),
		Unknowns:        pulumi.String("string"),
	},
	PagerDuty: &dynatrace.NotificationPagerDutyArgs{
		Account:         pulumi.String("string"),
		Active:          pulumi.Bool(false),
		AlertingProfile: pulumi.String("string"),
		Name:            pulumi.String("string"),
		ServiceName:     pulumi.String("string"),
		ServiceApiKey:   pulumi.String("string"),
		Unknowns:        pulumi.String("string"),
	},
	ServiceNow: &dynatrace.NotificationServiceNowArgs{
		Active:          pulumi.Bool(false),
		AlertingProfile: pulumi.String("string"),
		Message:         pulumi.String("string"),
		Name:            pulumi.String("string"),
		SendEvents:      pulumi.Bool(false),
		SendIncidents:   pulumi.Bool(false),
		Username:        pulumi.String("string"),
		InstanceName:    pulumi.String("string"),
		Password:        pulumi.String("string"),
		Unknowns:        pulumi.String("string"),
		Url:             pulumi.String("string"),
	},
	Slack: &dynatrace.NotificationSlackArgs{
		Active:          pulumi.Bool(false),
		AlertingProfile: pulumi.String("string"),
		Channel:         pulumi.String("string"),
		Name:            pulumi.String("string"),
		Title:           pulumi.String("string"),
		Unknowns:        pulumi.String("string"),
		Url:             pulumi.String("string"),
	},
	Trello: &dynatrace.NotificationTrelloArgs{
		Active:             pulumi.Bool(false),
		AlertingProfile:    pulumi.String("string"),
		ApplicationKey:     pulumi.String("string"),
		BoardId:            pulumi.String("string"),
		Description:        pulumi.String("string"),
		ListId:             pulumi.String("string"),
		Name:               pulumi.String("string"),
		ResolvedListId:     pulumi.String("string"),
		Text:               pulumi.String("string"),
		AuthorizationToken: pulumi.String("string"),
		Unknowns:           pulumi.String("string"),
	},
	VictorOps: &dynatrace.NotificationVictorOpsArgs{
		Active:          pulumi.Bool(false),
		AlertingProfile: pulumi.String("string"),
		Message:         pulumi.String("string"),
		Name:            pulumi.String("string"),
		RoutingKey:      pulumi.String("string"),
		ApiKey:          pulumi.String("string"),
		Unknowns:        pulumi.String("string"),
	},
	WebHook: &dynatrace.NotificationWebHookArgs{
		AcceptAnyCertificate: pulumi.Bool(false),
		Active:               pulumi.Bool(false),
		AlertingProfile:      pulumi.String("string"),
		Name:                 pulumi.String("string"),
		Payload:              pulumi.String("string"),
		Url:                  pulumi.String("string"),
		Headers: dynatrace.NotificationWebHookHeaderArray{
			&dynatrace.NotificationWebHookHeaderArgs{
				Name:  pulumi.String("string"),
				Value: pulumi.String("string"),
			},
		},
		NotifyEventMerges: pulumi.Bool(false),
		Unknowns:          pulumi.String("string"),
	},
	Xmatters: &dynatrace.NotificationXmattersArgs{
		AcceptAnyCertificate: pulumi.Bool(false),
		Active:               pulumi.Bool(false),
		AlertingProfile:      pulumi.String("string"),
		Name:                 pulumi.String("string"),
		Payload:              pulumi.String("string"),
		Url:                  pulumi.String("string"),
		Headers: dynatrace.NotificationXmattersHeaderArray{
			&dynatrace.NotificationXmattersHeaderArgs{
				Name:  pulumi.String("string"),
				Value: pulumi.String("string"),
			},
		},
		Unknowns: pulumi.String("string"),
	},
})
var notificationResource = new Notification("notificationResource", NotificationArgs.builder()
    .ansibleTower(NotificationAnsibleTowerArgs.builder()
        .acceptAnyCertificate(false)
        .active(false)
        .alertingProfile("string")
        .customMessage("string")
        .jobTemplateId(0)
        .jobTemplateUrl("string")
        .name("string")
        .username("string")
        .password("string")
        .unknowns("string")
        .build())
    .config(NotificationConfigArgs.builder()
        .active(false)
        .alertingProfile("string")
        .name("string")
        .type("string")
        .unknowns("string")
        .build())
    .email(NotificationEmailArgs.builder()
        .active(false)
        .alertingProfile("string")
        .body("string")
        .name("string")
        .subject("string")
        .bccReceivers("string")
        .ccReceivers("string")
        .receivers("string")
        .unknowns("string")
        .build())
    .jira(NotificationJiraArgs.builder()
        .active(false)
        .alertingProfile("string")
        .description("string")
        .issueType("string")
        .name("string")
        .projectKey("string")
        .summary("string")
        .url("string")
        .username("string")
        .password("string")
        .unknowns("string")
        .build())
    .opsGenie(NotificationOpsGenieArgs.builder()
        .active(false)
        .alertingProfile("string")
        .domain("string")
        .message("string")
        .name("string")
        .apiKey("string")
        .unknowns("string")
        .build())
    .pagerDuty(NotificationPagerDutyArgs.builder()
        .account("string")
        .active(false)
        .alertingProfile("string")
        .name("string")
        .serviceName("string")
        .serviceApiKey("string")
        .unknowns("string")
        .build())
    .serviceNow(NotificationServiceNowArgs.builder()
        .active(false)
        .alertingProfile("string")
        .message("string")
        .name("string")
        .sendEvents(false)
        .sendIncidents(false)
        .username("string")
        .instanceName("string")
        .password("string")
        .unknowns("string")
        .url("string")
        .build())
    .slack(NotificationSlackArgs.builder()
        .active(false)
        .alertingProfile("string")
        .channel("string")
        .name("string")
        .title("string")
        .unknowns("string")
        .url("string")
        .build())
    .trello(NotificationTrelloArgs.builder()
        .active(false)
        .alertingProfile("string")
        .applicationKey("string")
        .boardId("string")
        .description("string")
        .listId("string")
        .name("string")
        .resolvedListId("string")
        .text("string")
        .authorizationToken("string")
        .unknowns("string")
        .build())
    .victorOps(NotificationVictorOpsArgs.builder()
        .active(false)
        .alertingProfile("string")
        .message("string")
        .name("string")
        .routingKey("string")
        .apiKey("string")
        .unknowns("string")
        .build())
    .webHook(NotificationWebHookArgs.builder()
        .acceptAnyCertificate(false)
        .active(false)
        .alertingProfile("string")
        .name("string")
        .payload("string")
        .url("string")
        .headers(NotificationWebHookHeaderArgs.builder()
            .name("string")
            .value("string")
            .build())
        .notifyEventMerges(false)
        .unknowns("string")
        .build())
    .xmatters(NotificationXmattersArgs.builder()
        .acceptAnyCertificate(false)
        .active(false)
        .alertingProfile("string")
        .name("string")
        .payload("string")
        .url("string")
        .headers(NotificationXmattersHeaderArgs.builder()
            .name("string")
            .value("string")
            .build())
        .unknowns("string")
        .build())
    .build());
notification_resource = dynatrace.Notification("notificationResource",
    ansible_tower={
        "accept_any_certificate": False,
        "active": False,
        "alerting_profile": "string",
        "custom_message": "string",
        "job_template_id": 0,
        "job_template_url": "string",
        "name": "string",
        "username": "string",
        "password": "string",
        "unknowns": "string",
    },
    config={
        "active": False,
        "alerting_profile": "string",
        "name": "string",
        "type": "string",
        "unknowns": "string",
    },
    email={
        "active": False,
        "alerting_profile": "string",
        "body": "string",
        "name": "string",
        "subject": "string",
        "bcc_receivers": ["string"],
        "cc_receivers": ["string"],
        "receivers": ["string"],
        "unknowns": "string",
    },
    jira={
        "active": False,
        "alerting_profile": "string",
        "description": "string",
        "issue_type": "string",
        "name": "string",
        "project_key": "string",
        "summary": "string",
        "url": "string",
        "username": "string",
        "password": "string",
        "unknowns": "string",
    },
    ops_genie={
        "active": False,
        "alerting_profile": "string",
        "domain": "string",
        "message": "string",
        "name": "string",
        "api_key": "string",
        "unknowns": "string",
    },
    pager_duty={
        "account": "string",
        "active": False,
        "alerting_profile": "string",
        "name": "string",
        "service_name": "string",
        "service_api_key": "string",
        "unknowns": "string",
    },
    service_now={
        "active": False,
        "alerting_profile": "string",
        "message": "string",
        "name": "string",
        "send_events": False,
        "send_incidents": False,
        "username": "string",
        "instance_name": "string",
        "password": "string",
        "unknowns": "string",
        "url": "string",
    },
    slack={
        "active": False,
        "alerting_profile": "string",
        "channel": "string",
        "name": "string",
        "title": "string",
        "unknowns": "string",
        "url": "string",
    },
    trello={
        "active": False,
        "alerting_profile": "string",
        "application_key": "string",
        "board_id": "string",
        "description": "string",
        "list_id": "string",
        "name": "string",
        "resolved_list_id": "string",
        "text": "string",
        "authorization_token": "string",
        "unknowns": "string",
    },
    victor_ops={
        "active": False,
        "alerting_profile": "string",
        "message": "string",
        "name": "string",
        "routing_key": "string",
        "api_key": "string",
        "unknowns": "string",
    },
    web_hook={
        "accept_any_certificate": False,
        "active": False,
        "alerting_profile": "string",
        "name": "string",
        "payload": "string",
        "url": "string",
        "headers": [{
            "name": "string",
            "value": "string",
        }],
        "notify_event_merges": False,
        "unknowns": "string",
    },
    xmatters={
        "accept_any_certificate": False,
        "active": False,
        "alerting_profile": "string",
        "name": "string",
        "payload": "string",
        "url": "string",
        "headers": [{
            "name": "string",
            "value": "string",
        }],
        "unknowns": "string",
    })
const notificationResource = new dynatrace.Notification("notificationResource", {
    ansibleTower: {
        acceptAnyCertificate: false,
        active: false,
        alertingProfile: "string",
        customMessage: "string",
        jobTemplateId: 0,
        jobTemplateUrl: "string",
        name: "string",
        username: "string",
        password: "string",
        unknowns: "string",
    },
    config: {
        active: false,
        alertingProfile: "string",
        name: "string",
        type: "string",
        unknowns: "string",
    },
    email: {
        active: false,
        alertingProfile: "string",
        body: "string",
        name: "string",
        subject: "string",
        bccReceivers: ["string"],
        ccReceivers: ["string"],
        receivers: ["string"],
        unknowns: "string",
    },
    jira: {
        active: false,
        alertingProfile: "string",
        description: "string",
        issueType: "string",
        name: "string",
        projectKey: "string",
        summary: "string",
        url: "string",
        username: "string",
        password: "string",
        unknowns: "string",
    },
    opsGenie: {
        active: false,
        alertingProfile: "string",
        domain: "string",
        message: "string",
        name: "string",
        apiKey: "string",
        unknowns: "string",
    },
    pagerDuty: {
        account: "string",
        active: false,
        alertingProfile: "string",
        name: "string",
        serviceName: "string",
        serviceApiKey: "string",
        unknowns: "string",
    },
    serviceNow: {
        active: false,
        alertingProfile: "string",
        message: "string",
        name: "string",
        sendEvents: false,
        sendIncidents: false,
        username: "string",
        instanceName: "string",
        password: "string",
        unknowns: "string",
        url: "string",
    },
    slack: {
        active: false,
        alertingProfile: "string",
        channel: "string",
        name: "string",
        title: "string",
        unknowns: "string",
        url: "string",
    },
    trello: {
        active: false,
        alertingProfile: "string",
        applicationKey: "string",
        boardId: "string",
        description: "string",
        listId: "string",
        name: "string",
        resolvedListId: "string",
        text: "string",
        authorizationToken: "string",
        unknowns: "string",
    },
    victorOps: {
        active: false,
        alertingProfile: "string",
        message: "string",
        name: "string",
        routingKey: "string",
        apiKey: "string",
        unknowns: "string",
    },
    webHook: {
        acceptAnyCertificate: false,
        active: false,
        alertingProfile: "string",
        name: "string",
        payload: "string",
        url: "string",
        headers: [{
            name: "string",
            value: "string",
        }],
        notifyEventMerges: false,
        unknowns: "string",
    },
    xmatters: {
        acceptAnyCertificate: false,
        active: false,
        alertingProfile: "string",
        name: "string",
        payload: "string",
        url: "string",
        headers: [{
            name: "string",
            value: "string",
        }],
        unknowns: "string",
    },
});
type: dynatrace:Notification
properties:
    ansibleTower:
        acceptAnyCertificate: false
        active: false
        alertingProfile: string
        customMessage: string
        jobTemplateId: 0
        jobTemplateUrl: string
        name: string
        password: string
        unknowns: string
        username: string
    config:
        active: false
        alertingProfile: string
        name: string
        type: string
        unknowns: string
    email:
        active: false
        alertingProfile: string
        bccReceivers:
            - string
        body: string
        ccReceivers:
            - string
        name: string
        receivers:
            - string
        subject: string
        unknowns: string
    jira:
        active: false
        alertingProfile: string
        description: string
        issueType: string
        name: string
        password: string
        projectKey: string
        summary: string
        unknowns: string
        url: string
        username: string
    opsGenie:
        active: false
        alertingProfile: string
        apiKey: string
        domain: string
        message: string
        name: string
        unknowns: string
    pagerDuty:
        account: string
        active: false
        alertingProfile: string
        name: string
        serviceApiKey: string
        serviceName: string
        unknowns: string
    serviceNow:
        active: false
        alertingProfile: string
        instanceName: string
        message: string
        name: string
        password: string
        sendEvents: false
        sendIncidents: false
        unknowns: string
        url: string
        username: string
    slack:
        active: false
        alertingProfile: string
        channel: string
        name: string
        title: string
        unknowns: string
        url: string
    trello:
        active: false
        alertingProfile: string
        applicationKey: string
        authorizationToken: string
        boardId: string
        description: string
        listId: string
        name: string
        resolvedListId: string
        text: string
        unknowns: string
    victorOps:
        active: false
        alertingProfile: string
        apiKey: string
        message: string
        name: string
        routingKey: string
        unknowns: string
    webHook:
        acceptAnyCertificate: false
        active: false
        alertingProfile: string
        headers:
            - name: string
              value: string
        name: string
        notifyEventMerges: false
        payload: string
        unknowns: string
        url: string
    xmatters:
        acceptAnyCertificate: false
        active: false
        alertingProfile: string
        headers:
            - name: string
              value: string
        name: string
        payload: string
        unknowns: string
        url: string
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
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The Notification resource accepts the following input properties:
- AnsibleTower Pulumiverse.Dynatrace. Inputs. Notification Ansible Tower 
- Configuration for Ansible Tower Notification
- Config
Pulumiverse.Dynatrace. Inputs. Notification Config 
- Configuration for Generic Notification
- Email
Pulumiverse.Dynatrace. Inputs. Notification Email 
- Configuration for Email Notification
- Jira
Pulumiverse.Dynatrace. Inputs. Notification Jira 
- Configuration for Jira Notification
- OpsGenie Pulumiverse.Dynatrace. Inputs. Notification Ops Genie 
- Configuration for OpsGenie Notification
- PagerDuty Pulumiverse.Dynatrace. Inputs. Notification Pager Duty 
- Configuration for PagerDuty Notification
- ServiceNow Pulumiverse.Dynatrace. Inputs. Notification Service Now 
- Configuration for ServiceNow Notification
- Slack
Pulumiverse.Dynatrace. Inputs. Notification Slack 
- Configuration for Slack Notification
- Trello
Pulumiverse.Dynatrace. Inputs. Notification Trello 
- Configuration for Trello Notification
- VictorOps Pulumiverse.Dynatrace. Inputs. Notification Victor Ops 
- Configuration for VictorOps Notification
- WebHook Pulumiverse.Dynatrace. Inputs. Notification Web Hook 
- Configuration for WebHook Notification
- Xmatters
Pulumiverse.Dynatrace. Inputs. Notification Xmatters 
- Configuration for XMatters Notification
- AnsibleTower NotificationAnsible Tower Args 
- Configuration for Ansible Tower Notification
- Config
NotificationConfig Args 
- Configuration for Generic Notification
- Email
NotificationEmail Args 
- Configuration for Email Notification
- Jira
NotificationJira Args 
- Configuration for Jira Notification
- OpsGenie NotificationOps Genie Args 
- Configuration for OpsGenie Notification
- PagerDuty NotificationPager Duty Args 
- Configuration for PagerDuty Notification
- ServiceNow NotificationService Now Args 
- Configuration for ServiceNow Notification
- Slack
NotificationSlack Args 
- Configuration for Slack Notification
- Trello
NotificationTrello Args 
- Configuration for Trello Notification
- VictorOps NotificationVictor Ops Args 
- Configuration for VictorOps Notification
- WebHook NotificationWeb Hook Args 
- Configuration for WebHook Notification
- Xmatters
NotificationXmatters Args 
- Configuration for XMatters Notification
- ansibleTower NotificationAnsible Tower 
- Configuration for Ansible Tower Notification
- config
NotificationConfig 
- Configuration for Generic Notification
- email
NotificationEmail 
- Configuration for Email Notification
- jira
NotificationJira 
- Configuration for Jira Notification
- opsGenie NotificationOps Genie 
- Configuration for OpsGenie Notification
- pagerDuty NotificationPager Duty 
- Configuration for PagerDuty Notification
- serviceNow NotificationService Now 
- Configuration for ServiceNow Notification
- slack
NotificationSlack 
- Configuration for Slack Notification
- trello
NotificationTrello 
- Configuration for Trello Notification
- victorOps NotificationVictor Ops 
- Configuration for VictorOps Notification
- webHook NotificationWeb Hook 
- Configuration for WebHook Notification
- xmatters
NotificationXmatters 
- Configuration for XMatters Notification
- ansibleTower NotificationAnsible Tower 
- Configuration for Ansible Tower Notification
- config
NotificationConfig 
- Configuration for Generic Notification
- email
NotificationEmail 
- Configuration for Email Notification
- jira
NotificationJira 
- Configuration for Jira Notification
- opsGenie NotificationOps Genie 
- Configuration for OpsGenie Notification
- pagerDuty NotificationPager Duty 
- Configuration for PagerDuty Notification
- serviceNow NotificationService Now 
- Configuration for ServiceNow Notification
- slack
NotificationSlack 
- Configuration for Slack Notification
- trello
NotificationTrello 
- Configuration for Trello Notification
- victorOps NotificationVictor Ops 
- Configuration for VictorOps Notification
- webHook NotificationWeb Hook 
- Configuration for WebHook Notification
- xmatters
NotificationXmatters 
- Configuration for XMatters Notification
- ansible_tower NotificationAnsible Tower Args 
- Configuration for Ansible Tower Notification
- config
NotificationConfig Args 
- Configuration for Generic Notification
- email
NotificationEmail Args 
- Configuration for Email Notification
- jira
NotificationJira Args 
- Configuration for Jira Notification
- ops_genie NotificationOps Genie Args 
- Configuration for OpsGenie Notification
- pager_duty NotificationPager Duty Args 
- Configuration for PagerDuty Notification
- service_now NotificationService Now Args 
- Configuration for ServiceNow Notification
- slack
NotificationSlack Args 
- Configuration for Slack Notification
- trello
NotificationTrello Args 
- Configuration for Trello Notification
- victor_ops NotificationVictor Ops Args 
- Configuration for VictorOps Notification
- web_hook NotificationWeb Hook Args 
- Configuration for WebHook Notification
- xmatters
NotificationXmatters Args 
- 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
- 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,
        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) -> Notificationfunc 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.
- AnsibleTower Pulumiverse.Dynatrace. Inputs. Notification Ansible Tower 
- Configuration for Ansible Tower Notification
- Config
Pulumiverse.Dynatrace. Inputs. Notification Config 
- Configuration for Generic Notification
- Email
Pulumiverse.Dynatrace. Inputs. Notification Email 
- Configuration for Email Notification
- Jira
Pulumiverse.Dynatrace. Inputs. Notification Jira 
- Configuration for Jira Notification
- OpsGenie Pulumiverse.Dynatrace. Inputs. Notification Ops Genie 
- Configuration for OpsGenie Notification
- PagerDuty Pulumiverse.Dynatrace. Inputs. Notification Pager Duty 
- Configuration for PagerDuty Notification
- ServiceNow Pulumiverse.Dynatrace. Inputs. Notification Service Now 
- Configuration for ServiceNow Notification
- Slack
Pulumiverse.Dynatrace. Inputs. Notification Slack 
- Configuration for Slack Notification
- Trello
Pulumiverse.Dynatrace. Inputs. Notification Trello 
- Configuration for Trello Notification
- VictorOps Pulumiverse.Dynatrace. Inputs. Notification Victor Ops 
- Configuration for VictorOps Notification
- WebHook Pulumiverse.Dynatrace. Inputs. Notification Web Hook 
- Configuration for WebHook Notification
- Xmatters
Pulumiverse.Dynatrace. Inputs. Notification Xmatters 
- Configuration for XMatters Notification
- AnsibleTower NotificationAnsible Tower Args 
- Configuration for Ansible Tower Notification
- Config
NotificationConfig Args 
- Configuration for Generic Notification
- Email
NotificationEmail Args 
- Configuration for Email Notification
- Jira
NotificationJira Args 
- Configuration for Jira Notification
- OpsGenie NotificationOps Genie Args 
- Configuration for OpsGenie Notification
- PagerDuty NotificationPager Duty Args 
- Configuration for PagerDuty Notification
- ServiceNow NotificationService Now Args 
- Configuration for ServiceNow Notification
- Slack
NotificationSlack Args 
- Configuration for Slack Notification
- Trello
NotificationTrello Args 
- Configuration for Trello Notification
- VictorOps NotificationVictor Ops Args 
- Configuration for VictorOps Notification
- WebHook NotificationWeb Hook Args 
- Configuration for WebHook Notification
- Xmatters
NotificationXmatters Args 
- Configuration for XMatters Notification
- ansibleTower NotificationAnsible Tower 
- Configuration for Ansible Tower Notification
- config
NotificationConfig 
- Configuration for Generic Notification
- email
NotificationEmail 
- Configuration for Email Notification
- jira
NotificationJira 
- Configuration for Jira Notification
- opsGenie NotificationOps Genie 
- Configuration for OpsGenie Notification
- pagerDuty NotificationPager Duty 
- Configuration for PagerDuty Notification
- serviceNow NotificationService Now 
- Configuration for ServiceNow Notification
- slack
NotificationSlack 
- Configuration for Slack Notification
- trello
NotificationTrello 
- Configuration for Trello Notification
- victorOps NotificationVictor Ops 
- Configuration for VictorOps Notification
- webHook NotificationWeb Hook 
- Configuration for WebHook Notification
- xmatters
NotificationXmatters 
- Configuration for XMatters Notification
- ansibleTower NotificationAnsible Tower 
- Configuration for Ansible Tower Notification
- config
NotificationConfig 
- Configuration for Generic Notification
- email
NotificationEmail 
- Configuration for Email Notification
- jira
NotificationJira 
- Configuration for Jira Notification
- opsGenie NotificationOps Genie 
- Configuration for OpsGenie Notification
- pagerDuty NotificationPager Duty 
- Configuration for PagerDuty Notification
- serviceNow NotificationService Now 
- Configuration for ServiceNow Notification
- slack
NotificationSlack 
- Configuration for Slack Notification
- trello
NotificationTrello 
- Configuration for Trello Notification
- victorOps NotificationVictor Ops 
- Configuration for VictorOps Notification
- webHook NotificationWeb Hook 
- Configuration for WebHook Notification
- xmatters
NotificationXmatters 
- Configuration for XMatters Notification
- ansible_tower NotificationAnsible Tower Args 
- Configuration for Ansible Tower Notification
- config
NotificationConfig Args 
- Configuration for Generic Notification
- email
NotificationEmail Args 
- Configuration for Email Notification
- jira
NotificationJira Args 
- Configuration for Jira Notification
- ops_genie NotificationOps Genie Args 
- Configuration for OpsGenie Notification
- pager_duty NotificationPager Duty Args 
- Configuration for PagerDuty Notification
- service_now NotificationService Now Args 
- Configuration for ServiceNow Notification
- slack
NotificationSlack Args 
- Configuration for Slack Notification
- trello
NotificationTrello Args 
- Configuration for Trello Notification
- victor_ops NotificationVictor Ops Args 
- Configuration for VictorOps Notification
- web_hook NotificationWeb Hook Args 
- Configuration for WebHook Notification
- xmatters
NotificationXmatters Args 
- 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
- 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, NotificationAnsibleTowerArgs      
- AcceptAny boolCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- JobTemplate intId 
- The ID of the target Ansible Tower job template
- JobTemplate stringUrl 
- 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
- AcceptAny boolCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- JobTemplate intId 
- The ID of the target Ansible Tower job template
- JobTemplate stringUrl 
- 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
- acceptAny BooleanCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- jobTemplate IntegerId 
- The ID of the target Ansible Tower job template
- jobTemplate StringUrl 
- 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
- acceptAny booleanCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- jobTemplate numberId 
- The ID of the target Ansible Tower job template
- jobTemplate stringUrl 
- 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_ boolcertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- job_template_ intid 
- The ID of the target Ansible Tower job template
- job_template_ strurl 
- 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
- acceptAny BooleanCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- jobTemplate NumberId 
- The ID of the target Ansible Tower job template
- jobTemplate StringUrl 
- 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, NotificationConfigArgs    
- 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, NotificationEmailArgs    
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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
NotificationJira, NotificationJiraArgs    
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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, NotificationOpsGenieArgs      
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_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, NotificationPagerDutyArgs      
- 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
- ServiceApi stringKey 
- 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
- ServiceApi stringKey 
- 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
- serviceApi StringKey 
- 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
- serviceApi stringKey 
- 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_ strkey 
- 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
- serviceApi StringKey 
- 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, NotificationServiceNowArgs      
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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, andx_dynat_ruxit.Integrationroles
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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, andx_dynat_ruxit.Integrationroles
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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, andx_dynat_ruxit.Integrationroles
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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, andx_dynat_ruxit.Integrationroles
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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, andx_dynat_ruxit.Integrationroles
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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, andx_dynat_ruxit.Integrationroles
- 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, NotificationSlackArgs    
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 nullvalue, 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 nullvalue, 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 nullvalue, 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 nullvalue, 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 nullvalue, 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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 nullvalue, and it is optional for PUT requests
NotificationTrello, NotificationTrelloArgs    
- 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
- ResolvedList stringId 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- 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
- ResolvedList stringId 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- 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
- resolvedList StringId 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- 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
- resolvedList stringId 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- 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_ strid 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- 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
- resolvedList StringId 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- 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, NotificationVictorOpsArgs      
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED
- 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, NotificationWebHookArgs      
- AcceptAny boolCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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<Pulumiverse.Dynatrace. Inputs. Notification Web Hook Header> 
- A list of the additional HTTP headers
- NotifyEvent boolMerges 
- 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
- AcceptAny boolCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- Url string
- The URL of the WebHook endpoint
- Headers
[]NotificationWeb Hook Header 
- A list of the additional HTTP headers
- NotifyEvent boolMerges 
- 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
- acceptAny BooleanCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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<NotificationWeb Hook Header> 
- A list of the additional HTTP headers
- notifyEvent BooleanMerges 
- 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
- acceptAny booleanCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- url string
- The URL of the WebHook endpoint
- headers
NotificationWeb Hook Header[] 
- A list of the additional HTTP headers
- notifyEvent booleanMerges 
- 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_ boolcertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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[NotificationWeb Hook Header] 
- A list of the additional HTTP headers
- notify_event_ boolmerges 
- 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
- acceptAny BooleanCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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
- notifyEvent BooleanMerges 
- 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, NotificationWebHookHeaderArgs        
- Name string
- The name of the HTTP header
- Value string
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- Name string
- The name of the HTTP header
- Value string
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- name String
- The name of the HTTP header
- value String
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- name string
- The name of the HTTP header
- value string
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- name str
- The name of the HTTP header
- value str
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- name String
- The name of the HTTP header
- value String
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
NotificationXmatters, NotificationXmattersArgs    
- AcceptAny boolCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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<Pulumiverse.Dynatrace. Inputs. Notification Xmatters Header> 
- 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
- AcceptAny boolCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- Url string
- The URL of the xMatters WebHook
- Headers
[]NotificationXmatters Header 
- 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
- acceptAny BooleanCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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<NotificationXmatters Header> 
- 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
- acceptAny booleanCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{Tags}: The list of tags that are defined for all impacted entities, separated by commas
- url string
- The URL of the xMatters WebHook
- headers
NotificationXmatters Header[] 
- 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_ boolcertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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[NotificationXmatters Header] 
- 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
- acceptAny BooleanCertificate 
- 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 areAPPLICATION,SERVICE, andINFRASTRUCTURE. *{ProblemSeverity}: The severity level of the problem. Possible values areAVAILABILITY,ERROR,PERFORMANCE,RESOURCE_CONTENTION, andCUSTOM_ALERT. *{ProblemTitle}: A short description of the problem. *{ProblemURL}: The URL of the problem within Dynatrace. *{State}: The state of the problem. Possible values areOPENandRESOLVED. *{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, NotificationXmattersHeaderArgs      
- Name string
- The name of the HTTP header
- Value string
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- Name string
- The name of the HTTP header
- Value string
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- name String
- The name of the HTTP header
- value String
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- name string
- The name of the HTTP header
- value string
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- name str
- The name of the HTTP header
- value str
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
- name String
- The name of the HTTP header
- value String
- The value of the HTTP header. May contain an empty value. Required when creating a new notification. For the Authorization header, GET requests return the nullvalue. If you want update a notification configuration with an Authorization header which you want to remain intact, set the Authorization header with thenullvalue
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the dynatraceTerraform Provider.
