Dynatrace v0.16.0 published on Tuesday, Sep 10, 2024 by Pulumiverse
dynatrace.ServiceFailure
Explore with Pulumi AI
Create ServiceFailure Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new ServiceFailure(name: string, args: ServiceFailureArgs, opts?: CustomResourceOptions);
@overload
def ServiceFailure(resource_name: str,
args: ServiceFailureArgs,
opts: Optional[ResourceOptions] = None)
@overload
def ServiceFailure(resource_name: str,
opts: Optional[ResourceOptions] = None,
enabled: Optional[bool] = None,
service_id: Optional[str] = None,
exception_rules: Optional[ServiceFailureExceptionRulesArgs] = None)
func NewServiceFailure(ctx *Context, name string, args ServiceFailureArgs, opts ...ResourceOption) (*ServiceFailure, error)
public ServiceFailure(string name, ServiceFailureArgs args, CustomResourceOptions? opts = null)
public ServiceFailure(String name, ServiceFailureArgs args)
public ServiceFailure(String name, ServiceFailureArgs args, CustomResourceOptions options)
type: dynatrace:ServiceFailure
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 ServiceFailureArgs
- 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 ServiceFailureArgs
- 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 ServiceFailureArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args ServiceFailureArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args ServiceFailureArgs
- 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 serviceFailureResource = new Dynatrace.ServiceFailure("serviceFailureResource", new()
{
Enabled = false,
ServiceId = "string",
ExceptionRules = new Dynatrace.Inputs.ServiceFailureExceptionRulesArgs
{
IgnoreAllExceptions = false,
IgnoreSpanFailureDetection = false,
CustomErrorRules = new Dynatrace.Inputs.ServiceFailureExceptionRulesCustomErrorRulesArgs
{
CustomErrorRules = new[]
{
new Dynatrace.Inputs.ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleArgs
{
Condition = new Dynatrace.Inputs.ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs
{
CompareOperationType = "string",
CaseSensitive = false,
DoubleValue = 0,
IntValue = 0,
TextValue = "string",
},
RequestAttribute = "string",
},
},
},
CustomHandledExceptions = new Dynatrace.Inputs.ServiceFailureExceptionRulesCustomHandledExceptionsArgs
{
CustomHandledExceptions = new[]
{
new Dynatrace.Inputs.ServiceFailureExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs
{
ClassPattern = "string",
MessagePattern = "string",
},
},
},
IgnoredExceptions = new Dynatrace.Inputs.ServiceFailureExceptionRulesIgnoredExceptionsArgs
{
CustomHandledExceptions = new[]
{
new Dynatrace.Inputs.ServiceFailureExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs
{
ClassPattern = "string",
MessagePattern = "string",
},
},
},
SuccessForcingExceptions = new Dynatrace.Inputs.ServiceFailureExceptionRulesSuccessForcingExceptionsArgs
{
CustomHandledExceptions = new[]
{
new Dynatrace.Inputs.ServiceFailureExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs
{
ClassPattern = "string",
MessagePattern = "string",
},
},
},
},
});
example, err := dynatrace.NewServiceFailure(ctx, "serviceFailureResource", &dynatrace.ServiceFailureArgs{
Enabled: pulumi.Bool(false),
ServiceId: pulumi.String("string"),
ExceptionRules: &dynatrace.ServiceFailureExceptionRulesArgs{
IgnoreAllExceptions: pulumi.Bool(false),
IgnoreSpanFailureDetection: pulumi.Bool(false),
CustomErrorRules: &dynatrace.ServiceFailureExceptionRulesCustomErrorRulesArgs{
CustomErrorRules: dynatrace.ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleArray{
&dynatrace.ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleArgs{
Condition: &dynatrace.ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs{
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.ServiceFailureExceptionRulesCustomHandledExceptionsArgs{
CustomHandledExceptions: dynatrace.ServiceFailureExceptionRulesCustomHandledExceptionsCustomHandledExceptionArray{
&dynatrace.ServiceFailureExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs{
ClassPattern: pulumi.String("string"),
MessagePattern: pulumi.String("string"),
},
},
},
IgnoredExceptions: &dynatrace.ServiceFailureExceptionRulesIgnoredExceptionsArgs{
CustomHandledExceptions: dynatrace.ServiceFailureExceptionRulesIgnoredExceptionsCustomHandledExceptionArray{
&dynatrace.ServiceFailureExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs{
ClassPattern: pulumi.String("string"),
MessagePattern: pulumi.String("string"),
},
},
},
SuccessForcingExceptions: &dynatrace.ServiceFailureExceptionRulesSuccessForcingExceptionsArgs{
CustomHandledExceptions: dynatrace.ServiceFailureExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArray{
&dynatrace.ServiceFailureExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs{
ClassPattern: pulumi.String("string"),
MessagePattern: pulumi.String("string"),
},
},
},
},
})
var serviceFailureResource = new ServiceFailure("serviceFailureResource", ServiceFailureArgs.builder()
.enabled(false)
.serviceId("string")
.exceptionRules(ServiceFailureExceptionRulesArgs.builder()
.ignoreAllExceptions(false)
.ignoreSpanFailureDetection(false)
.customErrorRules(ServiceFailureExceptionRulesCustomErrorRulesArgs.builder()
.customErrorRules(ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleArgs.builder()
.condition(ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs.builder()
.compareOperationType("string")
.caseSensitive(false)
.doubleValue(0)
.intValue(0)
.textValue("string")
.build())
.requestAttribute("string")
.build())
.build())
.customHandledExceptions(ServiceFailureExceptionRulesCustomHandledExceptionsArgs.builder()
.customHandledExceptions(ServiceFailureExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs.builder()
.classPattern("string")
.messagePattern("string")
.build())
.build())
.ignoredExceptions(ServiceFailureExceptionRulesIgnoredExceptionsArgs.builder()
.customHandledExceptions(ServiceFailureExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs.builder()
.classPattern("string")
.messagePattern("string")
.build())
.build())
.successForcingExceptions(ServiceFailureExceptionRulesSuccessForcingExceptionsArgs.builder()
.customHandledExceptions(ServiceFailureExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs.builder()
.classPattern("string")
.messagePattern("string")
.build())
.build())
.build())
.build());
service_failure_resource = dynatrace.ServiceFailure("serviceFailureResource",
enabled=False,
service_id="string",
exception_rules=dynatrace.ServiceFailureExceptionRulesArgs(
ignore_all_exceptions=False,
ignore_span_failure_detection=False,
custom_error_rules=dynatrace.ServiceFailureExceptionRulesCustomErrorRulesArgs(
custom_error_rules=[dynatrace.ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleArgs(
condition=dynatrace.ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs(
compare_operation_type="string",
case_sensitive=False,
double_value=0,
int_value=0,
text_value="string",
),
request_attribute="string",
)],
),
custom_handled_exceptions=dynatrace.ServiceFailureExceptionRulesCustomHandledExceptionsArgs(
custom_handled_exceptions=[dynatrace.ServiceFailureExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs(
class_pattern="string",
message_pattern="string",
)],
),
ignored_exceptions=dynatrace.ServiceFailureExceptionRulesIgnoredExceptionsArgs(
custom_handled_exceptions=[dynatrace.ServiceFailureExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs(
class_pattern="string",
message_pattern="string",
)],
),
success_forcing_exceptions=dynatrace.ServiceFailureExceptionRulesSuccessForcingExceptionsArgs(
custom_handled_exceptions=[dynatrace.ServiceFailureExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs(
class_pattern="string",
message_pattern="string",
)],
),
))
const serviceFailureResource = new dynatrace.ServiceFailure("serviceFailureResource", {
enabled: false,
serviceId: "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",
}],
},
},
});
type: dynatrace:ServiceFailure
properties:
enabled: false
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
serviceId: string
ServiceFailure 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 ServiceFailure resource accepts the following input properties:
- Enabled bool
- This setting is enabled (
true
) or disabled (false
) - Service
Id string - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- Exception
Rules Pulumiverse.Dynatrace. Inputs. Service Failure Exception Rules - Customize failure detection for specific exceptions and errors
- Enabled bool
- This setting is enabled (
true
) or disabled (false
) - Service
Id string - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- Exception
Rules ServiceFailure Exception Rules Args - Customize failure detection for specific exceptions and errors
- enabled Boolean
- This setting is enabled (
true
) or disabled (false
) - service
Id String - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- exception
Rules ServiceFailure Exception Rules - Customize failure detection for specific exceptions and errors
- enabled boolean
- This setting is enabled (
true
) or disabled (false
) - service
Id string - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- exception
Rules ServiceFailure Exception Rules - Customize failure detection for specific exceptions and errors
- enabled bool
- This setting is enabled (
true
) or disabled (false
) - service_
id str - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- exception_
rules ServiceFailure Exception Rules Args - Customize failure detection for specific exceptions and errors
- enabled Boolean
- This setting is enabled (
true
) or disabled (false
) - service
Id String - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- exception
Rules Property Map - Customize failure detection for specific exceptions and errors
Outputs
All input properties are implicitly available as output properties. Additionally, the ServiceFailure 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 ServiceFailure Resource
Get an existing ServiceFailure 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?: ServiceFailureState, opts?: CustomResourceOptions): ServiceFailure
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
enabled: Optional[bool] = None,
exception_rules: Optional[ServiceFailureExceptionRulesArgs] = None,
service_id: Optional[str] = None) -> ServiceFailure
func GetServiceFailure(ctx *Context, name string, id IDInput, state *ServiceFailureState, opts ...ResourceOption) (*ServiceFailure, error)
public static ServiceFailure Get(string name, Input<string> id, ServiceFailureState? state, CustomResourceOptions? opts = null)
public static ServiceFailure get(String name, Output<String> id, ServiceFailureState 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.
- Enabled bool
- This setting is enabled (
true
) or disabled (false
) - Exception
Rules Pulumiverse.Dynatrace. Inputs. Service Failure Exception Rules - Customize failure detection for specific exceptions and errors
- Service
Id string - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- Enabled bool
- This setting is enabled (
true
) or disabled (false
) - Exception
Rules ServiceFailure Exception Rules Args - Customize failure detection for specific exceptions and errors
- Service
Id string - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- enabled Boolean
- This setting is enabled (
true
) or disabled (false
) - exception
Rules ServiceFailure Exception Rules - Customize failure detection for specific exceptions and errors
- service
Id String - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- enabled boolean
- This setting is enabled (
true
) or disabled (false
) - exception
Rules ServiceFailure Exception Rules - Customize failure detection for specific exceptions and errors
- service
Id string - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- enabled bool
- This setting is enabled (
true
) or disabled (false
) - exception_
rules ServiceFailure Exception Rules Args - Customize failure detection for specific exceptions and errors
- service_
id str - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
- enabled Boolean
- This setting is enabled (
true
) or disabled (false
) - exception
Rules Property Map - Customize failure detection for specific exceptions and errors
- service
Id String - The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
Supporting Types
ServiceFailureExceptionRules, ServiceFailureExceptionRulesArgs
- Ignore
All boolExceptions - Ignore all exceptions
- Ignore
Span boolFailure Detection - Ignore span failure detection
- Custom
Error Pulumiverse.Rules Dynatrace. Inputs. Service Failure 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. Service Failure 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. Service Failure 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. Service Failure 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 ServiceRules Failure 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 ServiceExceptions Failure 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 ServiceFailure 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 ServiceExceptions Failure 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 ServiceRules Failure 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 ServiceExceptions Failure 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 ServiceFailure 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 ServiceExceptions Failure 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 ServiceRules Failure 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 ServiceExceptions Failure 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 ServiceFailure 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 ServiceExceptions Failure 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_ Servicerules Failure 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_ Serviceexceptions Failure 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 ServiceFailure 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_ Serviceexceptions Failure 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.
ServiceFailureExceptionRulesCustomErrorRules, ServiceFailureExceptionRulesCustomErrorRulesArgs
ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRule, ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleArgs
- Condition
Pulumiverse.
Dynatrace. Inputs. Service Failure Exception Rules Custom Error Rules Custom Error Rule Condition - Request attribute condition
- Request
Attribute string - Request attribute
- Condition
Service
Failure Exception Rules Custom Error Rules Custom Error Rule Condition - Request attribute condition
- Request
Attribute string - Request attribute
- condition
Service
Failure Exception Rules Custom Error Rules Custom Error Rule Condition - Request attribute condition
- request
Attribute String - Request attribute
- condition
Service
Failure Exception Rules Custom Error Rules Custom Error Rule Condition - Request attribute condition
- request
Attribute string - Request attribute
- condition
Service
Failure 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
ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleCondition, ServiceFailureExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs
- 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
ServiceFailureExceptionRulesCustomHandledExceptions, ServiceFailureExceptionRulesCustomHandledExceptionsArgs
ServiceFailureExceptionRulesCustomHandledExceptionsCustomHandledException, ServiceFailureExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs
- 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.
ServiceFailureExceptionRulesIgnoredExceptions, ServiceFailureExceptionRulesIgnoredExceptionsArgs
ServiceFailureExceptionRulesIgnoredExceptionsCustomHandledException, ServiceFailureExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs
- 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.
ServiceFailureExceptionRulesSuccessForcingExceptions, ServiceFailureExceptionRulesSuccessForcingExceptionsArgs
ServiceFailureExceptionRulesSuccessForcingExceptionsCustomHandledException, ServiceFailureExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs
- 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.
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dynatrace
Terraform Provider.