1. Packages
  2. Dynatrace
  3. API Docs
  4. FailureDetectionParameters
Dynatrace v0.1.0 published on Wednesday, May 24, 2023 by Lbrlabs

dynatrace.FailureDetectionParameters

Explore with Pulumi AI

dynatrace logo
Dynatrace v0.1.0 published on Wednesday, May 24, 2023 by Lbrlabs

    Create FailureDetectionParameters Resource

    new FailureDetectionParameters(name: string, args: FailureDetectionParametersArgs, opts?: CustomResourceOptions);
    @overload
    def FailureDetectionParameters(resource_name: 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)
    @overload
    def FailureDetectionParameters(resource_name: str,
                                   args: FailureDetectionParametersArgs,
                                   opts: Optional[ResourceOptions] = 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.
    
    
    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.

    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:

    BrokenLinks Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersBrokenLinks
    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.
    ExceptionRules Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersExceptionRules
    Customize failure detection for specific exceptions and errors
    HttpResponseCodes Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersHttpResponseCodes
    HTTP response codes
    Description string
    Description
    Name string
    Name
    BrokenLinks FailureDetectionParametersBrokenLinksArgs
    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.
    ExceptionRules FailureDetectionParametersExceptionRulesArgs
    Customize failure detection for specific exceptions and errors
    HttpResponseCodes FailureDetectionParametersHttpResponseCodesArgs
    HTTP response codes
    Description string
    Description
    Name string
    Name
    brokenLinks FailureDetectionParametersBrokenLinks
    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.
    exceptionRules FailureDetectionParametersExceptionRules
    Customize failure detection for specific exceptions and errors
    httpResponseCodes FailureDetectionParametersHttpResponseCodes
    HTTP response codes
    description String
    Description
    name String
    Name
    brokenLinks FailureDetectionParametersBrokenLinks
    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.
    exceptionRules FailureDetectionParametersExceptionRules
    Customize failure detection for specific exceptions and errors
    httpResponseCodes FailureDetectionParametersHttpResponseCodes
    HTTP response codes
    description string
    Description
    name string
    Name
    broken_links FailureDetectionParametersBrokenLinksArgs
    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 FailureDetectionParametersExceptionRulesArgs
    Customize failure detection for specific exceptions and errors
    http_response_codes FailureDetectionParametersHttpResponseCodesArgs
    HTTP response codes
    description str
    Description
    name str
    Name
    brokenLinks 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.
    exceptionRules Property Map
    Customize failure detection for specific exceptions and errors
    httpResponseCodes Property Map
    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.
    The following state arguments are supported:
    BrokenLinks Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersBrokenLinks
    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
    ExceptionRules Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersExceptionRules
    Customize failure detection for specific exceptions and errors
    HttpResponseCodes Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersHttpResponseCodes
    HTTP response codes
    Name string
    Name
    BrokenLinks FailureDetectionParametersBrokenLinksArgs
    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
    ExceptionRules FailureDetectionParametersExceptionRulesArgs
    Customize failure detection for specific exceptions and errors
    HttpResponseCodes FailureDetectionParametersHttpResponseCodesArgs
    HTTP response codes
    Name string
    Name
    brokenLinks FailureDetectionParametersBrokenLinks
    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
    exceptionRules FailureDetectionParametersExceptionRules
    Customize failure detection for specific exceptions and errors
    httpResponseCodes FailureDetectionParametersHttpResponseCodes
    HTTP response codes
    name String
    Name
    brokenLinks FailureDetectionParametersBrokenLinks
    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
    exceptionRules FailureDetectionParametersExceptionRules
    Customize failure detection for specific exceptions and errors
    httpResponseCodes FailureDetectionParametersHttpResponseCodes
    HTTP response codes
    name string
    Name
    broken_links FailureDetectionParametersBrokenLinksArgs
    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 FailureDetectionParametersExceptionRulesArgs
    Customize failure detection for specific exceptions and errors
    http_response_codes FailureDetectionParametersHttpResponseCodesArgs
    HTTP response codes
    name str
    Name
    brokenLinks 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
    exceptionRules Property Map
    Customize failure detection for specific exceptions and errors
    httpResponseCodes Property Map
    HTTP response codes
    name String
    Name

    Supporting Types

    Http404NotFoundFailures bool
    Consider 404 HTTP response codes as failures
    BrokenLinkDomains List<string>
    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.
    Http404NotFoundFailures bool
    Consider 404 HTTP response codes as failures
    BrokenLinkDomains []string
    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.
    http404NotFoundFailures Boolean
    Consider 404 HTTP response codes as failures
    brokenLinkDomains List<String>
    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.
    http404NotFoundFailures boolean
    Consider 404 HTTP response codes as failures
    brokenLinkDomains string[]
    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_found_failures bool
    Consider 404 HTTP response codes as failures
    broken_link_domains Sequence[str]
    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.
    http404NotFoundFailures Boolean
    Consider 404 HTTP response codes as failures
    brokenLinkDomains List<String>
    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

    IgnoreAllExceptions bool
    Ignore all exceptions
    IgnoreSpanFailureDetection bool
    Ignore span failure detection
    CustomErrorRules Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersExceptionRulesCustomErrorRules
    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.
    CustomHandledExceptions Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersExceptionRulesCustomHandledExceptions
    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.
    IgnoredExceptions Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersExceptionRulesIgnoredExceptions
    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.
    SuccessForcingExceptions Lbrlabs.PulumiPackage.Dynatrace.Inputs.FailureDetectionParametersExceptionRulesSuccessForcingExceptions
    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.
    IgnoreAllExceptions bool
    Ignore all exceptions
    IgnoreSpanFailureDetection bool
    Ignore span failure detection
    CustomErrorRules FailureDetectionParametersExceptionRulesCustomErrorRules
    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.
    CustomHandledExceptions FailureDetectionParametersExceptionRulesCustomHandledExceptions
    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.
    IgnoredExceptions FailureDetectionParametersExceptionRulesIgnoredExceptions
    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.
    SuccessForcingExceptions FailureDetectionParametersExceptionRulesSuccessForcingExceptions
    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.
    ignoreAllExceptions Boolean
    Ignore all exceptions
    ignoreSpanFailureDetection Boolean
    Ignore span failure detection
    customErrorRules FailureDetectionParametersExceptionRulesCustomErrorRules
    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.
    customHandledExceptions FailureDetectionParametersExceptionRulesCustomHandledExceptions
    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.
    ignoredExceptions FailureDetectionParametersExceptionRulesIgnoredExceptions
    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.
    successForcingExceptions FailureDetectionParametersExceptionRulesSuccessForcingExceptions
    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.
    ignoreAllExceptions boolean
    Ignore all exceptions
    ignoreSpanFailureDetection boolean
    Ignore span failure detection
    customErrorRules FailureDetectionParametersExceptionRulesCustomErrorRules
    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.
    customHandledExceptions FailureDetectionParametersExceptionRulesCustomHandledExceptions
    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.
    ignoredExceptions FailureDetectionParametersExceptionRulesIgnoredExceptions
    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.
    successForcingExceptions FailureDetectionParametersExceptionRulesSuccessForcingExceptions
    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_exceptions bool
    Ignore all exceptions
    ignore_span_failure_detection bool
    Ignore span failure detection
    custom_error_rules FailureDetectionParametersExceptionRulesCustomErrorRules
    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_exceptions FailureDetectionParametersExceptionRulesCustomHandledExceptions
    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 FailureDetectionParametersExceptionRulesIgnoredExceptions
    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_exceptions FailureDetectionParametersExceptionRulesSuccessForcingExceptions
    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.
    ignoreAllExceptions Boolean
    Ignore all exceptions
    ignoreSpanFailureDetection Boolean
    Ignore span failure detection
    customErrorRules Property Map
    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.
    customHandledExceptions Property Map
    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.
    ignoredExceptions 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.
    successForcingExceptions Property Map
    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

    FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleCondition, FailureDetectionParametersExceptionRulesCustomErrorRulesCustomErrorRuleConditionArgs

    FailureDetectionParametersExceptionRulesCustomHandledExceptions, FailureDetectionParametersExceptionRulesCustomHandledExceptionsArgs

    FailureDetectionParametersExceptionRulesCustomHandledExceptionsCustomHandledException, FailureDetectionParametersExceptionRulesCustomHandledExceptionsCustomHandledExceptionArgs

    FailureDetectionParametersExceptionRulesIgnoredExceptions, FailureDetectionParametersExceptionRulesIgnoredExceptionsArgs

    FailureDetectionParametersExceptionRulesIgnoredExceptionsCustomHandledException, FailureDetectionParametersExceptionRulesIgnoredExceptionsCustomHandledExceptionArgs

    FailureDetectionParametersExceptionRulesSuccessForcingExceptions, FailureDetectionParametersExceptionRulesSuccessForcingExceptionsArgs

    FailureDetectionParametersExceptionRulesSuccessForcingExceptionsCustomHandledException, FailureDetectionParametersExceptionRulesSuccessForcingExceptionsCustomHandledExceptionArgs

    FailureDetectionParametersHttpResponseCodes, FailureDetectionParametersHttpResponseCodesArgs

    ClientSideErrors string
    HTTP response codes which indicate client side errors
    FailOnMissingResponseCodeClientSide bool
    Treat missing HTTP response code as client side error
    FailOnMissingResponseCodeServerSide bool
    Treat missing HTTP response code as server side errors
    ServerSideErrors string
    HTTP response codes which indicate an error on the server side
    ClientSideErrors string
    HTTP response codes which indicate client side errors
    FailOnMissingResponseCodeClientSide bool
    Treat missing HTTP response code as client side error
    FailOnMissingResponseCodeServerSide bool
    Treat missing HTTP response code as server side errors
    ServerSideErrors string
    HTTP response codes which indicate an error on the server side
    clientSideErrors String
    HTTP response codes which indicate client side errors
    failOnMissingResponseCodeClientSide Boolean
    Treat missing HTTP response code as client side error
    failOnMissingResponseCodeServerSide Boolean
    Treat missing HTTP response code as server side errors
    serverSideErrors String
    HTTP response codes which indicate an error on the server side
    clientSideErrors string
    HTTP response codes which indicate client side errors
    failOnMissingResponseCodeClientSide boolean
    Treat missing HTTP response code as client side error
    failOnMissingResponseCodeServerSide boolean
    Treat missing HTTP response code as server side errors
    serverSideErrors string
    HTTP response codes which indicate an error on the server side
    client_side_errors str
    HTTP response codes which indicate client side errors
    fail_on_missing_response_code_client_side bool
    Treat missing HTTP response code as client side error
    fail_on_missing_response_code_server_side bool
    Treat missing HTTP response code as server side errors
    server_side_errors str
    HTTP response codes which indicate an error on the server side
    clientSideErrors String
    HTTP response codes which indicate client side errors
    failOnMissingResponseCodeClientSide Boolean
    Treat missing HTTP response code as client side error
    failOnMissingResponseCodeServerSide Boolean
    Treat missing HTTP response code as server side errors
    serverSideErrors String
    HTTP response codes which indicate an error on the server side

    Package Details

    Repository
    dynatrace lbrlabs/pulumi-dynatrace
    License
    Apache-2.0
    Notes
    This Pulumi package is based on the dynatrace Terraform Provider.
    dynatrace logo
    Dynatrace v0.1.0 published on Wednesday, May 24, 2023 by Lbrlabs