Docs Packages
  1. Packages
  2. Dynatrace
  3. API Docs
  4. ServiceHttpFailure
Dynatrace v0.1.0 published on Wednesday, May 24, 2023 by Lbrlabs
lbrlabs/pulumi-dynatrace

dynatrace.ServiceHttpFailure

Explore with Pulumi AI

dynatrace logo
Dynatrace v0.1.0 published on Wednesday, May 24, 2023 by Lbrlabs
lbrlabs/pulumi-dynatrace

    Create ServiceHttpFailure Resource

    Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.

    Constructor syntax

    new ServiceHttpFailure(name: string, args: ServiceHttpFailureArgs, opts?: CustomResourceOptions);
    @overload
def ServiceHttpFailure(resource_name: str,
                       args: ServiceHttpFailureArgs,
                       opts: Optional[ResourceOptions] = None)

@overload
def ServiceHttpFailure(resource_name: str,
                       opts: Optional[ResourceOptions] = None,
                       enabled: Optional[bool] = None,
                       service_id: Optional[str] = None,
                       broken_links: Optional[ServiceHttpFailureBrokenLinksArgs] = None,
                       http_response_codes: Optional[ServiceHttpFailureHttpResponseCodesArgs] = None)
    func NewServiceHttpFailure(ctx *Context, name string, args ServiceHttpFailureArgs, opts ...ResourceOption) (*ServiceHttpFailure, error)
    public ServiceHttpFailure(string name, ServiceHttpFailureArgs args, CustomResourceOptions? opts = null)
    public ServiceHttpFailure(String name, ServiceHttpFailureArgs args)
public ServiceHttpFailure(String name, ServiceHttpFailureArgs args, CustomResourceOptions options)

    type: dynatrace:ServiceHttpFailure
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 ServiceHttpFailureArgs
    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 ServiceHttpFailureArgs
    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 ServiceHttpFailureArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args ServiceHttpFailureArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args ServiceHttpFailureArgs
    The arguments to resource properties.
    options CustomResourceOptions
    Bag of options to control resource's behavior.

    Example

    The following reference example uses placeholder values for all input properties.

    var serviceHttpFailureResource = new Dynatrace.ServiceHttpFailure("serviceHttpFailureResource", new()
{
    Enabled = false,
    ServiceId = "string",
    BrokenLinks = new Dynatrace.Inputs.ServiceHttpFailureBrokenLinksArgs
    {
        Http404NotFoundFailures = false,
        BrokenLinkDomains = new[]
        {
            "string",
        },
    },
    HttpResponseCodes = new Dynatrace.Inputs.ServiceHttpFailureHttpResponseCodesArgs
    {
        ClientSideErrors = "string",
        FailOnMissingResponseCodeClientSide = false,
        FailOnMissingResponseCodeServerSide = false,
        ServerSideErrors = "string",
    },
});

    example, err := dynatrace.NewServiceHttpFailure(ctx, "serviceHttpFailureResource", &dynatrace.ServiceHttpFailureArgs{
	Enabled:   pulumi.Bool(false),
	ServiceId: pulumi.String("string"),
	BrokenLinks: &dynatrace.ServiceHttpFailureBrokenLinksArgs{
		Http404NotFoundFailures: pulumi.Bool(false),
		BrokenLinkDomains: pulumi.StringArray{
			pulumi.String("string"),
		},
	},
	HttpResponseCodes: &dynatrace.ServiceHttpFailureHttpResponseCodesArgs{
		ClientSideErrors:                    pulumi.String("string"),
		FailOnMissingResponseCodeClientSide: pulumi.Bool(false),
		FailOnMissingResponseCodeServerSide: pulumi.Bool(false),
		ServerSideErrors:                    pulumi.String("string"),
	},
})

    var serviceHttpFailureResource = new ServiceHttpFailure("serviceHttpFailureResource", ServiceHttpFailureArgs.builder()        
    .enabled(false)
    .serviceId("string")
    .brokenLinks(ServiceHttpFailureBrokenLinksArgs.builder()
        .http404NotFoundFailures(false)
        .brokenLinkDomains("string")
        .build())
    .httpResponseCodes(ServiceHttpFailureHttpResponseCodesArgs.builder()
        .clientSideErrors("string")
        .failOnMissingResponseCodeClientSide(false)
        .failOnMissingResponseCodeServerSide(false)
        .serverSideErrors("string")
        .build())
    .build());

    service_http_failure_resource = dynatrace.ServiceHttpFailure("serviceHttpFailureResource",
    enabled=False,
    service_id="string",
    broken_links=dynatrace.ServiceHttpFailureBrokenLinksArgs(
        http404_not_found_failures=False,
        broken_link_domains=["string"],
    ),
    http_response_codes=dynatrace.ServiceHttpFailureHttpResponseCodesArgs(
        client_side_errors="string",
        fail_on_missing_response_code_client_side=False,
        fail_on_missing_response_code_server_side=False,
        server_side_errors="string",
    ))

    const serviceHttpFailureResource = new dynatrace.ServiceHttpFailure("serviceHttpFailureResource", {
    enabled: false,
    serviceId: "string",
    brokenLinks: {
        http404NotFoundFailures: false,
        brokenLinkDomains: ["string"],
    },
    httpResponseCodes: {
        clientSideErrors: "string",
        failOnMissingResponseCodeClientSide: false,
        failOnMissingResponseCodeServerSide: false,
        serverSideErrors: "string",
    },
});

    type: dynatrace:ServiceHttpFailure
