Docs Home Pulumi IaC Pulumi ESC Pulumi Cloud Packages Tutorials
  1. Packages
  2. Dynatrace
  3. API Docs
  4. ProcessGroupDetectionFlags
Dynatrace v0.21.0 published on Sunday, Nov 17, 2024 by Pulumiverse
lbrlabs/pulumi-dynatrace

dynatrace.ProcessGroupDetectionFlags

Explore with Pulumi AI

dynatrace logo
Dynatrace v0.21.0 published on Sunday, Nov 17, 2024 by Pulumiverse
lbrlabs/pulumi-dynatrace

    Create ProcessGroupDetectionFlags Resource

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

    Constructor syntax

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

@overload
def ProcessGroupDetectionFlags(resource_name: str,
                               opts: Optional[ResourceOptions] = None,
                               identify_jboss_server_by_system_property: Optional[bool] = None,
                               auto_detect_web_sphere_liberty_application: Optional[bool] = None,
                               auto_detect_spring_boot: Optional[bool] = None,
                               auto_detect_tibco_container_edition_engines: Optional[bool] = None,
                               add_node_js_script_name: Optional[bool] = None,
                               auto_detect_web_methods_integration_server: Optional[bool] = None,
                               auto_detect_cassandra_clusters: Optional[bool] = None,
                               group_ibmmqby_instance_name: Optional[bool] = None,
                               auto_detect_tibco_engines: Optional[bool] = None,
                               ignore_unique_identifiers: Optional[bool] = None,
                               use_docker_container_name: Optional[bool] = None,
                               short_lived_processes_monitoring: Optional[bool] = None,
                               split_oracle_database_pg: Optional[bool] = None,
                               split_oracle_listener_pg: Optional[bool] = None,
                               use_catalina_base: Optional[bool] = None,
                               scope: Optional[str] = None)
    func NewProcessGroupDetectionFlags(ctx *Context, name string, args ProcessGroupDetectionFlagsArgs, opts ...ResourceOption) (*ProcessGroupDetectionFlags, error)
    public ProcessGroupDetectionFlags(string name, ProcessGroupDetectionFlagsArgs args, CustomResourceOptions? opts = null)
    public ProcessGroupDetectionFlags(String name, ProcessGroupDetectionFlagsArgs args)
