import * as pulumi from "@pulumi/pulumi"; export declare class ProcessGroupDetectionFlags extends pulumi.CustomResource { /** * Get an existing ProcessGroupDetectionFlags resource's state with the given name, ID, and optional extra * properties used to qualify the lookup. * * @param name The _unique_ name of the resulting resource. * @param id The _unique_ provider ID of the resource to lookup. * @param state Any extra arguments used during the lookup. * @param opts Optional settings to control the behavior of the CustomResource. */ static get(name: string, id: pulumi.Input, state?: ProcessGroupDetectionFlagsState, opts?: pulumi.CustomResourceOptions): ProcessGroupDetectionFlags; /** * Returns true if the given object is an instance of ProcessGroupDetectionFlags. This is designed to work even * when multiple copies of the Pulumi SDK have been loaded into the same process. */ static isInstance(obj: any): obj is ProcessGroupDetectionFlags; /** * 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. */ readonly addNodeJsScriptName: pulumi.Output; /** * Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name. */ readonly autoDetectCassandraClusters: pulumi.Output; /** * Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files. */ readonly autoDetectSpringBoot: pulumi.Output; /** * Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file. */ readonly autoDetectTibcoContainerEditionEngines: pulumi.Output; /** * Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file. */ readonly autoDetectTibcoEngines: pulumi.Output; /** * Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name. */ readonly autoDetectWebMethodsIntegrationServer: pulumi.Output; /** * Enabling this flag will detect separate WebSphere Liberty process groups based on java command line. */ readonly autoDetectWebSphereLibertyApplication: pulumi.Output; /** * 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. */ readonly groupIbmmqbyInstanceName: pulumi.Output; /** * 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. */ readonly identifyJbossServerBySystemProperty: pulumi.Output; /** * 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 CATALINA*HOME and JBOSS*HOME 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. */ readonly ignoreUniqueIdentifiers: pulumi.Output; /** * The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment. */ readonly scope: pulumi.Output; /** * This flag enables the detection of security software such as anti-malware protection. */ readonly securitySoftwareDetectionEnabled: pulumi.Output; /** * 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. */ readonly shortLivedProcessesMonitoring: pulumi.Output; /** * Enable to group and separately analyze the processes of each DB2 Instance. Each process receives a unique name based on the DB2 Instance name. */ readonly splitDb2GroupingByInstances: pulumi.Output; /** * 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. */ readonly splitOracleDatabasePg: pulumi.Output; /** * 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. */ readonly splitOracleListenerPg: pulumi.Output; /** * By default, Tomcat clusters are identified and named based on the CATALINA*HOME directory name. This setting results in the use of the CATALINA*BASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINA*HOME+CATALINA*BASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host. */ readonly useCatalinaBase: pulumi.Output; /** * 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! */ readonly useDockerContainerName: pulumi.Output; /** * Create a ProcessGroupDetectionFlags resource with the given unique name, arguments, and options. * * @param name The _unique_ name of the resource. * @param args The arguments to use to populate this resource's properties. * @param opts A bag of options that control this resource's behavior. */ constructor(name: string, args: ProcessGroupDetectionFlagsArgs, opts?: pulumi.CustomResourceOptions); } /** * Input properties used for looking up and filtering ProcessGroupDetectionFlags resources. */ export interface ProcessGroupDetectionFlagsState { /** * 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. */ addNodeJsScriptName?: pulumi.Input; /** * Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name. */ autoDetectCassandraClusters?: pulumi.Input; /** * Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files. */ autoDetectSpringBoot?: pulumi.Input; /** * Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file. */ autoDetectTibcoContainerEditionEngines?: pulumi.Input; /** * Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file. */ autoDetectTibcoEngines?: pulumi.Input; /** * Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name. */ autoDetectWebMethodsIntegrationServer?: pulumi.Input; /** * Enabling this flag will detect separate WebSphere Liberty process groups based on java command line. */ autoDetectWebSphereLibertyApplication?: pulumi.Input; /** * 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. */ groupIbmmqbyInstanceName?: pulumi.Input; /** * 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. */ identifyJbossServerBySystemProperty?: pulumi.Input; /** * 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 CATALINA*HOME and JBOSS*HOME 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. */ ignoreUniqueIdentifiers?: pulumi.Input; /** * The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment. */ scope?: pulumi.Input; /** * This flag enables the detection of security software such as anti-malware protection. */ securitySoftwareDetectionEnabled?: pulumi.Input; /** * 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. */ shortLivedProcessesMonitoring?: pulumi.Input; /** * Enable to group and separately analyze the processes of each DB2 Instance. Each process receives a unique name based on the DB2 Instance name. */ splitDb2GroupingByInstances?: pulumi.Input; /** * 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. */ splitOracleDatabasePg?: pulumi.Input; /** * 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. */ splitOracleListenerPg?: pulumi.Input; /** * By default, Tomcat clusters are identified and named based on the CATALINA*HOME directory name. This setting results in the use of the CATALINA*BASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINA*HOME+CATALINA*BASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host. */ useCatalinaBase?: pulumi.Input; /** * 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! */ useDockerContainerName?: pulumi.Input; } /** * The set of arguments for constructing a ProcessGroupDetectionFlags resource. */ export interface ProcessGroupDetectionFlagsArgs { /** * 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. */ addNodeJsScriptName: pulumi.Input; /** * Enabling this flag will detect separate Cassandra process groups based on the configured Cassandra cluster name. */ autoDetectCassandraClusters: pulumi.Input; /** * Enabling this flag will detect Spring Boot process groups based on command line and applications' configuration files. */ autoDetectSpringBoot: pulumi.Input; /** * Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file. */ autoDetectTibcoContainerEditionEngines: pulumi.Input; /** * Enabling this flag will detect separate TIBCO BusinessWorks process groups per engine property file. */ autoDetectTibcoEngines: pulumi.Input; /** * Enabling this flag will detect webMethods Integration Server including specific properties like install root and product name. */ autoDetectWebMethodsIntegrationServer: pulumi.Input; /** * Enabling this flag will detect separate WebSphere Liberty process groups based on java command line. */ autoDetectWebSphereLibertyApplication: pulumi.Input; /** * 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. */ groupIbmmqbyInstanceName: pulumi.Input; /** * 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. */ identifyJbossServerBySystemProperty: pulumi.Input; /** * 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 CATALINA*HOME and JBOSS*HOME 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. */ ignoreUniqueIdentifiers: pulumi.Input; /** * The scope of this setting (HOST, HOST_GROUP). Omit this property if you want to cover the whole environment. */ scope?: pulumi.Input; /** * This flag enables the detection of security software such as anti-malware protection. */ securitySoftwareDetectionEnabled?: pulumi.Input; /** * 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. */ shortLivedProcessesMonitoring: pulumi.Input; /** * Enable to group and separately analyze the processes of each DB2 Instance. Each process receives a unique name based on the DB2 Instance name. */ splitDb2GroupingByInstances?: pulumi.Input; /** * 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. */ splitOracleDatabasePg: pulumi.Input; /** * 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. */ splitOracleListenerPg: pulumi.Input; /** * By default, Tomcat clusters are identified and named based on the CATALINA*HOME directory name. This setting results in the use of the CATALINA*BASE directory name to identify multiple Tomcat nodes within each Tomcat cluster. If this setting is not enabled, each CATALINA*HOME+CATALINA*BASE combination will be considered a separate Tomcat cluster. In other words, Tomcat clusters can't have multiple nodes on a single host. */ useCatalinaBase: pulumi.Input; /** * 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! */ useDockerContainerName: pulumi.Input; }