dynatrace.WebhookNotification
Explore with Pulumi AI
Create WebhookNotification Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new WebhookNotification(name: string, args: WebhookNotificationArgs, opts?: CustomResourceOptions);
@overload
def WebhookNotification(resource_name: str,
args: WebhookNotificationArgs,
opts: Optional[ResourceOptions] = None)
@overload
def WebhookNotification(resource_name: str,
opts: Optional[ResourceOptions] = None,
active: Optional[bool] = None,
profile: Optional[str] = None,
payload: Optional[str] = None,
legacy_id: Optional[str] = None,
name: Optional[str] = None,
notify_closed_problems: Optional[bool] = None,
notify_event_merges: Optional[bool] = None,
oauth2_credentials: Optional[WebhookNotificationOauth2CredentialsArgs] = None,
insecure: Optional[bool] = None,
headers: Optional[WebhookNotificationHeadersArgs] = None,
secret_url: Optional[str] = None,
url: Optional[str] = None,
url_contains_secret: Optional[bool] = None,
use_oauth2: Optional[bool] = None)
func NewWebhookNotification(ctx *Context, name string, args WebhookNotificationArgs, opts ...ResourceOption) (*WebhookNotification, error)
public WebhookNotification(string name, WebhookNotificationArgs args, CustomResourceOptions? opts = null)
public WebhookNotification(String name, WebhookNotificationArgs args)
public WebhookNotification(String name, WebhookNotificationArgs args, CustomResourceOptions options)
type: dynatrace:WebhookNotification
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 WebhookNotificationArgs
- 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 WebhookNotificationArgs
- 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 WebhookNotificationArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args WebhookNotificationArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args WebhookNotificationArgs
- 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 webhookNotificationResource = new Dynatrace.WebhookNotification("webhookNotificationResource", new()
{
Active = false,
Profile = "string",
Payload = "string",
LegacyId = "string",
Name = "string",
NotifyClosedProblems = false,
NotifyEventMerges = false,
Oauth2Credentials = new Dynatrace.Inputs.WebhookNotificationOauth2CredentialsArgs
{
AccessTokenUrl = "string",
ClientId = "string",
ClientSecret = "string",
AuthenticateViaRequestHeader = false,
Scope = "string",
},
Insecure = false,
Headers = new Dynatrace.Inputs.WebhookNotificationHeadersArgs
{
Headers = new[]
{
new Dynatrace.Inputs.WebhookNotificationHeadersHeaderArgs
{
Name = "string",
SecretValue = "string",
Value = "string",
},
},
},
SecretUrl = "string",
Url = "string",
UrlContainsSecret = false,
UseOauth2 = false,
});
example, err := dynatrace.NewWebhookNotification(ctx, "webhookNotificationResource", &dynatrace.WebhookNotificationArgs{
Active: pulumi.Bool(false),
Profile: pulumi.String("string"),
Payload: pulumi.String("string"),
LegacyId: pulumi.String("string"),
Name: pulumi.String("string"),
NotifyClosedProblems: pulumi.Bool(false),
NotifyEventMerges: pulumi.Bool(false),
Oauth2Credentials: &dynatrace.WebhookNotificationOauth2CredentialsArgs{
AccessTokenUrl: pulumi.String("string"),
ClientId: pulumi.String("string"),
ClientSecret: pulumi.String("string"),
AuthenticateViaRequestHeader: pulumi.Bool(false),
Scope: pulumi.String("string"),
},
Insecure: pulumi.Bool(false),
Headers: &dynatrace.WebhookNotificationHeadersArgs{
Headers: dynatrace.WebhookNotificationHeadersHeaderArray{
&dynatrace.WebhookNotificationHeadersHeaderArgs{
Name: pulumi.String("string"),
SecretValue: pulumi.String("string"),
Value: pulumi.String("string"),
},
},
},
SecretUrl: pulumi.String("string"),
Url: pulumi.String("string"),
UrlContainsSecret: pulumi.Bool(false),
UseOauth2: pulumi.Bool(false),
})
var webhookNotificationResource = new WebhookNotification("webhookNotificationResource", WebhookNotificationArgs.builder()
.active(false)
.profile("string")
.payload("string")
.legacyId("string")
.name("string")
.notifyClosedProblems(false)
.notifyEventMerges(false)
.oauth2Credentials(WebhookNotificationOauth2CredentialsArgs.builder()
.accessTokenUrl("string")
.clientId("string")
.clientSecret("string")
.authenticateViaRequestHeader(false)
.scope("string")
.build())
.insecure(false)
.headers(WebhookNotificationHeadersArgs.builder()
.headers(WebhookNotificationHeadersHeaderArgs.builder()
.name("string")
.secretValue("string")
.value("string")
.build())
.build())
.secretUrl("string")
.url("string")
.urlContainsSecret(false)
.useOauth2(false)
.build());
webhook_notification_resource = dynatrace.WebhookNotification("webhookNotificationResource",
active=False,
profile="string",
payload="string",
legacy_id="string",
name="string",
notify_closed_problems=False,
notify_event_merges=False,
oauth2_credentials={
"access_token_url": "string",
"client_id": "string",
"client_secret": "string",
"authenticate_via_request_header": False,
"scope": "string",
},
insecure=False,
headers={
"headers": [{
"name": "string",
"secret_value": "string",
"value": "string",
}],
},
secret_url="string",
url="string",
url_contains_secret=False,
use_oauth2=False)
const webhookNotificationResource = new dynatrace.WebhookNotification("webhookNotificationResource", {
active: false,
profile: "string",
payload: "string",
legacyId: "string",
name: "string",
notifyClosedProblems: false,
notifyEventMerges: false,
oauth2Credentials: {
accessTokenUrl: "string",
clientId: "string",
clientSecret: "string",
authenticateViaRequestHeader: false,
scope: "string",
},
insecure: false,
headers: {
headers: [{
name: "string",
secretValue: "string",
value: "string",
}],
},
secretUrl: "string",
url: "string",
urlContainsSecret: false,
useOauth2: false,
});
type: dynatrace:WebhookNotification
properties:
active: false
headers:
headers:
- name: string
secretValue: string
value: string
insecure: false
legacyId: string
name: string
notifyClosedProblems: false
notifyEventMerges: false
oauth2Credentials:
accessTokenUrl: string
authenticateViaRequestHeader: false
clientId: string
clientSecret: string
scope: string
payload: string
profile: string
secretUrl: string
url: string
urlContainsSecret: false
useOauth2: false
WebhookNotification 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 WebhookNotification resource accepts the following input properties:
- Active bool
- The configuration is enabled (
true
) or disabled (false
) - 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - Profile string
- The ID of the associated alerting profile
- Headers
Pulumiverse.
Dynatrace. Inputs. Webhook Notification Headers - A list of the additional HTTP headers
- Insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- Notify
Closed boolProblems - Send email if problem is closed
- Notify
Event boolMerges - Call webhook if new events merge into existing problems
- Oauth2Credentials
Pulumiverse.
Dynatrace. Inputs. Webhook Notification Oauth2Credentials - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- Secret
Url string - The secret URL of the webhook endpoint.
- Url string
- The URL of the WebHook endpoint
- Url
Contains boolSecret - Secret webhook URL
- Use
Oauth2 bool - Use OAuth 2.0 for authentication
- Active bool
- The configuration is enabled (
true
) or disabled (false
) - 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - Profile string
- The ID of the associated alerting profile
- Headers
Webhook
Notification Headers Args - A list of the additional HTTP headers
- Insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- Notify
Closed boolProblems - Send email if problem is closed
- Notify
Event boolMerges - Call webhook if new events merge into existing problems
- Oauth2Credentials
Webhook
Notification Oauth2Credentials Args - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- Secret
Url string - The secret URL of the webhook endpoint.
- Url string
- The URL of the WebHook endpoint
- Url
Contains boolSecret - Secret webhook URL
- Use
Oauth2 bool - Use OAuth 2.0 for authentication
- active Boolean
- The configuration is enabled (
true
) or disabled (false
) - 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - profile String
- The ID of the associated alerting profile
- headers
Webhook
Notification Headers - A list of the additional HTTP headers
- insecure Boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- notify
Closed BooleanProblems - Send email if problem is closed
- notify
Event BooleanMerges - Call webhook if new events merge into existing problems
- oauth2Credentials
Webhook
Notification Oauth2Credentials - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- secret
Url String - The secret URL of the webhook endpoint.
- url String
- The URL of the WebHook endpoint
- url
Contains BooleanSecret - Secret webhook URL
- use
Oauth2 Boolean - Use OAuth 2.0 for authentication
- active boolean
- The configuration is enabled (
true
) or disabled (false
) - 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - profile string
- The ID of the associated alerting profile
- headers
Webhook
Notification Headers - A list of the additional HTTP headers
- insecure boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- notify
Closed booleanProblems - Send email if problem is closed
- notify
Event booleanMerges - Call webhook if new events merge into existing problems
- oauth2Credentials
Webhook
Notification Oauth2Credentials - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- secret
Url string - The secret URL of the webhook endpoint.
- url string
- The URL of the WebHook endpoint
- url
Contains booleanSecret - Secret webhook URL
- use
Oauth2 boolean - Use OAuth 2.0 for authentication
- active bool
- The configuration is enabled (
true
) or disabled (false
) - 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - profile str
- The ID of the associated alerting profile
- headers
Webhook
Notification Headers Args - A list of the additional HTTP headers
- insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - legacy_
id str - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name str
- The name of the notification configuration
- notify_
closed_ boolproblems - Send email if problem is closed
- notify_
event_ boolmerges - Call webhook if new events merge into existing problems
- oauth2_
credentials WebhookNotification Oauth2Credentials Args - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- secret_
url str - The secret URL of the webhook endpoint.
- url str
- The URL of the WebHook endpoint
- url_
contains_ boolsecret - Secret webhook URL
- use_
oauth2 bool - Use OAuth 2.0 for authentication
- active Boolean
- The configuration is enabled (
true
) or disabled (false
) - 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - profile String
- The ID of the associated alerting profile
- headers Property Map
- A list of the additional HTTP headers
- insecure Boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- notify
Closed BooleanProblems - Send email if problem is closed
- notify
Event BooleanMerges - Call webhook if new events merge into existing problems
- oauth2Credentials Property Map
- To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- secret
Url String - The secret URL of the webhook endpoint.
- url String
- The URL of the WebHook endpoint
- url
Contains BooleanSecret - Secret webhook URL
- use
Oauth2 Boolean - Use OAuth 2.0 for authentication
Outputs
All input properties are implicitly available as output properties. Additionally, the WebhookNotification 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 WebhookNotification Resource
Get an existing WebhookNotification 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?: WebhookNotificationState, opts?: CustomResourceOptions): WebhookNotification
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
active: Optional[bool] = None,
headers: Optional[WebhookNotificationHeadersArgs] = None,
insecure: Optional[bool] = None,
legacy_id: Optional[str] = None,
name: Optional[str] = None,
notify_closed_problems: Optional[bool] = None,
notify_event_merges: Optional[bool] = None,
oauth2_credentials: Optional[WebhookNotificationOauth2CredentialsArgs] = None,
payload: Optional[str] = None,
profile: Optional[str] = None,
secret_url: Optional[str] = None,
url: Optional[str] = None,
url_contains_secret: Optional[bool] = None,
use_oauth2: Optional[bool] = None) -> WebhookNotification
func GetWebhookNotification(ctx *Context, name string, id IDInput, state *WebhookNotificationState, opts ...ResourceOption) (*WebhookNotification, error)
public static WebhookNotification Get(string name, Input<string> id, WebhookNotificationState? state, CustomResourceOptions? opts = null)
public static WebhookNotification get(String name, Output<String> id, WebhookNotificationState 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
) - Headers
Pulumiverse.
Dynatrace. Inputs. Webhook Notification Headers - A list of the additional HTTP headers
- Insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- Notify
Closed boolProblems - Send email if problem is closed
- Notify
Event boolMerges - Call webhook if new events merge into existing problems
- Oauth2Credentials
Pulumiverse.
Dynatrace. Inputs. Webhook Notification Oauth2Credentials - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - Profile string
- The ID of the associated alerting profile
- Secret
Url string - The secret URL of the webhook endpoint.
- Url string
- The URL of the WebHook endpoint
- Url
Contains boolSecret - Secret webhook URL
- Use
Oauth2 bool - Use OAuth 2.0 for authentication
- Active bool
- The configuration is enabled (
true
) or disabled (false
) - Headers
Webhook
Notification Headers Args - A list of the additional HTTP headers
- Insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- Notify
Closed boolProblems - Send email if problem is closed
- Notify
Event boolMerges - Call webhook if new events merge into existing problems
- Oauth2Credentials
Webhook
Notification Oauth2Credentials Args - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - Profile string
- The ID of the associated alerting profile
- Secret
Url string - The secret URL of the webhook endpoint.
- Url string
- The URL of the WebHook endpoint
- Url
Contains boolSecret - Secret webhook URL
- Use
Oauth2 bool - Use OAuth 2.0 for authentication
- active Boolean
- The configuration is enabled (
true
) or disabled (false
) - headers
Webhook
Notification Headers - A list of the additional HTTP headers
- insecure Boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- notify
Closed BooleanProblems - Send email if problem is closed
- notify
Event BooleanMerges - Call webhook if new events merge into existing problems
- oauth2Credentials
Webhook
Notification Oauth2Credentials - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - profile String
- The ID of the associated alerting profile
- secret
Url String - The secret URL of the webhook endpoint.
- url String
- The URL of the WebHook endpoint
- url
Contains BooleanSecret - Secret webhook URL
- use
Oauth2 Boolean - Use OAuth 2.0 for authentication
- active boolean
- The configuration is enabled (
true
) or disabled (false
) - headers
Webhook
Notification Headers - A list of the additional HTTP headers
- insecure boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- notify
Closed booleanProblems - Send email if problem is closed
- notify
Event booleanMerges - Call webhook if new events merge into existing problems
- oauth2Credentials
Webhook
Notification Oauth2Credentials - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - profile string
- The ID of the associated alerting profile
- secret
Url string - The secret URL of the webhook endpoint.
- url string
- The URL of the WebHook endpoint
- url
Contains booleanSecret - Secret webhook URL
- use
Oauth2 boolean - Use OAuth 2.0 for authentication
- active bool
- The configuration is enabled (
true
) or disabled (false
) - headers
Webhook
Notification Headers Args - A list of the additional HTTP headers
- insecure bool
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - legacy_
id str - The ID of these settings when referred to from resources requiring the REST API V1 keys
- name str
- The name of the notification configuration
- notify_
closed_ boolproblems - Send email if problem is closed
- notify_
event_ boolmerges - Call webhook if new events merge into existing problems
- oauth2_
credentials WebhookNotification Oauth2Credentials Args - To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - profile str
- The ID of the associated alerting profile
- secret_
url str - The secret URL of the webhook endpoint.
- url str
- The URL of the WebHook endpoint
- url_
contains_ boolsecret - Secret webhook URL
- use_
oauth2 bool - Use OAuth 2.0 for authentication
- active Boolean
- The configuration is enabled (
true
) or disabled (false
) - headers Property Map
- A list of the additional HTTP headers
- insecure Boolean
- Accept any, including self-signed and invalid, SSL certificate (
true
) or only trusted (false
) certificates - 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
- notify
Closed BooleanProblems - Send email if problem is closed
- notify
Event BooleanMerges - Call webhook if new events merge into existing problems
- oauth2Credentials Property Map
- To authenticate your integration, the OAuth 2.0 Client Credentials Flow (Grant Type) is used. For details see Client Credentials Flow).
- 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 areOPEN
andRESOLVED
. *{Tags}
: The list of tags that are defined for all impacted entities, separated by commas - profile String
- The ID of the associated alerting profile
- secret
Url String - The secret URL of the webhook endpoint.
- url String
- The URL of the WebHook endpoint
- url
Contains BooleanSecret - Secret webhook URL
- use
Oauth2 Boolean - Use OAuth 2.0 for authentication
Supporting Types
WebhookNotificationHeaders, WebhookNotificationHeadersArgs
- Headers
List<Pulumiverse.
Dynatrace. Inputs. Webhook Notification Headers Header> - An additional HTTP Header to include when sending requests
- Headers
[]Webhook
Notification Headers Header - An additional HTTP Header to include when sending requests
- headers
List<Webhook
Notification Headers Header> - An additional HTTP Header to include when sending requests
- headers
Webhook
Notification Headers Header[] - An additional HTTP Header to include when sending requests
- headers
Sequence[Webhook
Notification Headers Header] - An additional HTTP Header to include when sending requests
- headers List<Property Map>
- An additional HTTP Header to include when sending requests
WebhookNotificationHeadersHeader, WebhookNotificationHeadersHeaderArgs
- Name string
- The name of the HTTP header
- Secret
Value string - The value of the HTTP header as a sensitive property. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified. - Value string
- The value of the HTTP header. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified.
- Name string
- The name of the HTTP header
- Secret
Value string - The value of the HTTP header as a sensitive property. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified. - Value string
- The value of the HTTP header. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified.
- name String
- The name of the HTTP header
- secret
Value String - The value of the HTTP header as a sensitive property. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified. - value String
- The value of the HTTP header. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified.
- name string
- The name of the HTTP header
- secret
Value string - The value of the HTTP header as a sensitive property. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified. - value string
- The value of the HTTP header. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified.
- name str
- The name of the HTTP header
- secret_
value str - The value of the HTTP header as a sensitive property. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified. - value str
- The value of the HTTP header. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified.
- name String
- The name of the HTTP header
- secret
Value String - The value of the HTTP header as a sensitive property. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified. - value String
- The value of the HTTP header. May contain an empty value.
secret_value
andvalue
are mutually exclusive. Only one of those two is allowed to be specified.
WebhookNotificationOauth2Credentials, WebhookNotificationOauth2CredentialsArgs
- Access
Token stringUrl - Access token URL
- Client
Id string - Client ID
- Client
Secret string - Client secret
- Authenticate
Via boolRequest Header - If false, the client credentials are included in the HTTP request body.
- Scope string
- The scope of access you are requesting
- Access
Token stringUrl - Access token URL
- Client
Id string - Client ID
- Client
Secret string - Client secret
- Authenticate
Via boolRequest Header - If false, the client credentials are included in the HTTP request body.
- Scope string
- The scope of access you are requesting
- access
Token StringUrl - Access token URL
- client
Id String - Client ID
- client
Secret String - Client secret
- authenticate
Via BooleanRequest Header - If false, the client credentials are included in the HTTP request body.
- scope String
- The scope of access you are requesting
- access
Token stringUrl - Access token URL
- client
Id string - Client ID
- client
Secret string - Client secret
- authenticate
Via booleanRequest Header - If false, the client credentials are included in the HTTP request body.
- scope string
- The scope of access you are requesting
- access_
token_ strurl - Access token URL
- client_
id str - Client ID
- client_
secret str - Client secret
- authenticate_
via_ boolrequest_ header - If false, the client credentials are included in the HTTP request body.
- scope str
- The scope of access you are requesting
- access
Token StringUrl - Access token URL
- client
Id String - Client ID
- client
Secret String - Client secret
- authenticate
Via BooleanRequest Header - If false, the client credentials are included in the HTTP request body.
- scope String
- The scope of access you are requesting
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dynatrace
Terraform Provider.