properties:
    brokenLinks:
        brokenLinkDomains:
            - string
        http404NotFoundFailures: false
    enabled: false
    httpResponseCodes:
        clientSideErrors: string
        failOnMissingResponseCodeClientSide: false
        failOnMissingResponseCodeServerSide: false
        serverSideErrors: string
    serviceId: string

    ServiceHttpFailure 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 ServiceHttpFailure resource accepts the following input properties:

    Enabled bool
    This setting is enabled (true) or disabled (false)
    ServiceId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    BrokenLinks Lbrlabs.PulumiPackage.Dynatrace.Inputs.ServiceHttpFailureBrokenLinks
    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.
    HttpResponseCodes Lbrlabs.PulumiPackage.Dynatrace.Inputs.ServiceHttpFailureHttpResponseCodes
    HTTP response codes
    Enabled bool
    This setting is enabled (true) or disabled (false)
    ServiceId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    BrokenLinks ServiceHttpFailureBrokenLinksArgs
    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.
    HttpResponseCodes ServiceHttpFailureHttpResponseCodesArgs
    HTTP response codes
    enabled Boolean
    This setting is enabled (true) or disabled (false)
    serviceId String
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    brokenLinks ServiceHttpFailureBrokenLinks
    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.
    httpResponseCodes ServiceHttpFailureHttpResponseCodes
    HTTP response codes
    enabled boolean
    This setting is enabled (true) or disabled (false)
    serviceId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    brokenLinks ServiceHttpFailureBrokenLinks
    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.
    httpResponseCodes ServiceHttpFailureHttpResponseCodes
    HTTP response codes
    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.
    broken_links ServiceHttpFailureBrokenLinksArgs
    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.
    http_response_codes ServiceHttpFailureHttpResponseCodesArgs
    HTTP response codes
    enabled Boolean
    This setting is enabled (true) or disabled (false)
    serviceId String
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    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.
    httpResponseCodes Property Map
    HTTP response codes

    Outputs

    All input properties are implicitly available as output properties. Additionally, the ServiceHttpFailure 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 ServiceHttpFailure Resource

    Get an existing ServiceHttpFailure 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?: ServiceHttpFailureState, opts?: CustomResourceOptions): ServiceHttpFailure
    @staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        broken_links: Optional[ServiceHttpFailureBrokenLinksArgs] = None,
        enabled: Optional[bool] = None,
        http_response_codes: Optional[ServiceHttpFailureHttpResponseCodesArgs] = None,
        service_id: Optional[str] = None) -> ServiceHttpFailure
    func GetServiceHttpFailure(ctx *Context, name string, id IDInput, state *ServiceHttpFailureState, opts ...ResourceOption) (*ServiceHttpFailure, error)
    public static ServiceHttpFailure Get(string name, Input<string> id, ServiceHttpFailureState? state, CustomResourceOptions? opts = null)
    public static ServiceHttpFailure get(String name, Output<String> id, ServiceHttpFailureState 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.ServiceHttpFailureBrokenLinks
    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.
    Enabled bool
    This setting is enabled (true) or disabled (false)
    HttpResponseCodes Lbrlabs.PulumiPackage.Dynatrace.Inputs.ServiceHttpFailureHttpResponseCodes
    HTTP response codes
    ServiceId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    BrokenLinks ServiceHttpFailureBrokenLinksArgs
    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.
    Enabled bool
    This setting is enabled (true) or disabled (false)
    HttpResponseCodes ServiceHttpFailureHttpResponseCodesArgs
    HTTP response codes
    ServiceId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    brokenLinks ServiceHttpFailureBrokenLinks
    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.
    enabled Boolean
    This setting is enabled (true) or disabled (false)
    httpResponseCodes ServiceHttpFailureHttpResponseCodes
    HTTP response codes
    serviceId String
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    brokenLinks ServiceHttpFailureBrokenLinks
    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.
    enabled boolean
    This setting is enabled (true) or disabled (false)
    httpResponseCodes ServiceHttpFailureHttpResponseCodes
    HTTP response codes
    serviceId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    broken_links ServiceHttpFailureBrokenLinksArgs
    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.
    enabled bool
    This setting is enabled (true) or disabled (false)
    http_response_codes ServiceHttpFailureHttpResponseCodesArgs
    HTTP response codes
    service_id str
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    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.
    enabled Boolean
    This setting is enabled (true) or disabled (false)
    httpResponseCodes Property Map
    HTTP response codes
    serviceId String
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.

    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.

    ServiceHttpFailureHttpResponseCodes, ServiceHttpFailureHttpResponseCodesArgs

    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
    lbrlabs/pulumi-dynatrace