Dynatrace v0.16.0 published on Tuesday, Sep 10, 2024 by Pulumiverse
dynatrace.AnsibleTowerNotification
Explore with Pulumi AI
Create AnsibleTowerNotification Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new AnsibleTowerNotification(name: string, args: AnsibleTowerNotificationArgs, opts?: CustomResourceOptions);
@overload
def AnsibleTowerNotification(resource_name: str,
args: AnsibleTowerNotificationArgs,
opts: Optional[ResourceOptions] = None)
@overload
def AnsibleTowerNotification(resource_name: str,
opts: Optional[ResourceOptions] = None,
custom_message: Optional[str] = None,
job_template_url: Optional[str] = None,
profile: Optional[str] = None,
username: Optional[str] = None,
active: Optional[bool] = None,
insecure: Optional[bool] = None,
legacy_id: Optional[str] = None,
name: Optional[str] = None,
password: Optional[str] = None)
func NewAnsibleTowerNotification(ctx *Context, name string, args AnsibleTowerNotificationArgs, opts ...ResourceOption) (*AnsibleTowerNotification, error)
public AnsibleTowerNotification(string name, AnsibleTowerNotificationArgs args, CustomResourceOptions? opts = null)
public AnsibleTowerNotification(String name, AnsibleTowerNotificationArgs args)
public AnsibleTowerNotification(String name, AnsibleTowerNotificationArgs args, CustomResourceOptions options)
type: dynatrace:AnsibleTowerNotification
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 AnsibleTowerNotificationArgs
- 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 AnsibleTowerNotificationArgs
- 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 AnsibleTowerNotificationArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args AnsibleTowerNotificationArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args AnsibleTowerNotificationArgs
- 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 ansibleTowerNotificationResource = new Dynatrace.AnsibleTowerNotification("ansibleTowerNotificationResource", new()
{
CustomMessage = "string",
JobTemplateUrl = "string",
Profile = "string",
Username = "string",
Active = false,
Insecure = false,
LegacyId = "string",
Name = "string",
Password = "string",
});
example, err := dynatrace.NewAnsibleTowerNotification(ctx, "ansibleTowerNotificationResource", &dynatrace.AnsibleTowerNotificationArgs{
CustomMessage: pulumi.String("string"),
JobTemplateUrl: pulumi.String("string"),
Profile: pulumi.String("string"),
Username: pulumi.String("string"),
Active: pulumi.Bool(false),
Insecure: pulumi.Bool(false),
LegacyId: pulumi.String("string"),
Name: pulumi.String("string"),
Password: pulumi.String("string"),
})
var ansibleTowerNotificationResource = new AnsibleTowerNotification("ansibleTowerNotificationResource", AnsibleTowerNotificationArgs.builder()
.customMessage("string")
.jobTemplateUrl("string")
.profile("string")
.username("string")
.active(false)
.insecure(false)
.legacyId("string")
.name("string")
.password("string")
.build());
ansible_tower_notification_resource = dynatrace.AnsibleTowerNotification("ansibleTowerNotificationResource",
custom_message="string",
job_template_url="string",
profile="string",
username="string",
active=False,
insecure=False,
legacy_id="string",
name="string",
password="string")
const ansibleTowerNotificationResource = new dynatrace.AnsibleTowerNotification("ansibleTowerNotificationResource", {
customMessage: "string",
jobTemplateUrl: "string",
profile: "string",
username: "string",
active: false,
insecure: false,
legacyId: "string",
name: "string",
password: "string",
});
type: dynatrace:AnsibleTowerNotification
properties:
active: false
customMessage: string
insecure: false
jobTemplateUrl: string
legacyId: string
name: string
password: string
profile: string
username: string
AnsibleTowerNotification Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The AnsibleTowerNotification resource accepts the following input properties:
- Custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - Job
Template stringUrl - The URL of the target Ansible Tower job template
- Profile string
- The ID of the associated alerting profile.
- Username string
- The username of the Ansible Tower account
- Active bool
- The notification is active (
true
) or inactive (false
). Default isfalse
. - Insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - Legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- Name string
- The display name within the Dynatrace WebUI.
- Password string
- The password for the Ansible Tower account
- Custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - Job
Template stringUrl - The URL of the target Ansible Tower job template
- Profile string
- The ID of the associated alerting profile.
- Username string
- The username of the Ansible Tower account
- Active bool
- The notification is active (
true
) or inactive (false
). Default isfalse
. - Insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - Legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- Name string
- The display name within the Dynatrace WebUI.
- Password string
- The password for the Ansible Tower account
- custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - job
Template StringUrl - The URL of the target Ansible Tower job template
- profile String
- The ID of the associated alerting profile.
- username String
- The username of the Ansible Tower account
- active Boolean
- The notification is active (
true
) or inactive (false
). Default isfalse
. - insecure Boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - legacy
Id String - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name String
- The display name within the Dynatrace WebUI.
- password String
- The password for the Ansible Tower account
- custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - job
Template stringUrl - The URL of the target Ansible Tower job template
- profile string
- The ID of the associated alerting profile.
- username string
- The username of the Ansible Tower account
- active boolean
- The notification is active (
true
) or inactive (false
). Default isfalse
. - insecure boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name string
- The display name within the Dynatrace WebUI.
- password string
- The password for the Ansible Tower account
- 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - job_
template_ strurl - The URL of the target Ansible Tower job template
- profile str
- The ID of the associated alerting profile.
- username str
- The username of the Ansible Tower account
- active bool
- The notification is active (
true
) or inactive (false
). Default isfalse
. - insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - legacy_
id str - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name str
- The display name within the Dynatrace WebUI.
- password str
- The password for the Ansible Tower account
- custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - job
Template StringUrl - The URL of the target Ansible Tower job template
- profile String
- The ID of the associated alerting profile.
- username String
- The username of the Ansible Tower account
- active Boolean
- The notification is active (
true
) or inactive (false
). Default isfalse
. - insecure Boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - legacy
Id String - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name String
- The display name within the Dynatrace WebUI.
- password String
- The password for the Ansible Tower account
Outputs
All input properties are implicitly available as output properties. Additionally, the AnsibleTowerNotification 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 AnsibleTowerNotification Resource
Get an existing AnsibleTowerNotification 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?: AnsibleTowerNotificationState, opts?: CustomResourceOptions): AnsibleTowerNotification
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
active: Optional[bool] = None,
custom_message: Optional[str] = None,
insecure: Optional[bool] = None,
job_template_url: Optional[str] = None,
legacy_id: Optional[str] = None,
name: Optional[str] = None,
password: Optional[str] = None,
profile: Optional[str] = None,
username: Optional[str] = None) -> AnsibleTowerNotification
func GetAnsibleTowerNotification(ctx *Context, name string, id IDInput, state *AnsibleTowerNotificationState, opts ...ResourceOption) (*AnsibleTowerNotification, error)
public static AnsibleTowerNotification Get(string name, Input<string> id, AnsibleTowerNotificationState? state, CustomResourceOptions? opts = null)
public static AnsibleTowerNotification get(String name, Output<String> id, AnsibleTowerNotificationState 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.
- Active bool
- The notification is active (
true
) or inactive (false
). Default isfalse
. - Custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - Insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - Job
Template stringUrl - The URL of the target Ansible Tower job template
- Legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- Name string
- The display name within the Dynatrace WebUI.
- Password string
- The password for the Ansible Tower account
- Profile string
- The ID of the associated alerting profile.
- Username string
- The username of the Ansible Tower account
- Active bool
- The notification is active (
true
) or inactive (false
). Default isfalse
. - Custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - Insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - Job
Template stringUrl - The URL of the target Ansible Tower job template
- Legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- Name string
- The display name within the Dynatrace WebUI.
- Password string
- The password for the Ansible Tower account
- Profile string
- The ID of the associated alerting profile.
- Username string
- The username of the Ansible Tower account
- active Boolean
- The notification is active (
true
) or inactive (false
). Default isfalse
. - custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - insecure Boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - job
Template StringUrl - The URL of the target Ansible Tower job template
- legacy
Id String - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name String
- The display name within the Dynatrace WebUI.
- password String
- The password for the Ansible Tower account
- profile String
- The ID of the associated alerting profile.
- username String
- The username of the Ansible Tower account
- active boolean
- The notification is active (
true
) or inactive (false
). Default isfalse
. - custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - insecure boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - job
Template stringUrl - The URL of the target Ansible Tower job template
- legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name string
- The display name within the Dynatrace WebUI.
- password string
- The password for the Ansible Tower account
- profile string
- The ID of the associated alerting profile.
- username string
- The username of the Ansible Tower account
- active bool
- The notification is active (
true
) or inactive (false
). Default isfalse
. - 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - job_
template_ strurl - The URL of the target Ansible Tower job template
- legacy_
id str - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name str
- The display name within the Dynatrace WebUI.
- password str
- The password for the Ansible Tower account
- profile str
- The ID of the associated alerting profile.
- username str
- The username of the Ansible Tower account
- active Boolean
- The notification is active (
true
) or inactive (false
). Default isfalse
. - custom
Message 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - insecure Boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates. Default isfalse
. - job
Template StringUrl - The URL of the target Ansible Tower job template
- legacy
Id String - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name String
- The display name within the Dynatrace WebUI.
- password String
- The password for the Ansible Tower account
- profile String
- The ID of the associated alerting profile.
- username String
- The username of the Ansible Tower account
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dynatrace
Terraform Provider.