public ProcessGroupDetectionFlags(String name, ProcessGroupDetectionFlagsArgs args, CustomResourceOptions options)

    type: dynatrace:ProcessGroupDetectionFlags
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 ProcessGroupDetectionFlagsArgs
    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 ProcessGroupDetectionFlagsArgs
    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 ProcessGroupDetectionFlagsArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args ProcessGroupDetectionFlagsArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args ProcessGroupDetectionFlagsArgs
    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 processGroupDetectionFlagsResource = new Dynatrace.ProcessGroupDetectionFlags("processGroupDetectionFlagsResource", new()
{
    IdentifyJbossServerBySystemProperty = false,
    AutoDetectWebSphereLibertyApplication = false,
    AutoDetectSpringBoot = false,
    AutoDetectTibcoContainerEditionEngines = false,
    AddNodeJsScriptName = false,
    AutoDetectWebMethodsIntegrationServer = false,
    AutoDetectCassandraClusters = false,
    GroupIbmmqbyInstanceName = false,
    AutoDetectTibcoEngines = false,
    IgnoreUniqueIdentifiers = false,
    UseDockerContainerName = false,
    ShortLivedProcessesMonitoring = false,
    SplitOracleDatabasePg = false,
    SplitOracleListenerPg = false,
    UseCatalinaBase = false,
    Scope = "string",
});

    example, err := dynatrace.NewProcessGroupDetectionFlags(ctx, "processGroupDetectionFlagsResource", &dynatrace.ProcessGroupDetectionFlagsArgs{
	IdentifyJbossServerBySystemProperty:    pulumi.Bool(false),
	AutoDetectWebSphereLibertyApplication:  pulumi.Bool(false),
	AutoDetectSpringBoot:                   pulumi.Bool(false),
	AutoDetectTibcoContainerEditionEngines: pulumi.Bool(false),
	AddNodeJsScriptName:                    pulumi.Bool(false),
	AutoDetectWebMethodsIntegrationServer:  pulumi.Bool(false),
	AutoDetectCassandraClusters:            pulumi.Bool(false),
	GroupIbmmqbyInstanceName:               pulumi.Bool(false),
	AutoDetectTibcoEngines:                 pulumi.Bool(false),
	IgnoreUniqueIdentifiers:                pulumi.Bool(false),
	UseDockerContainerName:                 pulumi.Bool(false),
	ShortLivedProcessesMonitoring:          pulumi.Bool(false),
	SplitOracleDatabasePg:                  pulumi.Bool(false),
	SplitOracleListenerPg:                  pulumi.Bool(false),
	UseCatalinaBase:                        pulumi.Bool(false),
	Scope:                                  pulumi.String("string"),
})

    var processGroupDetectionFlagsResource = new ProcessGroupDetectionFlags("processGroupDetectionFlagsResource", ProcessGroupDetectionFlagsArgs.builder()
    .identifyJbossServerBySystemProperty(false)
    .autoDetectWebSphereLibertyApplication(false)
    .autoDetectSpringBoot(false)
    .autoDetectTibcoContainerEditionEngines(false)
    .addNodeJsScriptName(false)
    .autoDetectWebMethodsIntegrationServer(false)
    .autoDetectCassandraClusters(false)
    .groupIbmmqbyInstanceName(false)
    .autoDetectTibcoEngines(false)
    .ignoreUniqueIdentifiers(false)
    .useDockerContainerName(false)
    .shortLivedProcessesMonitoring(false)
    .splitOracleDatabasePg(false)
    .splitOracleListenerPg(false)
    .useCatalinaBase(false)
    .scope("string")
    .build());

    process_group_detection_flags_resource = dynatrace.ProcessGroupDetectionFlags("processGroupDetectionFlagsResource",
    identify_jboss_server_by_system_property=False,
    auto_detect_web_sphere_liberty_application=False,
    auto_detect_spring_boot=False,
    auto_detect_tibco_container_edition_engines=False,
    add_node_js_script_name=False,
    auto_detect_web_methods_integration_server=False,
    auto_detect_cassandra_clusters=False,
    group_ibmmqby_instance_name=False,
    auto_detect_tibco_engines=False,
    ignore_unique_identifiers=False,
    use_docker_container_name=False,
    short_lived_processes_monitoring=False,
    split_oracle_database_pg=False,
    split_oracle_listener_pg=False,
    use_catalina_base=False,
    scope="string")

    const processGroupDetectionFlagsResource = new dynatrace.ProcessGroupDetectionFlags("processGroupDetectionFlagsResource", {
    identifyJbossServerBySystemProperty: false,
    autoDetectWebSphereLibertyApplication: false,
    autoDetectSpringBoot: false,
    autoDetectTibcoContainerEditionEngines: false,
    addNodeJsScriptName: false,
    autoDetectWebMethodsIntegrationServer: false,
    autoDetectCassandraClusters: false,
    groupIbmmqbyInstanceName: false,
    autoDetectTibcoEngines: false,
    ignoreUniqueIdentifiers: false,
    useDockerContainerName: false,
    shortLivedProcessesMonitoring: false,
    splitOracleDatabasePg: false,
    splitOracleListenerPg: false,
    useCatalinaBase: false,
    scope: "string",
});

    type: dynatrace:ProcessGroupDetectionFlags
