Dynatrace v0.19.0 published on Wednesday, Oct 23, 2024 by Pulumiverse
dynatrace.FailureDetectionParameters
Explore with Pulumi AI
Create FailureDetectionParameters Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new FailureDetectionParameters(name: string, args: FailureDetectionParametersArgs, opts?: CustomResourceOptions);
@overload
def FailureDetectionParameters(resource_name: str,
args: FailureDetectionParametersArgs,
opts: Optional[ResourceOptions] = None)
@overload
def FailureDetectionParameters(resource_name: str,
opts: Optional[ResourceOptions] = None,
broken_links: Optional[FailureDetectionParametersBrokenLinksArgs] = None,
exception_rules: Optional[FailureDetectionParametersExceptionRulesArgs] = None,
http_response_codes: Optional[FailureDetectionParametersHttpResponseCodesArgs] = None,
description: Optional[str] = None,
name: Optional[str] = None)
func NewFailureDetectionParameters(ctx *Context, name string, args FailureDetectionParametersArgs, opts ...ResourceOption) (*FailureDetectionParameters, error)
public FailureDetectionParameters(string name, FailureDetectionParametersArgs args, CustomResourceOptions? opts = null)
public FailureDetectionParameters(String name, FailureDetectionParametersArgs args)
public FailureDetectionParameters(String name, FailureDetectionParametersArgs args, CustomResourceOptions options)
type: dynatrace:FailureDetectionParameters
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 FailureDetectionParametersArgs
- 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 FailureDetectionParametersArgs
- 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 FailureDetectionParametersArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args FailureDetectionParametersArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args FailureDetectionParametersArgs
- 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 failureDetectionParametersResource = new Dynatrace.FailureDetectionParameters("failureDetectionParametersResource", new()
{
BrokenLinks = new Dynatrace.Inputs.FailureDetectionParametersBrokenLinksArgs
{
Http404NotFoundFailures = false,
BrokenLinkDomains = new[]
{
"string",
},
},
ExceptionRules = new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesArgs
{
IgnoreAllExceptions = false,
IgnoreSpanFailureDetection = false,
CustomErrorRules = new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesCustomErrorRulesArgs
{
CustomErrorRules = new[]
{
new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleArgs
{
Condition = new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs
{
CompareOperationType = "string",
CaseSensitive = false,
DoubleValue = 0,
IntValue = 0,
TextValue = "string",
},
RequestAttribute = "string",
},
},
},
CustomHandledExceptions = new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesCustomHandledExceptionsArgs
{
CustomHandledExceptions = new[]
{
new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs
{
ClassPattern = "string",
MessagePattern = "string",
},
},
},
IgnoredExceptions = new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesIgnoredExceptionsArgs
{
CustomHandledExceptions = new[]
{
new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs
{
ClassPattern = "string",
MessagePattern = "string",
},
},
},
SuccessForcingExceptions = new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesSuccessForcingExceptionsArgs
{
CustomHandledExceptions = new[]
{
new Dynatrace.Inputs.FailureDetectionParametersExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs
{
ClassPattern = "string",
MessagePattern = "string",
},
},
},
},
HttpResponseCodes = new Dynatrace.Inputs.FailureDetectionParametersHttpResponseCodesArgs
{
ClientSideErrors = "string",
FailOnMissingResponseCodeClientSide = false,
FailOnMissingResponseCodeServerSide = false,
ServerSideErrors = "string",
},
Description = "string",
Name = "string",
});
example, err := dynatrace.NewFailureDetectionParameters(ctx, "failureDetectionParametersResource", &dynatrace.FailureDetectionParametersArgs{
BrokenLinks: &dynatrace.FailureDetectionParametersBrokenLinksArgs{
Http404NotFoundFailures: pulumi.Bool(false),
BrokenLinkDomains: pulumi.StringArray{
pulumi.String("string"),
},
},
ExceptionRules: &dynatrace.FailureDetectionParametersExceptionRulesArgs{
IgnoreAllExceptions: pulumi.Bool(false),
IgnoreSpanFailureDetection: pulumi.Bool(false),
CustomErrorRules: &dynatrace.FailureDetectionParametersExceptionRulesCustomErrorRulesArgs{
CustomErrorRules: dynatrace.FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleArray{
&dynatrace.FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleArgs{
Condition: &dynatrace.FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs{
CompareOperationType: pulumi.String("string"),
CaseSensitive: pulumi.Bool(false),
DoubleValue: pulumi.Float64(0),
IntValue: pulumi.Int(0),
TextValue: pulumi.String("string"),
},
RequestAttribute: pulumi.String("string"),
},
},
},
CustomHandledExceptions: &dynatrace.FailureDetectionParametersExceptionRulesCustomHandledExceptionsArgs{
CustomHandledExceptions: dynatrace.FailureDetectionParametersExceptionRulesCustomHandledExceptionsCustomHandledExceptionArray{
&dynatrace.FailureDetectionParametersExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs{
ClassPattern: pulumi.String("string"),
MessagePattern: pulumi.String("string"),
},
},
},
IgnoredExceptions: &dynatrace.FailureDetectionParametersExceptionRulesIgnoredExceptionsArgs{
CustomHandledExceptions: dynatrace.FailureDetectionParametersExceptionRulesIgnoredExceptionsCustomHandledExceptionArray{
&dynatrace.FailureDetectionParametersExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs{
ClassPattern: pulumi.String("string"),
MessagePattern: pulumi.String("string"),
},
},
},
SuccessForcingExceptions: &dynatrace.FailureDetectionParametersExceptionRulesSuccessForcingExceptionsArgs{
CustomHandledExceptions: dynatrace.FailureDetectionParametersExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArray{
&dynatrace.FailureDetectionParametersExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs{
ClassPattern: pulumi.String("string"),
MessagePattern: pulumi.String("string"),
},
},
},
},
HttpResponseCodes: &dynatrace.FailureDetectionParametersHttpResponseCodesArgs{
ClientSideErrors: pulumi.String("string"),
FailOnMissingResponseCodeClientSide: pulumi.Bool(false),
FailOnMissingResponseCodeServerSide: pulumi.Bool(false),
ServerSideErrors: pulumi.String("string"),
},
Description: pulumi.String("string"),
Name: pulumi.String("string"),
})
var failureDetectionParametersResource = new FailureDetectionParameters("failureDetectionParametersResource", FailureDetectionParametersArgs.builder()
.brokenLinks(FailureDetectionParametersBrokenLinksArgs.builder()
.http404NotFoundFailures(false)
.brokenLinkDomains("string")
.build())
.exceptionRules(FailureDetectionParametersExceptionRulesArgs.builder()
.ignoreAllExceptions(false)
.ignoreSpanFailureDetection(false)
.customErrorRules(FailureDetectionParametersExceptionRulesCustomErrorRulesArgs.builder()
.customErrorRules(FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleArgs.builder()
.condition(FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs.builder()
.compareOperationType("string")
.caseSensitive(false)
.doubleValue(0)
.intValue(0)
.textValue("string")
.build())
.requestAttribute("string")
.build())
.build())
.customHandledExceptions(FailureDetectionParametersExceptionRulesCustomHandledExceptionsArgs.builder()
.customHandledExceptions(FailureDetectionParametersExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs.builder()
.classPattern("string")
.messagePattern("string")
.build())
.build())
.ignoredExceptions(FailureDetectionParametersExceptionRulesIgnoredExceptionsArgs.builder()
.customHandledExceptions(FailureDetectionParametersExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs.builder()
.classPattern("string")
.messagePattern("string")
.build())
.build())
.successForcingExceptions(FailureDetectionParametersExceptionRulesSuccessForcingExceptionsArgs.builder()
.customHandledExceptions(FailureDetectionParametersExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs.builder()
.classPattern("string")
.messagePattern("string")
.build())
.build())
.build())
.httpResponseCodes(FailureDetectionParametersHttpResponseCodesArgs.builder()
.clientSideErrors("string")
.failOnMissingResponseCodeClientSide(false)
.failOnMissingResponseCodeServerSide(false)
.serverSideErrors("string")
.build())
.description("string")
.name("string")
.build());
failure_detection_parameters_resource = dynatrace.FailureDetectionParameters("failureDetectionParametersResource",
broken_links=dynatrace.FailureDetectionParametersBrokenLinksArgs(
http404_not_found_failures=False,
broken_link_domains=["string"],
),
exception_rules=dynatrace.FailureDetectionParametersExceptionRulesArgs(
ignore_all_exceptions=False,
ignore_span_failure_detection=False,
custom_error_rules=dynatrace.FailureDetectionParametersExceptionRulesCustomErrorRulesArgs(
custom_error_rules=[dynatrace.FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleArgs(
condition=dynatrace.FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs(
compare_operation_type="string",
case_sensitive=False,
double_value=0,
int_value=0,
text_value="string",
),
request_attribute="string",
)],
),
custom_handled_exceptions=dynatrace.FailureDetectionParametersExceptionRulesCustomHandledExceptionsArgs(
custom_handled_exceptions=[dynatrace.FailureDetectionParametersExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs(
class_pattern="string",
message_pattern="string",
)],
),
ignored_exceptions=dynatrace.FailureDetectionParametersExceptionRulesIgnoredExceptionsArgs(
custom_handled_exceptions=[dynatrace.FailureDetectionParametersExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs(
class_pattern="string",
message_pattern="string",
)],
),
success_forcing_exceptions=dynatrace.FailureDetectionParametersExceptionRulesSuccessForcingExceptionsArgs(
custom_handled_exceptions=[dynatrace.FailureDetectionParametersExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs(
class_pattern="string",
message_pattern="string",
)],
),
),
http_response_codes=dynatrace.FailureDetectionParametersHttpResponseCodesArgs(
client_side_errors="string",
fail_on_missing_response_code_client_side=False,
fail_on_missing_response_code_server_side=False,
server_side_errors="string",
),
description="string",
name="string")
const failureDetectionParametersResource = new dynatrace.FailureDetectionParameters("failureDetectionParametersResource", {
brokenLinks: {
http404NotFoundFailures: false,
brokenLinkDomains: ["string"],
},
exceptionRules: {
ignoreAllExceptions: false,
ignoreSpanFailureDetection: false,
customErrorRules: {
customErrorRules: [{
condition: {
compareOperationType: "string",
caseSensitive: false,
doubleValue: 0,
intValue: 0,
textValue: "string",
},
requestAttribute: "string",
}],
},
customHandledExceptions: {
customHandledExceptions: [{
classPattern: "string",
messagePattern: "string",
}],
},
ignoredExceptions: {
customHandledExceptions: [{
classPattern: "string",
messagePattern: "string",
}],
},
successForcingExceptions: {
customHandledExceptions: [{
classPattern: "string",
messagePattern: "string",
}],
},
},
httpResponseCodes: {
clientSideErrors: "string",
failOnMissingResponseCodeClientSide: false,
failOnMissingResponseCodeServerSide: false,
serverSideErrors: "string",
},
description: "string",
name: "string",
});
type: dynatrace:FailureDetectionParameters
properties:
brokenLinks:
brokenLinkDomains:
- string
http404NotFoundFailures: false
description: string
exceptionRules:
customErrorRules:
customErrorRules:
- condition:
caseSensitive: false
compareOperationType: string
doubleValue: 0
intValue: 0
textValue: string
requestAttribute: string
customHandledExceptions:
customHandledExceptions:
- classPattern: string
messagePattern: string
ignoreAllExceptions: false
ignoreSpanFailureDetection: false
ignoredExceptions:
customHandledExceptions:
- classPattern: string
messagePattern: string
successForcingExceptions:
customHandledExceptions:
- classPattern: string
messagePattern: string
httpResponseCodes:
clientSideErrors: string
failOnMissingResponseCodeClientSide: false
failOnMissingResponseCodeServerSide: false
serverSideErrors: string
name: string
FailureDetectionParameters 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 FailureDetectionParameters resource accepts the following input properties:
- Broken
Links Pulumiverse.Dynatrace. Inputs. Failure Detection Parameters Broken Links - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- Exception
Rules Pulumiverse.Dynatrace. Inputs. Failure Detection Parameters Exception Rules - Customize failure detection for specific exceptions and errors
- Http
Response Pulumiverse.Codes Dynatrace. Inputs. Failure Detection Parameters Http Response Codes - HTTP response codes
- Description string
- Description
- Name string
- Name
- Broken
Links FailureDetection Parameters Broken Links Args - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- Exception
Rules FailureDetection Parameters Exception Rules Args - Customize failure detection for specific exceptions and errors
- Http
Response FailureCodes Detection Parameters Http Response Codes Args - HTTP response codes
- Description string
- Description
- Name string
- Name
- broken
Links FailureDetection Parameters Broken Links - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- exception
Rules FailureDetection Parameters Exception Rules - Customize failure detection for specific exceptions and errors
- http
Response FailureCodes Detection Parameters Http Response Codes - HTTP response codes
- description String
- Description
- name String
- Name
- broken
Links FailureDetection Parameters Broken Links - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- exception
Rules FailureDetection Parameters Exception Rules - Customize failure detection for specific exceptions and errors
- http
Response FailureCodes Detection Parameters Http Response Codes - HTTP response codes
- description string
- Description
- name string
- Name
- broken_
links FailureDetection Parameters Broken Links Args - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- exception_
rules FailureDetection Parameters Exception Rules Args - Customize failure detection for specific exceptions and errors
- http_
response_ Failurecodes Detection Parameters Http Response Codes Args - HTTP response codes
- description str
- Description
- name str
- Name
- broken
Links Property Map - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- exception
Rules Property Map - Customize failure detection for specific exceptions and errors
- http
Response Property MapCodes - HTTP response codes
- description String
- Description
- name String
- Name
Outputs
All input properties are implicitly available as output properties. Additionally, the FailureDetectionParameters 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 FailureDetectionParameters Resource
Get an existing FailureDetectionParameters 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?: FailureDetectionParametersState, opts?: CustomResourceOptions): FailureDetectionParameters
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
broken_links: Optional[FailureDetectionParametersBrokenLinksArgs] = None,
description: Optional[str] = None,
exception_rules: Optional[FailureDetectionParametersExceptionRulesArgs] = None,
http_response_codes: Optional[FailureDetectionParametersHttpResponseCodesArgs] = None,
name: Optional[str] = None) -> FailureDetectionParameters
func GetFailureDetectionParameters(ctx *Context, name string, id IDInput, state *FailureDetectionParametersState, opts ...ResourceOption) (*FailureDetectionParameters, error)
public static FailureDetectionParameters Get(string name, Input<string> id, FailureDetectionParametersState? state, CustomResourceOptions? opts = null)
public static FailureDetectionParameters get(String name, Output<String> id, FailureDetectionParametersState 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.
- Broken
Links Pulumiverse.Dynatrace. Inputs. Failure Detection Parameters Broken Links - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- Description string
- Description
- Exception
Rules Pulumiverse.Dynatrace. Inputs. Failure Detection Parameters Exception Rules - Customize failure detection for specific exceptions and errors
- Http
Response Pulumiverse.Codes Dynatrace. Inputs. Failure Detection Parameters Http Response Codes - HTTP response codes
- Name string
- Name
- Broken
Links FailureDetection Parameters Broken Links Args - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- Description string
- Description
- Exception
Rules FailureDetection Parameters Exception Rules Args - Customize failure detection for specific exceptions and errors
- Http
Response FailureCodes Detection Parameters Http Response Codes Args - HTTP response codes
- Name string
- Name
- broken
Links FailureDetection Parameters Broken Links - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- description String
- Description
- exception
Rules FailureDetection Parameters Exception Rules - Customize failure detection for specific exceptions and errors
- http
Response FailureCodes Detection Parameters Http Response Codes - HTTP response codes
- name String
- Name
- broken
Links FailureDetection Parameters Broken Links - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- description string
- Description
- exception
Rules FailureDetection Parameters Exception Rules - Customize failure detection for specific exceptions and errors
- http
Response FailureCodes Detection Parameters Http Response Codes - HTTP response codes
- name string
- Name
- broken_
links FailureDetection Parameters Broken Links Args - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- description str
- Description
- exception_
rules FailureDetection Parameters Exception Rules Args - Customize failure detection for specific exceptions and errors
- http_
response_ Failurecodes Detection Parameters Http Response Codes Args - HTTP response codes
- name str
- Name
- broken
Links Property Map - HTTP 404 response codes are thrown when a web server can't find a certain page. 404s are classified as broken links on the client side and therefore aren't considered to be service failures. By enabling this setting, you can have 404s treated as server-side service failures.
- description String
- Description
- exception
Rules Property Map - Customize failure detection for specific exceptions and errors
- http
Response Property MapCodes - HTTP response codes
- name String
- Name
Supporting Types
FailureDetectionParametersBrokenLinks, FailureDetectionParametersBrokenLinksArgs
- Http404Not
Found boolFailures - Consider 404 HTTP response codes as failures
- Broken
Link List<string>Domains - If your application relies on other hosts at other domains, add the associated domain names here. Once configured, Dynatrace will consider 404s thrown by hosts at these domains to be service failures related to your application.
- Http404Not
Found boolFailures - Consider 404 HTTP response codes as failures
- Broken
Link []stringDomains - If your application relies on other hosts at other domains, add the associated domain names here. Once configured, Dynatrace will consider 404s thrown by hosts at these domains to be service failures related to your application.
- http404Not
Found BooleanFailures - Consider 404 HTTP response codes as failures
- broken
Link List<String>Domains - If your application relies on other hosts at other domains, add the associated domain names here. Once configured, Dynatrace will consider 404s thrown by hosts at these domains to be service failures related to your application.
- http404Not
Found booleanFailures - Consider 404 HTTP response codes as failures
- broken
Link string[]Domains - If your application relies on other hosts at other domains, add the associated domain names here. Once configured, Dynatrace will consider 404s thrown by hosts at these domains to be service failures related to your application.
- http404_
not_ boolfound_ failures - Consider 404 HTTP response codes as failures
- broken_
link_ Sequence[str]domains - If your application relies on other hosts at other domains, add the associated domain names here. Once configured, Dynatrace will consider 404s thrown by hosts at these domains to be service failures related to your application.
- http404Not
Found BooleanFailures - Consider 404 HTTP response codes as failures
- broken
Link List<String>Domains - If your application relies on other hosts at other domains, add the associated domain names here. Once configured, Dynatrace will consider 404s thrown by hosts at these domains to be service failures related to your application.
FailureDetectionParametersExceptionRules, FailureDetectionParametersExceptionRulesArgs
- Ignore
All boolExceptions - Ignore all exceptions
- Ignore
Span boolFailure Detection - Ignore span failure detection
- Custom
Error Pulumiverse.Rules Dynatrace. Inputs. Failure Detection Parameters Exception Rules Custom Error Rules - Some custom error situations are only detectable via a return value or other means. To support such cases, define a request attribute that captures the required data. Then define a custom error rule that determines if the request has failed based on the value of the request attribute.
- Custom
Handled Pulumiverse.Exceptions Dynatrace. Inputs. Failure Detection Parameters Exception Rules Custom Handled Exceptions - There may be situations where your application code handles exceptions gracefully in a manner that these failures aren't detected by Dynatrace. Use this setting to define specific gracefully-handled exceptions that should be treated as service failures.
- Ignored
Exceptions Pulumiverse.Dynatrace. Inputs. Failure Detection Parameters Exception Rules Ignored Exceptions - Some exceptions that are thrown by legacy or 3rd-party code indicate a specific response, not an error. Use this setting to instruct Dynatrace to treat such exceptions as non-failed requests.. If an exception matching any of the defined patterns occurs in a request, it will not be considered as a failure. Other exceptions occurring at the same request might still mark the request as failed.
- Success
Forcing Pulumiverse.Exceptions Dynatrace. Inputs. Failure Detection Parameters Exception Rules Success Forcing Exceptions - Define exceptions which indicate that a service call should not be considered as failed. E.g. an exception indicating that the client aborted the operation.. If an exception matching any of the defined patterns occurs on the entry node of the service, it will be considered successful. Compared to ignored exceptions, the request will be considered successful even if other exceptions occur in the same request.
- Ignore
All boolExceptions - Ignore all exceptions
- Ignore
Span boolFailure Detection - Ignore span failure detection
- Custom
Error FailureRules Detection Parameters Exception Rules Custom Error Rules - Some custom error situations are only detectable via a return value or other means. To support such cases, define a request attribute that captures the required data. Then define a custom error rule that determines if the request has failed based on the value of the request attribute.
- Custom
Handled FailureExceptions Detection Parameters Exception Rules Custom Handled Exceptions - There may be situations where your application code handles exceptions gracefully in a manner that these failures aren't detected by Dynatrace. Use this setting to define specific gracefully-handled exceptions that should be treated as service failures.
- Ignored
Exceptions FailureDetection Parameters Exception Rules Ignored Exceptions - Some exceptions that are thrown by legacy or 3rd-party code indicate a specific response, not an error. Use this setting to instruct Dynatrace to treat such exceptions as non-failed requests.. If an exception matching any of the defined patterns occurs in a request, it will not be considered as a failure. Other exceptions occurring at the same request might still mark the request as failed.
- Success
Forcing FailureExceptions Detection Parameters Exception Rules Success Forcing Exceptions - Define exceptions which indicate that a service call should not be considered as failed. E.g. an exception indicating that the client aborted the operation.. If an exception matching any of the defined patterns occurs on the entry node of the service, it will be considered successful. Compared to ignored exceptions, the request will be considered successful even if other exceptions occur in the same request.
- ignore
All BooleanExceptions - Ignore all exceptions
- ignore
Span BooleanFailure Detection - Ignore span failure detection
- custom
Error FailureRules Detection Parameters Exception Rules Custom Error Rules - Some custom error situations are only detectable via a return value or other means. To support such cases, define a request attribute that captures the required data. Then define a custom error rule that determines if the request has failed based on the value of the request attribute.
- custom
Handled FailureExceptions Detection Parameters Exception Rules Custom Handled Exceptions - There may be situations where your application code handles exceptions gracefully in a manner that these failures aren't detected by Dynatrace. Use this setting to define specific gracefully-handled exceptions that should be treated as service failures.
- ignored
Exceptions FailureDetection Parameters Exception Rules Ignored Exceptions - Some exceptions that are thrown by legacy or 3rd-party code indicate a specific response, not an error. Use this setting to instruct Dynatrace to treat such exceptions as non-failed requests.. If an exception matching any of the defined patterns occurs in a request, it will not be considered as a failure. Other exceptions occurring at the same request might still mark the request as failed.
- success
Forcing FailureExceptions Detection Parameters Exception Rules Success Forcing Exceptions - Define exceptions which indicate that a service call should not be considered as failed. E.g. an exception indicating that the client aborted the operation.. If an exception matching any of the defined patterns occurs on the entry node of the service, it will be considered successful. Compared to ignored exceptions, the request will be considered successful even if other exceptions occur in the same request.
- ignore
All booleanExceptions - Ignore all exceptions
- ignore
Span booleanFailure Detection - Ignore span failure detection
- custom
Error FailureRules Detection Parameters Exception Rules Custom Error Rules - Some custom error situations are only detectable via a return value or other means. To support such cases, define a request attribute that captures the required data. Then define a custom error rule that determines if the request has failed based on the value of the request attribute.
- custom
Handled FailureExceptions Detection Parameters Exception Rules Custom Handled Exceptions - There may be situations where your application code handles exceptions gracefully in a manner that these failures aren't detected by Dynatrace. Use this setting to define specific gracefully-handled exceptions that should be treated as service failures.
- ignored
Exceptions FailureDetection Parameters Exception Rules Ignored Exceptions - Some exceptions that are thrown by legacy or 3rd-party code indicate a specific response, not an error. Use this setting to instruct Dynatrace to treat such exceptions as non-failed requests.. If an exception matching any of the defined patterns occurs in a request, it will not be considered as a failure. Other exceptions occurring at the same request might still mark the request as failed.
- success
Forcing FailureExceptions Detection Parameters Exception Rules Success Forcing Exceptions - Define exceptions which indicate that a service call should not be considered as failed. E.g. an exception indicating that the client aborted the operation.. If an exception matching any of the defined patterns occurs on the entry node of the service, it will be considered successful. Compared to ignored exceptions, the request will be considered successful even if other exceptions occur in the same request.
- ignore_
all_ boolexceptions - Ignore all exceptions
- ignore_
span_ boolfailure_ detection - Ignore span failure detection
- custom_
error_ Failurerules Detection Parameters Exception Rules Custom Error Rules - Some custom error situations are only detectable via a return value or other means. To support such cases, define a request attribute that captures the required data. Then define a custom error rule that determines if the request has failed based on the value of the request attribute.
- custom_
handled_ Failureexceptions Detection Parameters Exception Rules Custom Handled Exceptions - There may be situations where your application code handles exceptions gracefully in a manner that these failures aren't detected by Dynatrace. Use this setting to define specific gracefully-handled exceptions that should be treated as service failures.
- ignored_
exceptions FailureDetection Parameters Exception Rules Ignored Exceptions - Some exceptions that are thrown by legacy or 3rd-party code indicate a specific response, not an error. Use this setting to instruct Dynatrace to treat such exceptions as non-failed requests.. If an exception matching any of the defined patterns occurs in a request, it will not be considered as a failure. Other exceptions occurring at the same request might still mark the request as failed.
- success_
forcing_ Failureexceptions Detection Parameters Exception Rules Success Forcing Exceptions - Define exceptions which indicate that a service call should not be considered as failed. E.g. an exception indicating that the client aborted the operation.. If an exception matching any of the defined patterns occurs on the entry node of the service, it will be considered successful. Compared to ignored exceptions, the request will be considered successful even if other exceptions occur in the same request.
- ignore
All BooleanExceptions - Ignore all exceptions
- ignore
Span BooleanFailure Detection - Ignore span failure detection
- custom
Error Property MapRules - Some custom error situations are only detectable via a return value or other means. To support such cases, define a request attribute that captures the required data. Then define a custom error rule that determines if the request has failed based on the value of the request attribute.
- custom
Handled Property MapExceptions - There may be situations where your application code handles exceptions gracefully in a manner that these failures aren't detected by Dynatrace. Use this setting to define specific gracefully-handled exceptions that should be treated as service failures.
- ignored
Exceptions Property Map - Some exceptions that are thrown by legacy or 3rd-party code indicate a specific response, not an error. Use this setting to instruct Dynatrace to treat such exceptions as non-failed requests.. If an exception matching any of the defined patterns occurs in a request, it will not be considered as a failure. Other exceptions occurring at the same request might still mark the request as failed.
- success
Forcing Property MapExceptions - Define exceptions which indicate that a service call should not be considered as failed. E.g. an exception indicating that the client aborted the operation.. If an exception matching any of the defined patterns occurs on the entry node of the service, it will be considered successful. Compared to ignored exceptions, the request will be considered successful even if other exceptions occur in the same request.
FailureDetectionParametersExceptionRulesCustomErrorRules, FailureDetectionParametersExceptionRulesCustomErrorRulesArgs
FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRule, FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleArgs
- Condition
Pulumiverse.
Dynatrace. Inputs. Failure Detection Parameters Exception Rules Custom Error Rules Custom Error Rule Condition - Request attribute condition
- Request
Attribute string - Request attribute
- Condition
Failure
Detection Parameters Exception Rules Custom Error Rules Custom Error Rule Condition - Request attribute condition
- Request
Attribute string - Request attribute
- condition
Failure
Detection Parameters Exception Rules Custom Error Rules Custom Error Rule Condition - Request attribute condition
- request
Attribute String - Request attribute
- condition
Failure
Detection Parameters Exception Rules Custom Error Rules Custom Error Rule Condition - Request attribute condition
- request
Attribute string - Request attribute
- condition
Failure
Detection Parameters Exception Rules Custom Error Rules Custom Error Rule Condition - Request attribute condition
- request_
attribute str - Request attribute
- condition Property Map
- Request attribute condition
- request
Attribute String - Request attribute
FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleCondition, FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs
- Compare
Operation stringType - Apply this comparison
- Case
Sensitive bool - Case sensitive
- Double
Value double - Value
- Int
Value int - Value
- Text
Value string - Value
- Compare
Operation stringType - Apply this comparison
- Case
Sensitive bool - Case sensitive
- Double
Value float64 - Value
- Int
Value int - Value
- Text
Value string - Value
- compare
Operation StringType - Apply this comparison
- case
Sensitive Boolean - Case sensitive
- double
Value Double - Value
- int
Value Integer - Value
- text
Value String - Value
- compare
Operation stringType - Apply this comparison
- case
Sensitive boolean - Case sensitive
- double
Value number - Value
- int
Value number - Value
- text
Value string - Value
- compare_
operation_ strtype - Apply this comparison
- case_
sensitive bool - Case sensitive
- double_
value float - Value
- int_
value int - Value
- text_
value str - Value
- compare
Operation StringType - Apply this comparison
- case
Sensitive Boolean - Case sensitive
- double
Value Number - Value
- int
Value Number - Value
- text
Value String - Value
FailureDetectionParametersExceptionRulesCustomHandledExceptions, FailureDetectionParametersExceptionRulesCustomHandledExceptionsArgs
FailureDetectionParametersExceptionRulesCustomHandledExceptionsCustomHandledException, FailureDetectionParametersExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs
- Class
Pattern string - The pattern will match if it is contained within the actual class name.
- Message
Pattern string - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- Class
Pattern string - The pattern will match if it is contained within the actual class name.
- Message
Pattern string - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class
Pattern String - The pattern will match if it is contained within the actual class name.
- message
Pattern String - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class
Pattern string - The pattern will match if it is contained within the actual class name.
- message
Pattern string - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class_
pattern str - The pattern will match if it is contained within the actual class name.
- message_
pattern str - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class
Pattern String - The pattern will match if it is contained within the actual class name.
- message
Pattern String - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
FailureDetectionParametersExceptionRulesIgnoredExceptions, FailureDetectionParametersExceptionRulesIgnoredExceptionsArgs
FailureDetectionParametersExceptionRulesIgnoredExceptionsCustomHandledException, FailureDetectionParametersExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs
- Class
Pattern string - The pattern will match if it is contained within the actual class name.
- Message
Pattern string - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- Class
Pattern string - The pattern will match if it is contained within the actual class name.
- Message
Pattern string - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class
Pattern String - The pattern will match if it is contained within the actual class name.
- message
Pattern String - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class
Pattern string - The pattern will match if it is contained within the actual class name.
- message
Pattern string - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class_
pattern str - The pattern will match if it is contained within the actual class name.
- message_
pattern str - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class
Pattern String - The pattern will match if it is contained within the actual class name.
- message
Pattern String - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
FailureDetectionParametersExceptionRulesSuccessForcingExceptions, FailureDetectionParametersExceptionRulesSuccessForcingExceptionsArgs
FailureDetectionParametersExceptionRulesSuccessForcingExceptionsCustomHandledException, FailureDetectionParametersExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs
- Class
Pattern string - The pattern will match if it is contained within the actual class name.
- Message
Pattern string - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- Class
Pattern string - The pattern will match if it is contained within the actual class name.
- Message
Pattern string - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class
Pattern String - The pattern will match if it is contained within the actual class name.
- message
Pattern String - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class
Pattern string - The pattern will match if it is contained within the actual class name.
- message
Pattern string - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class_
pattern str - The pattern will match if it is contained within the actual class name.
- message_
pattern str - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
- class
Pattern String - The pattern will match if it is contained within the actual class name.
- message
Pattern String - Optionally, define an exception message pattern. The pattern will match if the actual exception message contains the pattern.
FailureDetectionParametersHttpResponseCodes, FailureDetectionParametersHttpResponseCodesArgs
- Client
Side stringErrors - HTTP response codes which indicate client side errors
- Fail
On boolMissing Response Code Client Side - Treat missing HTTP response code as client side error
- Fail
On boolMissing Response Code Server Side - Treat missing HTTP response code as server side errors
- Server
Side stringErrors - HTTP response codes which indicate an error on the server side
- Client
Side stringErrors - HTTP response codes which indicate client side errors
- Fail
On boolMissing Response Code Client Side - Treat missing HTTP response code as client side error
- Fail
On boolMissing Response Code Server Side - Treat missing HTTP response code as server side errors
- Server
Side stringErrors - HTTP response codes which indicate an error on the server side
- client
Side StringErrors - HTTP response codes which indicate client side errors
- fail
On BooleanMissing Response Code Client Side - Treat missing HTTP response code as client side error
- fail
On BooleanMissing Response Code Server Side - Treat missing HTTP response code as server side errors
- server
Side StringErrors - HTTP response codes which indicate an error on the server side
- client
Side stringErrors - HTTP response codes which indicate client side errors
- fail
On booleanMissing Response Code Client Side - Treat missing HTTP response code as client side error
- fail
On booleanMissing Response Code Server Side - Treat missing HTTP response code as server side errors
- server
Side stringErrors - HTTP response codes which indicate an error on the server side
- client_
side_ strerrors - HTTP response codes which indicate client side errors
- fail_
on_ boolmissing_ response_ code_ client_ side - Treat missing HTTP response code as client side error
- fail_
on_ boolmissing_ response_ code_ server_ side - Treat missing HTTP response code as server side errors
- server_
side_ strerrors - HTTP response codes which indicate an error on the server side
- client
Side StringErrors - HTTP response codes which indicate client side errors
- fail
On BooleanMissing Response Code Client Side - Treat missing HTTP response code as client side error
- fail
On BooleanMissing Response Code Server Side - Treat missing HTTP response code as server side errors
- server
Side StringErrors - HTTP response codes which indicate an error on the server side
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dynatrace
Terraform Provider.