dynatrace.JiraNotification
Explore with Pulumi AI
Create JiraNotification Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new JiraNotification(name: string, args: JiraNotificationArgs, opts?: CustomResourceOptions);
@overload
def JiraNotification(resource_name: str,
args: JiraNotificationArgs,
opts: Optional[ResourceOptions] = None)
@overload
def JiraNotification(resource_name: str,
opts: Optional[ResourceOptions] = None,
active: Optional[bool] = None,
description: Optional[str] = None,
issue_type: Optional[str] = None,
profile: Optional[str] = None,
project_key: Optional[str] = None,
summary: Optional[str] = None,
url: Optional[str] = None,
username: Optional[str] = None,
api_token: Optional[str] = None,
legacy_id: Optional[str] = None,
name: Optional[str] = None)
func NewJiraNotification(ctx *Context, name string, args JiraNotificationArgs, opts ...ResourceOption) (*JiraNotification, error)
public JiraNotification(string name, JiraNotificationArgs args, CustomResourceOptions? opts = null)
public JiraNotification(String name, JiraNotificationArgs args)
public JiraNotification(String name, JiraNotificationArgs args, CustomResourceOptions options)
type: dynatrace:JiraNotification
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 JiraNotificationArgs
- 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 JiraNotificationArgs
- 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 JiraNotificationArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args JiraNotificationArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args JiraNotificationArgs
- 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 jiraNotificationResource = new Dynatrace.JiraNotification("jiraNotificationResource", new()
{
Active = false,
Description = "string",
IssueType = "string",
Profile = "string",
ProjectKey = "string",
Summary = "string",
Url = "string",
Username = "string",
ApiToken = "string",
LegacyId = "string",
Name = "string",
});
example, err := dynatrace.NewJiraNotification(ctx, "jiraNotificationResource", &dynatrace.JiraNotificationArgs{
Active: pulumi.Bool(false),
Description: pulumi.String("string"),
IssueType: pulumi.String("string"),
Profile: pulumi.String("string"),
ProjectKey: pulumi.String("string"),
Summary: pulumi.String("string"),
Url: pulumi.String("string"),
Username: pulumi.String("string"),
ApiToken: pulumi.String("string"),
LegacyId: pulumi.String("string"),
Name: pulumi.String("string"),
})
var jiraNotificationResource = new JiraNotification("jiraNotificationResource", JiraNotificationArgs.builder()
.active(false)
.description("string")
.issueType("string")
.profile("string")
.projectKey("string")
.summary("string")
.url("string")
.username("string")
.apiToken("string")
.legacyId("string")
.name("string")
.build());
jira_notification_resource = dynatrace.JiraNotification("jiraNotificationResource",
active=False,
description="string",
issue_type="string",
profile="string",
project_key="string",
summary="string",
url="string",
username="string",
api_token="string",
legacy_id="string",
name="string")
const jiraNotificationResource = new dynatrace.JiraNotification("jiraNotificationResource", {
active: false,
description: "string",
issueType: "string",
profile: "string",
projectKey: "string",
summary: "string",
url: "string",
username: "string",
apiToken: "string",
legacyId: "string",
name: "string",
});
type: dynatrace:JiraNotification
properties:
active: false
apiToken: string
description: string
issueType: string
legacyId: string
name: string
profile: string
projectKey: string
summary: string
url: string
username: string
JiraNotification 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 JiraNotification resource accepts the following input properties:
- Active bool
- The configuration is enabled (
true
) or disabled (false
) - Description string
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- Issue
Type string - The type of the Jira issue to be created by this notification
- Profile string
- The ID of the associated alerting profile
- Project
Key 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 areOPEN
andRESOLVED
. *{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
- Api
Token string - The API token for the Jira profile. Using password authentication was deprecated by Jira
- Legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- Name string
- The name of the notification configuration
- Active bool
- The configuration is enabled (
true
) or disabled (false
) - Description string
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- Issue
Type string - The type of the Jira issue to be created by this notification
- Profile string
- The ID of the associated alerting profile
- Project
Key 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 areOPEN
andRESOLVED
. *{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
- Api
Token string - The API token for the Jira profile. Using password authentication was deprecated by Jira
- Legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- Name string
- The name of the notification configuration
- active Boolean
- The configuration is enabled (
true
) or disabled (false
) - description String
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- issue
Type String - The type of the Jira issue to be created by this notification
- profile String
- The ID of the associated alerting profile
- project
Key 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 areOPEN
andRESOLVED
. *{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
- api
Token String - The API token for the Jira profile. Using password authentication was deprecated by Jira
- legacy
Id String - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name String
- The name of the notification configuration
- active boolean
- The configuration is enabled (
true
) or disabled (false
) - description string
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- issue
Type string - The type of the Jira issue to be created by this notification
- profile string
- The ID of the associated alerting profile
- project
Key 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 areOPEN
andRESOLVED
. *{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
- api
Token string - The API token for the Jira profile. Using password authentication was deprecated by Jira
- legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name string
- The name of the notification configuration
- active bool
- The configuration is enabled (
true
) or disabled (false
) - 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
- profile str
- The ID of the associated alerting profile
- 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 areOPEN
andRESOLVED
. *{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
- api_
token str - The API token for the Jira profile. Using password authentication was deprecated by Jira
- legacy_
id str - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name str
- The name of the notification configuration
- active Boolean
- The configuration is enabled (
true
) or disabled (false
) - description String
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- issue
Type String - The type of the Jira issue to be created by this notification
- profile String
- The ID of the associated alerting profile
- project
Key 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 areOPEN
andRESOLVED
. *{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
- api
Token String - The API token for the Jira profile. Using password authentication was deprecated by Jira
- legacy
Id String - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name String
- The name of the notification configuration
Outputs
All input properties are implicitly available as output properties. Additionally, the JiraNotification 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 JiraNotification Resource
Get an existing JiraNotification 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?: JiraNotificationState, opts?: CustomResourceOptions): JiraNotification
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
active: Optional[bool] = None,
api_token: Optional[str] = None,
description: Optional[str] = None,
issue_type: Optional[str] = None,
legacy_id: Optional[str] = None,
name: Optional[str] = None,
profile: Optional[str] = None,
project_key: Optional[str] = None,
summary: Optional[str] = None,
url: Optional[str] = None,
username: Optional[str] = None) -> JiraNotification
func GetJiraNotification(ctx *Context, name string, id IDInput, state *JiraNotificationState, opts ...ResourceOption) (*JiraNotification, error)
public static JiraNotification Get(string name, Input<string> id, JiraNotificationState? state, CustomResourceOptions? opts = null)
public static JiraNotification get(String name, Output<String> id, JiraNotificationState 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 configuration is enabled (
true
) or disabled (false
) - Api
Token string - The API token for the Jira profile. Using password authentication was deprecated by Jira
- Description string
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- Issue
Type string - The type of the Jira issue to be created by this notification
- Legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- Name string
- The name of the notification configuration
- Profile string
- The ID of the associated alerting profile
- Project
Key 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 areOPEN
andRESOLVED
. *{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
- Active bool
- The configuration is enabled (
true
) or disabled (false
) - Api
Token string - The API token for the Jira profile. Using password authentication was deprecated by Jira
- Description string
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- Issue
Type string - The type of the Jira issue to be created by this notification
- Legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- Name string
- The name of the notification configuration
- Profile string
- The ID of the associated alerting profile
- Project
Key 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 areOPEN
andRESOLVED
. *{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
- active Boolean
- The configuration is enabled (
true
) or disabled (false
) - api
Token String - The API token for the Jira profile. Using password authentication was deprecated by Jira
- description String
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- issue
Type String - The type of the Jira issue to be created by this notification
- legacy
Id String - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name String
- The name of the notification configuration
- profile String
- The ID of the associated alerting profile
- project
Key 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 areOPEN
andRESOLVED
. *{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
- active boolean
- The configuration is enabled (
true
) or disabled (false
) - api
Token string - The API token for the Jira profile. Using password authentication was deprecated by Jira
- description string
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- issue
Type string - The type of the Jira issue to be created by this notification
- legacy
Id string - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name string
- The name of the notification configuration
- profile string
- The ID of the associated alerting profile
- project
Key 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 areOPEN
andRESOLVED
. *{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
- active bool
- The configuration is enabled (
true
) or disabled (false
) - api_
token str - The API token for the Jira profile. Using password authentication was deprecated by Jira
- 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
- legacy_
id str - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name str
- The name of the notification configuration
- profile str
- The ID of the associated alerting profile
- 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 areOPEN
andRESOLVED
. *{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
- active Boolean
- The configuration is enabled (
true
) or disabled (false
) - api
Token String - The API token for the Jira profile. Using password authentication was deprecated by Jira
- description String
- The description of the Jira issue to be created by this notification. You can use same placeholders as in issue summary
- issue
Type String - The type of the Jira issue to be created by this notification
- legacy
Id String - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name String
- The name of the notification configuration
- profile String
- The ID of the associated alerting profile
- project
Key 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 areOPEN
andRESOLVED
. *{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
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dynatrace
Terraform Provider.