properties:
    addNodeJsScriptName: false
    autoDetectCassandraClusters: false
    autoDetectSpringBoot: false
    autoDetectTibcoContainerEditionEngines: false
    autoDetectTibcoEngines: false
    autoDetectWebMethodsIntegrationServer: false
    autoDetectWebSphereLibertyApplication: false
    groupIbmmqbyInstanceName: false
    identifyJbossServerBySystemProperty: false
    ignoreUniqueIdentifiers: false
    scope: string
    shortLivedProcessesMonitoring: false
    splitOracleDatabasePg: false
    splitOracleListenerPg: false
    useCatalinaBase: false
    useDockerContainerName: false

    ProcessGroupDetectionFlags Resource Properties

    To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.

    Inputs

    In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.

    The ProcessGroupDetectionFlags resource accepts the following input properties:

    AddNodeJsScriptName bool
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    AutoDetectCassandraClusters bool
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    AutoDetectSpringBoot bool
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    AutoDetectTibcoContainerEditionEngines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    AutoDetectTibcoEngines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    AutoDetectWebMethodsIntegrationServer bool
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    AutoDetectWebSphereLibertyApplication bool
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    GroupIbmmqbyInstanceName bool
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    IdentifyJbossServerBySystemProperty bool
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    IgnoreUniqueIdentifiers bool
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    ShortLivedProcessesMonitoring bool
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    SplitOracleDatabasePg bool
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    SplitOracleListenerPg bool
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    UseCatalinaBase bool
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    UseDockerContainerName bool
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    Scope string
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    AddNodeJsScriptName bool
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    AutoDetectCassandraClusters bool
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    AutoDetectSpringBoot bool
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    AutoDetectTibcoContainerEditionEngines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    AutoDetectTibcoEngines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    AutoDetectWebMethodsIntegrationServer bool
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    AutoDetectWebSphereLibertyApplication bool
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    GroupIbmmqbyInstanceName bool
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    IdentifyJbossServerBySystemProperty bool
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    IgnoreUniqueIdentifiers bool
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    ShortLivedProcessesMonitoring bool
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    SplitOracleDatabasePg bool
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    SplitOracleListenerPg bool
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    UseCatalinaBase bool
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    UseDockerContainerName bool
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    Scope string
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    addNodeJsScriptName Boolean
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    autoDetectCassandraClusters Boolean
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    autoDetectSpringBoot Boolean
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    autoDetectTibcoContainerEditionEngines Boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectTibcoEngines Boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectWebMethodsIntegrationServer Boolean
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    autoDetectWebSphereLibertyApplication Boolean
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    groupIbmmqbyInstanceName Boolean
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    identifyJbossServerBySystemProperty Boolean
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    ignoreUniqueIdentifiers Boolean
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    shortLivedProcessesMonitoring Boolean
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    splitOracleDatabasePg Boolean
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    splitOracleListenerPg Boolean
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    useCatalinaBase Boolean
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    useDockerContainerName Boolean
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    scope String
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    addNodeJsScriptName boolean
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    autoDetectCassandraClusters boolean
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    autoDetectSpringBoot boolean
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    autoDetectTibcoContainerEditionEngines boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectTibcoEngines boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectWebMethodsIntegrationServer boolean
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    autoDetectWebSphereLibertyApplication boolean
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    groupIbmmqbyInstanceName boolean
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    identifyJbossServerBySystemProperty boolean
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    ignoreUniqueIdentifiers boolean
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    shortLivedProcessesMonitoring boolean
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    splitOracleDatabasePg boolean
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    splitOracleListenerPg boolean
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    useCatalinaBase boolean
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    useDockerContainerName boolean
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    scope string
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    add_node_js_script_name bool
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    auto_detect_cassandra_clusters bool
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    auto_detect_spring_boot bool
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    auto_detect_tibco_container_edition_engines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    auto_detect_tibco_engines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    auto_detect_web_methods_integration_server bool
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    auto_detect_web_sphere_liberty_application bool
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    group_ibmmqby_instance_name bool
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    identify_jboss_server_by_system_property bool
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    ignore_unique_identifiers bool
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    short_lived_processes_monitoring bool
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    split_oracle_database_pg bool
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    split_oracle_listener_pg bool
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    use_catalina_base bool
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    use_docker_container_name bool
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    scope str
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    addNodeJsScriptName Boolean
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    autoDetectCassandraClusters Boolean
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    autoDetectSpringBoot Boolean
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    autoDetectTibcoContainerEditionEngines Boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectTibcoEngines Boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectWebMethodsIntegrationServer Boolean
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    autoDetectWebSphereLibertyApplication Boolean
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    groupIbmmqbyInstanceName Boolean
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    identifyJbossServerBySystemProperty Boolean
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    ignoreUniqueIdentifiers Boolean
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    shortLivedProcessesMonitoring Boolean
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    splitOracleDatabasePg Boolean
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    splitOracleListenerPg Boolean
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    useCatalinaBase Boolean
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    useDockerContainerName Boolean
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    scope String
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.

    Outputs

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

    Get an existing ProcessGroupDetectionFlags 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?: ProcessGroupDetectionFlagsState, opts?: CustomResourceOptions): ProcessGroupDetectionFlags
    @staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        add_node_js_script_name: Optional[bool] = None,
        auto_detect_cassandra_clusters: Optional[bool] = None,
        auto_detect_spring_boot: Optional[bool] = None,
        auto_detect_tibco_container_edition_engines: Optional[bool] = None,
        auto_detect_tibco_engines: Optional[bool] = None,
        auto_detect_web_methods_integration_server: Optional[bool] = None,
        auto_detect_web_sphere_liberty_application: Optional[bool] = None,
        group_ibmmqby_instance_name: Optional[bool] = None,
        identify_jboss_server_by_system_property: Optional[bool] = None,
        ignore_unique_identifiers: Optional[bool] = None,
        scope: Optional[str] = None,
        short_lived_processes_monitoring: Optional[bool] = None,
        split_oracle_database_pg: Optional[bool] = None,
        split_oracle_listener_pg: Optional[bool] = None,
        use_catalina_base: Optional[bool] = None,
        use_docker_container_name: Optional[bool] = None) -> ProcessGroupDetectionFlags
    func GetProcessGroupDetectionFlags(ctx *Context, name string, id IDInput, state *ProcessGroupDetectionFlagsState, opts ...ResourceOption) (*ProcessGroupDetectionFlags, error)
    public static ProcessGroupDetectionFlags Get(string name, Input<string> id, ProcessGroupDetectionFlagsState? state, CustomResourceOptions? opts = null)
    public static ProcessGroupDetectionFlags get(String name, Output<String> id, ProcessGroupDetectionFlagsState 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:
    AddNodeJsScriptName bool
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    AutoDetectCassandraClusters bool
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    AutoDetectSpringBoot bool
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    AutoDetectTibcoContainerEditionEngines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    AutoDetectTibcoEngines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    AutoDetectWebMethodsIntegrationServer bool
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    AutoDetectWebSphereLibertyApplication bool
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    GroupIbmmqbyInstanceName bool
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    IdentifyJbossServerBySystemProperty bool
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    IgnoreUniqueIdentifiers bool
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    Scope string
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    ShortLivedProcessesMonitoring bool
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    SplitOracleDatabasePg bool
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    SplitOracleListenerPg bool
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    UseCatalinaBase bool
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    UseDockerContainerName bool
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    AddNodeJsScriptName bool
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    AutoDetectCassandraClusters bool
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    AutoDetectSpringBoot bool
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    AutoDetectTibcoContainerEditionEngines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    AutoDetectTibcoEngines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    AutoDetectWebMethodsIntegrationServer bool
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    AutoDetectWebSphereLibertyApplication bool
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    GroupIbmmqbyInstanceName bool
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    IdentifyJbossServerBySystemProperty bool
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    IgnoreUniqueIdentifiers bool
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    Scope string
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    ShortLivedProcessesMonitoring bool
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    SplitOracleDatabasePg bool
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    SplitOracleListenerPg bool
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    UseCatalinaBase bool
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    UseDockerContainerName bool
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    addNodeJsScriptName Boolean
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    autoDetectCassandraClusters Boolean
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    autoDetectSpringBoot Boolean
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    autoDetectTibcoContainerEditionEngines Boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectTibcoEngines Boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectWebMethodsIntegrationServer Boolean
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    autoDetectWebSphereLibertyApplication Boolean
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    groupIbmmqbyInstanceName Boolean
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    identifyJbossServerBySystemProperty Boolean
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    ignoreUniqueIdentifiers Boolean
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    scope String
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    shortLivedProcessesMonitoring Boolean
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    splitOracleDatabasePg Boolean
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    splitOracleListenerPg Boolean
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    useCatalinaBase Boolean
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    useDockerContainerName Boolean
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    addNodeJsScriptName boolean
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    autoDetectCassandraClusters boolean
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    autoDetectSpringBoot boolean
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    autoDetectTibcoContainerEditionEngines boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectTibcoEngines boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectWebMethodsIntegrationServer boolean
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    autoDetectWebSphereLibertyApplication boolean
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    groupIbmmqbyInstanceName boolean
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    identifyJbossServerBySystemProperty boolean
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    ignoreUniqueIdentifiers boolean
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    scope string
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    shortLivedProcessesMonitoring boolean
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    splitOracleDatabasePg boolean
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    splitOracleListenerPg boolean
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    useCatalinaBase boolean
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    useDockerContainerName boolean
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    add_node_js_script_name bool
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    auto_detect_cassandra_clusters bool
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    auto_detect_spring_boot bool
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    auto_detect_tibco_container_edition_engines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    auto_detect_tibco_engines bool
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    auto_detect_web_methods_integration_server bool
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    auto_detect_web_sphere_liberty_application bool
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    group_ibmmqby_instance_name bool
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    identify_jboss_server_by_system_property bool
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    ignore_unique_identifiers bool
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    scope str
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    short_lived_processes_monitoring bool
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    split_oracle_database_pg bool
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    split_oracle_listener_pg bool
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    use_catalina_base bool
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    use_docker_container_name bool
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!
    addNodeJsScriptName Boolean
    In older versions, Node.js applications were distinguished based on their directory name, omitting the script name. Changing this setting may change the general handling of Node.js process groups. Leave unchanged if in doubt.
    autoDetectCassandraClusters Boolean
    Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name.
    autoDetectSpringBoot Boolean
    Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files.
    autoDetectTibcoContainerEditionEngines Boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectTibcoEngines Boolean
    Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file.
    autoDetectWebMethodsIntegrationServer Boolean
    Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name.
    autoDetectWebSphereLibertyApplication Boolean
    Enabling this flag will detect separate WebSphere Liberty process groups based on java command line.
    groupIbmmqbyInstanceName Boolean
    Enable to group and separately analyze the processes of each IBM MQ Queue manager instance. Each process group receives a unique name based on the queue manager instance name.
    identifyJbossServerBySystemProperty Boolean
    Enabling this flag will detect the JBoss server name from the system property jboss.server.name=\n\n, only if -D[Server:\n\n] is not set.
    ignoreUniqueIdentifiers Boolean
    To determine the unique identity of each detected process, and to generate a unique name for each detected process, Dynatrace evaluates the name of the directory that each process binary is contained within. For application containers like Tomcat and JBoss, Dynatrace evaluates important directories like CATALINAHOME and JBOSSHOME for this information. In some automated deployment scenarios such directory names are updated automatically with new version numbers, build numbers, dates, or GUIDs. Enable this setting to ensure that automated directory name changes don't result in Dynatrace registering pre-existing processes as new processes.
    scope String
    The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment.
    shortLivedProcessesMonitoring Boolean
    Enable to monitor CPU and memory usage of short lived processes, otherwise being lost by traditional monitoring. Disabling this flag blocks passing data to cluster only, it does not stop data collection and has no effect on performance.
    splitOracleDatabasePg Boolean
    Enable to group and separately analyze the processes of each Oracle DB. Each process group receives a unique name based on the Oracle DB SID.
    splitOracleListenerPg Boolean
    Enable to group and separately analyze the processes of each Oracle Listener. Each process group receives a unique name based on the Oracle Listener name.
    useCatalinaBase Boolean
    By default, Tomcat clusters are identified and named based on the CATALINAHOME directory name. This setting results in the use of the CATALINABASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINAHOME+CATALINABASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host.
    useDockerContainerName Boolean
    By default, Dynatrace uses image names as identifiers for individual process groups, with one process-group instance per host. Normally Docker container names can't serve as stable identifiers of process group instances because they are variable and auto-generated. You can however manually assign proper container names to their Docker instances. Such manually-assigned container names can serve as reliable process-group instance identifiers. This flag instructs Dynatrace to use Docker-provided names to distinguish between multiple instances of the same image. If this flag is not applied and you run multiple containers of the same image on the same host, the resulting processes will be consolidated into a single process view. Use this flag with caution!

    Package Details

    Repository
    dynatrace pulumiverse/pulumi-dynatrace
    License
    Apache-2.0
    Notes
    This Pulumi package is based on the dynatrace Terraform Provider.
    dynatrace logo
    Dynatrace v0.21.0 published on Sunday, Nov 17, 2024 by Pulumiverse
    lbrlabs/pulumi-dynatrace