published on Tuesday, Jun 23, 2026 by Pulumiverse
published on Tuesday, Jun 23, 2026 by Pulumiverse
This resource requires the API token scopes Read settings (
settings.read) and Write settings (settings.write)
Dynatrace Documentation
Process grouping rules - https://docs.dynatrace.com/docs/observe/infrastructure-observability/process-groups/configuration/unified-process-grouping/process-grouping-rules-configure
Settings API - https://www.dynatrace.com/support/help/dynatrace-api/environment-api/settings (schemaId:
builtin:process-grouping-rules)
Export Example Usage
terraform-provider-dynatrace -export dynatrace.ProcessGroupingRulesdownloads all existing process grouping rules
The full documentation of the export feature is available here.
Resource Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as dynatrace from "@pulumiverse/dynatrace";
const rules = new dynatrace.ProcessGroupingRules("rules", {
enabled: true,
customTechnologyName: "custom_technology_name",
scope: "environment",
pgExtraction: {
processGroupExtractions: [{
report: "auto",
name: "My process group",
processType: "PROCESS_TYPE_GO",
detection: {
detectionConditions: [{
condition: "$contains(TFExecutableSample)",
caseSensitive: true,
property: "EXE_NAME",
}],
},
pgIdSource: {
property: "COMMAND_LINE_ARGS",
standaloneRule: false,
type: "EXISTING",
advancedSettings: {
ignoreNumbers: false,
},
},
pgiIdSource: {
property: "AWS_ECS_FAMILY",
advancedSettings: {
ignoreNumbers: false,
},
},
}],
},
});
import pulumi
import pulumiverse_dynatrace as dynatrace
rules = dynatrace.ProcessGroupingRules("rules",
enabled=True,
custom_technology_name="custom_technology_name",
scope="environment",
pg_extraction={
"process_group_extractions": [{
"report": "auto",
"name": "My process group",
"process_type": "PROCESS_TYPE_GO",
"detection": {
"detection_conditions": [{
"condition": "$contains(TFExecutableSample)",
"case_sensitive": True,
"property": "EXE_NAME",
}],
},
"pg_id_source": {
"property": "COMMAND_LINE_ARGS",
"standalone_rule": False,
"type": "EXISTING",
"advanced_settings": {
"ignore_numbers": False,
},
},
"pgi_id_source": {
"property": "AWS_ECS_FAMILY",
"advanced_settings": {
"ignore_numbers": False,
},
},
}],
})
package main
import (
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
"github.com/pulumiverse/pulumi-dynatrace/sdk/go/dynatrace"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := dynatrace.NewProcessGroupingRules(ctx, "rules", &dynatrace.ProcessGroupingRulesArgs{
Enabled: pulumi.Bool(true),
CustomTechnologyName: pulumi.String("custom_technology_name"),
Scope: pulumi.String("environment"),
PgExtraction: &dynatrace.ProcessGroupingRulesPgExtractionArgs{
ProcessGroupExtractions: dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionArray{
&dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionArgs{
Report: pulumi.String("auto"),
Name: pulumi.String("My process group"),
ProcessType: pulumi.String("PROCESS_TYPE_GO"),
Detection: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionArgs{
DetectionConditions: dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArray{
&dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArgs{
Condition: pulumi.String("$contains(TFExecutableSample)"),
CaseSensitive: pulumi.Bool(true),
Property: pulumi.String("EXE_NAME"),
},
},
},
PgIdSource: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceArgs{
Property: pulumi.String("COMMAND_LINE_ARGS"),
StandaloneRule: pulumi.Bool(false),
Type: pulumi.String("EXISTING"),
AdvancedSettings: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceAdvancedSettingsArgs{
IgnoreNumbers: pulumi.Bool(false),
},
},
PgiIdSource: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceArgs{
Property: pulumi.String("AWS_ECS_FAMILY"),
AdvancedSettings: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceAdvancedSettingsArgs{
IgnoreNumbers: pulumi.Bool(false),
},
},
},
},
},
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Dynatrace = Pulumiverse.Dynatrace;
return await Deployment.RunAsync(() =>
{
var rules = new Dynatrace.ProcessGroupingRules("rules", new()
{
Enabled = true,
CustomTechnologyName = "custom_technology_name",
Scope = "environment",
PgExtraction = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionArgs
{
ProcessGroupExtractions = new[]
{
new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionArgs
{
Report = "auto",
Name = "My process group",
ProcessType = "PROCESS_TYPE_GO",
Detection = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionArgs
{
DetectionConditions = new[]
{
new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArgs
{
Condition = "$contains(TFExecutableSample)",
CaseSensitive = true,
Property = "EXE_NAME",
},
},
},
PgIdSource = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceArgs
{
Property = "COMMAND_LINE_ARGS",
StandaloneRule = false,
Type = "EXISTING",
AdvancedSettings = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceAdvancedSettingsArgs
{
IgnoreNumbers = false,
},
},
PgiIdSource = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceArgs
{
Property = "AWS_ECS_FAMILY",
AdvancedSettings = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceAdvancedSettingsArgs
{
IgnoreNumbers = false,
},
},
},
},
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.dynatrace.ProcessGroupingRules;
import com.pulumi.dynatrace.ProcessGroupingRulesArgs;
import com.pulumi.dynatrace.inputs.ProcessGroupingRulesPgExtractionArgs;
import com.pulumi.dynatrace.inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionArgs;
import com.pulumi.dynatrace.inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionArgs;
import com.pulumi.dynatrace.inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArgs;
import com.pulumi.dynatrace.inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceArgs;
import com.pulumi.dynatrace.inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceAdvancedSettingsArgs;
import com.pulumi.dynatrace.inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceArgs;
import com.pulumi.dynatrace.inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceAdvancedSettingsArgs;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var rules = new ProcessGroupingRules("rules", ProcessGroupingRulesArgs.builder()
.enabled(true)
.customTechnologyName("custom_technology_name")
.scope("environment")
.pgExtraction(ProcessGroupingRulesPgExtractionArgs.builder()
.processGroupExtractions(ProcessGroupingRulesPgExtractionProcessGroupExtractionArgs.builder()
.report("auto")
.name("My process group")
.processType("PROCESS_TYPE_GO")
.detection(ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionArgs.builder()
.detectionConditions(ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArgs.builder()
.condition("$contains(TFExecutableSample)")
.caseSensitive(true)
.property("EXE_NAME")
.build())
.build())
.pgIdSource(ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceArgs.builder()
.property("COMMAND_LINE_ARGS")
.standaloneRule(false)
.type("EXISTING")
.advancedSettings(ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceAdvancedSettingsArgs.builder()
.ignoreNumbers(false)
.build())
.build())
.pgiIdSource(ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceArgs.builder()
.property("AWS_ECS_FAMILY")
.advancedSettings(ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceAdvancedSettingsArgs.builder()
.ignoreNumbers(false)
.build())
.build())
.build())
.build())
.build());
}
}
resources:
rules:
type: dynatrace:ProcessGroupingRules
properties:
enabled: true
customTechnologyName: custom_technology_name
scope: environment
pgExtraction:
processGroupExtractions:
- report: auto
name: My process group
processType: PROCESS_TYPE_GO
detection:
detectionConditions:
- condition: $contains(TFExecutableSample)
caseSensitive: true
property: EXE_NAME
pgIdSource:
property: COMMAND_LINE_ARGS
standaloneRule: false
type: EXISTING
advancedSettings:
ignoreNumbers: false
pgiIdSource:
property: AWS_ECS_FAMILY
advancedSettings:
ignoreNumbers: false
pulumi {
required_providers {
dynatrace = {
source = "pulumi/dynatrace"
}
}
}
resource "dynatrace_processgroupingrules" "rules" {
enabled = true
custom_technology_name = "custom_technology_name"
scope = "environment"
pg_extraction = {
process_group_extractions = [{
"report" = "auto"
"name" = "My process group"
"processType" = "PROCESS_TYPE_GO"
"detection" = {
"detectionConditions" = [{
"condition" = "$contains(TFExecutableSample)"
"caseSensitive" = true
"property" = "EXE_NAME"
}]
}
"pgIdSource" = {
"property" = "COMMAND_LINE_ARGS"
"standaloneRule" = false
"type" = "EXISTING"
"advancedSettings" = {
"ignoreNumbers" = false
}
}
"pgiIdSource" = {
"property" = "AWS_ECS_FAMILY"
"advancedSettings" = {
"ignoreNumbers" = false
}
}
}]
}
}
Create ProcessGroupingRules Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new ProcessGroupingRules(name: string, args: ProcessGroupingRulesArgs, opts?: CustomResourceOptions);@overload
def ProcessGroupingRules(resource_name: str,
args: ProcessGroupingRulesArgs,
opts: Optional[ResourceOptions] = None)
@overload
def ProcessGroupingRules(resource_name: str,
opts: Optional[ResourceOptions] = None,
enabled: Optional[bool] = None,
pg_extraction: Optional[ProcessGroupingRulesPgExtractionArgs] = None,
custom_technology_name: Optional[str] = None,
insert_after: Optional[str] = None,
scope: Optional[str] = None)func NewProcessGroupingRules(ctx *Context, name string, args ProcessGroupingRulesArgs, opts ...ResourceOption) (*ProcessGroupingRules, error)public ProcessGroupingRules(string name, ProcessGroupingRulesArgs args, CustomResourceOptions? opts = null)
public ProcessGroupingRules(String name, ProcessGroupingRulesArgs args)
public ProcessGroupingRules(String name, ProcessGroupingRulesArgs args, CustomResourceOptions options)
type: dynatrace:ProcessGroupingRules
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
resource "dynatrace_processgroupingrules" "name" {
# resource properties
}Parameters
- name string
- The unique name of the resource.
- args ProcessGroupingRulesArgs
- 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 ProcessGroupingRulesArgs
- 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 ProcessGroupingRulesArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args ProcessGroupingRulesArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args ProcessGroupingRulesArgs
- 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 processGroupingRulesResource = new Dynatrace.ProcessGroupingRules("processGroupingRulesResource", new()
{
Enabled = false,
PgExtraction = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionArgs
{
ProcessGroupExtractions = new[]
{
new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionArgs
{
Detection = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionArgs
{
DetectionConditions = new[]
{
new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArgs
{
CaseSensitive = false,
Property = "string",
Condition = "string",
Name = "string",
},
},
},
PgIdSource = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceArgs
{
StandaloneRule = false,
Type = "string",
AdvancedSettings = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceAdvancedSettingsArgs
{
IgnoreNumbers = false,
From = "string",
To = "string",
},
Id = "string",
Name = "string",
Property = "string",
},
Report = "string",
Name = "string",
PgiIdSource = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceArgs
{
AdvancedSettings = new Dynatrace.Inputs.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceAdvancedSettingsArgs
{
IgnoreNumbers = false,
From = "string",
To = "string",
},
Name = "string",
Property = "string",
},
ProcessType = "string",
},
},
},
CustomTechnologyName = "string",
InsertAfter = "string",
Scope = "string",
});
example, err := dynatrace.NewProcessGroupingRules(ctx, "processGroupingRulesResource", &dynatrace.ProcessGroupingRulesArgs{
Enabled: pulumi.Bool(false),
PgExtraction: &dynatrace.ProcessGroupingRulesPgExtractionArgs{
ProcessGroupExtractions: dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionArray{
&dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionArgs{
Detection: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionArgs{
DetectionConditions: dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArray{
&dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArgs{
CaseSensitive: pulumi.Bool(false),
Property: pulumi.String("string"),
Condition: pulumi.String("string"),
Name: pulumi.String("string"),
},
},
},
PgIdSource: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceArgs{
StandaloneRule: pulumi.Bool(false),
Type: pulumi.String("string"),
AdvancedSettings: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceAdvancedSettingsArgs{
IgnoreNumbers: pulumi.Bool(false),
From: pulumi.String("string"),
To: pulumi.String("string"),
},
Id: pulumi.String("string"),
Name: pulumi.String("string"),
Property: pulumi.String("string"),
},
Report: pulumi.String("string"),
Name: pulumi.String("string"),
PgiIdSource: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceArgs{
AdvancedSettings: &dynatrace.ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceAdvancedSettingsArgs{
IgnoreNumbers: pulumi.Bool(false),
From: pulumi.String("string"),
To: pulumi.String("string"),
},
Name: pulumi.String("string"),
Property: pulumi.String("string"),
},
ProcessType: pulumi.String("string"),
},
},
},
CustomTechnologyName: pulumi.String("string"),
InsertAfter: pulumi.String("string"),
Scope: pulumi.String("string"),
})
resource "dynatrace_processgroupingrules" "processGroupingRulesResource" {
enabled = false
pg_extraction = {
process_group_extractions = [{
"detection" = {
"detectionConditions" = [{
"caseSensitive" = false
"property" = "string"
"condition" = "string"
"name" = "string"
}]
}
"pgIdSource" = {
"standaloneRule" = false
"type" = "string"
"advancedSettings" = {
"ignoreNumbers" = false
"from" = "string"
"to" = "string"
}
"id" = "string"
"name" = "string"
"property" = "string"
}
"report" = "string"
"name" = "string"
"pgiIdSource" = {
"advancedSettings" = {
"ignoreNumbers" = false
"from" = "string"
"to" = "string"
}
"name" = "string"
"property" = "string"
}
"processType" = "string"
}]
}
custom_technology_name = "string"
insert_after = "string"
scope = "string"
}
var processGroupingRulesResource = new ProcessGroupingRules("processGroupingRulesResource", ProcessGroupingRulesArgs.builder()
.enabled(false)
.pgExtraction(ProcessGroupingRulesPgExtractionArgs.builder()
.processGroupExtractions(ProcessGroupingRulesPgExtractionProcessGroupExtractionArgs.builder()
.detection(ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionArgs.builder()
.detectionConditions(ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArgs.builder()
.caseSensitive(false)
.property("string")
.condition("string")
.name("string")
.build())
.build())
.pgIdSource(ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceArgs.builder()
.standaloneRule(false)
.type("string")
.advancedSettings(ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceAdvancedSettingsArgs.builder()
.ignoreNumbers(false)
.from("string")
.to("string")
.build())
.id("string")
.name("string")
.property("string")
.build())
.report("string")
.name("string")
.pgiIdSource(ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceArgs.builder()
.advancedSettings(ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceAdvancedSettingsArgs.builder()
.ignoreNumbers(false)
.from("string")
.to("string")
.build())
.name("string")
.property("string")
.build())
.processType("string")
.build())
.build())
.customTechnologyName("string")
.insertAfter("string")
.scope("string")
.build());
process_grouping_rules_resource = dynatrace.ProcessGroupingRules("processGroupingRulesResource",
enabled=False,
pg_extraction={
"process_group_extractions": [{
"detection": {
"detection_conditions": [{
"case_sensitive": False,
"property": "string",
"condition": "string",
"name": "string",
}],
},
"pg_id_source": {
"standalone_rule": False,
"type": "string",
"advanced_settings": {
"ignore_numbers": False,
"from_": "string",
"to": "string",
},
"id": "string",
"name": "string",
"property": "string",
},
"report": "string",
"name": "string",
"pgi_id_source": {
"advanced_settings": {
"ignore_numbers": False,
"from_": "string",
"to": "string",
},
"name": "string",
"property": "string",
},
"process_type": "string",
}],
},
custom_technology_name="string",
insert_after="string",
scope="string")
const processGroupingRulesResource = new dynatrace.ProcessGroupingRules("processGroupingRulesResource", {
enabled: false,
pgExtraction: {
processGroupExtractions: [{
detection: {
detectionConditions: [{
caseSensitive: false,
property: "string",
condition: "string",
name: "string",
}],
},
pgIdSource: {
standaloneRule: false,
type: "string",
advancedSettings: {
ignoreNumbers: false,
from: "string",
to: "string",
},
id: "string",
name: "string",
property: "string",
},
report: "string",
name: "string",
pgiIdSource: {
advancedSettings: {
ignoreNumbers: false,
from: "string",
to: "string",
},
name: "string",
property: "string",
},
processType: "string",
}],
},
customTechnologyName: "string",
insertAfter: "string",
scope: "string",
});
type: dynatrace:ProcessGroupingRules
properties:
customTechnologyName: string
enabled: false
insertAfter: string
pgExtraction:
processGroupExtractions:
- detection:
detectionConditions:
- caseSensitive: false
condition: string
name: string
property: string
name: string
pgIdSource:
advancedSettings:
from: string
ignoreNumbers: false
to: string
id: string
name: string
property: string
standaloneRule: false
type: string
pgiIdSource:
advancedSettings:
from: string
ignoreNumbers: false
to: string
name: string
property: string
processType: string
report: string
scope: string
ProcessGroupingRules 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 ProcessGroupingRules resource accepts the following input properties:
- Enabled bool
- This setting is enabled (
true) or disabled (false) - Pg
Extraction Pulumiverse.Dynatrace. Inputs. Process Grouping Rules Pg Extraction - Define process groups and processes.
- Custom
Technology stringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- Insert
After string - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- Scope string
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- Enabled bool
- This setting is enabled (
true) or disabled (false) - Pg
Extraction ProcessGrouping Rules Pg Extraction Args - Define process groups and processes.
- Custom
Technology stringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- Insert
After string - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- Scope string
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- enabled bool
- This setting is enabled (
true) or disabled (false) - pg_
extraction object - Define process groups and processes.
- custom_
technology_ stringname - Note: Reported only in full-stack, infrastructure and discovery modes.
- insert_
after string - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- scope string
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- enabled Boolean
- This setting is enabled (
true) or disabled (false) - pg
Extraction ProcessGrouping Rules Pg Extraction - Define process groups and processes.
- custom
Technology StringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- insert
After String - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- scope String
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- enabled boolean
- This setting is enabled (
true) or disabled (false) - pg
Extraction ProcessGrouping Rules Pg Extraction - Define process groups and processes.
- custom
Technology stringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- insert
After string - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- scope string
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- enabled bool
- This setting is enabled (
true) or disabled (false) - pg_
extraction ProcessGrouping Rules Pg Extraction Args - Define process groups and processes.
- custom_
technology_ strname - Note: Reported only in full-stack, infrastructure and discovery modes.
- insert_
after str - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- scope str
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- enabled Boolean
- This setting is enabled (
true) or disabled (false) - pg
Extraction Property Map - Define process groups and processes.
- custom
Technology StringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- insert
After String - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- scope String
- The scope of this setting (HOST, KUBERNETES_CLUSTER, 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 ProcessGroupingRules 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 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 ProcessGroupingRules Resource
Get an existing ProcessGroupingRules 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?: ProcessGroupingRulesState, opts?: CustomResourceOptions): ProcessGroupingRules@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
custom_technology_name: Optional[str] = None,
enabled: Optional[bool] = None,
insert_after: Optional[str] = None,
pg_extraction: Optional[ProcessGroupingRulesPgExtractionArgs] = None,
scope: Optional[str] = None) -> ProcessGroupingRulesfunc GetProcessGroupingRules(ctx *Context, name string, id IDInput, state *ProcessGroupingRulesState, opts ...ResourceOption) (*ProcessGroupingRules, error)public static ProcessGroupingRules Get(string name, Input<string> id, ProcessGroupingRulesState? state, CustomResourceOptions? opts = null)public static ProcessGroupingRules get(String name, Output<String> id, ProcessGroupingRulesState state, CustomResourceOptions options)resources: _: type: dynatrace:ProcessGroupingRules get: id: ${id}import {
to = dynatrace_processgroupingrules.example
id = "${id}"
}
- 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.
- Custom
Technology stringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- Enabled bool
- This setting is enabled (
true) or disabled (false) - Insert
After string - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- Pg
Extraction Pulumiverse.Dynatrace. Inputs. Process Grouping Rules Pg Extraction - Define process groups and processes.
- Scope string
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- Custom
Technology stringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- Enabled bool
- This setting is enabled (
true) or disabled (false) - Insert
After string - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- Pg
Extraction ProcessGrouping Rules Pg Extraction Args - Define process groups and processes.
- Scope string
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- custom_
technology_ stringname - Note: Reported only in full-stack, infrastructure and discovery modes.
- enabled bool
- This setting is enabled (
true) or disabled (false) - insert_
after string - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- pg_
extraction object - Define process groups and processes.
- scope string
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- custom
Technology StringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- enabled Boolean
- This setting is enabled (
true) or disabled (false) - insert
After String - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- pg
Extraction ProcessGrouping Rules Pg Extraction - Define process groups and processes.
- scope String
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- custom
Technology stringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- enabled boolean
- This setting is enabled (
true) or disabled (false) - insert
After string - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- pg
Extraction ProcessGrouping Rules Pg Extraction - Define process groups and processes.
- scope string
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- custom_
technology_ strname - Note: Reported only in full-stack, infrastructure and discovery modes.
- enabled bool
- This setting is enabled (
true) or disabled (false) - insert_
after str - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- pg_
extraction ProcessGrouping Rules Pg Extraction Args - Define process groups and processes.
- scope str
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
- custom
Technology StringName - Note: Reported only in full-stack, infrastructure and discovery modes.
- enabled Boolean
- This setting is enabled (
true) or disabled (false) - insert
After String - Because this resource allows for ordering you may specify the ID of the resource instance that comes before this instance regarding order. If not specified when creating the setting will be added to the end of the list. If not specified during update the order will remain untouched
- pg
Extraction Property Map - Define process groups and processes.
- scope String
- The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
Supporting Types
ProcessGroupingRulesPgExtraction, ProcessGroupingRulesPgExtractionArgs
ProcessGroupingRulesPgExtractionProcessGroupExtraction, ProcessGroupingRulesPgExtractionProcessGroupExtractionArgs
- Detection
Pulumiverse.
Dynatrace. Inputs. Process Grouping Rules Pg Extraction Process Group Extraction Detection 2. Define detection rules
Define process detection rules to select processes on which this rule will apply to. At least one rule must be defined.
- Pg
Id Pulumiverse.Source Dynatrace. Inputs. Process Grouping Rules Pg Extraction Process Group Extraction Pg Id Source 3. Define grouping rules
3.1. Process group id source
- Report string
- Auto reports only processes which are important - meaning deep monitored or with high resource usage. Possible values:
always,auto,never - Name string
- When this field is empty, OneAgent will automatically assign the process group name based on process type and properties like executable name. If you expect that multiple processes will be matched by the rule, it is highly recommended that you fill this field because it is unspecified which process will be used as the group name source.
- Pgi
Id Pulumiverse.Source Dynatrace. Inputs. Process Grouping Rules Pg Extraction Process Group Extraction Pgi Id Source 3.2. Process id source (optional)
Define a property that should be used to identify your process.
- Process
Type string - Note: Not all types can be detected at startup.. Restrict this rule to specific process types to avoid mixing deep monitored properties leading to confusing results. Possible values:
PROCESS_TYPE_APACHE_HTTPD,PROCESS_TYPE_GLASSFISH,PROCESS_TYPE_GO,PROCESS_TYPE_IBM_CICS_REGION,PROCESS_TYPE_IBM_IMS_CONTROL,PROCESS_TYPE_IBM_IMS_MPR,PROCESS_TYPE_IIS_APP_POOL,PROCESS_TYPE_JAVA,PROCESS_TYPE_JBOSS,PROCESS_TYPE_NGINX,PROCESS_TYPE_NODE_JS,PROCESS_TYPE_PHP,PROCESS_TYPE_RUBY,PROCESS_TYPE_TOMCAT,PROCESS_TYPE_WEBLOGIC,PROCESS_TYPE_WEBSPHERE
- Detection
Process
Grouping Rules Pg Extraction Process Group Extraction Detection 2. Define detection rules
Define process detection rules to select processes on which this rule will apply to. At least one rule must be defined.
- Pg
Id ProcessSource Grouping Rules Pg Extraction Process Group Extraction Pg Id Source 3. Define grouping rules
3.1. Process group id source
- Report string
- Auto reports only processes which are important - meaning deep monitored or with high resource usage. Possible values:
always,auto,never - Name string
- When this field is empty, OneAgent will automatically assign the process group name based on process type and properties like executable name. If you expect that multiple processes will be matched by the rule, it is highly recommended that you fill this field because it is unspecified which process will be used as the group name source.
- Pgi
Id ProcessSource Grouping Rules Pg Extraction Process Group Extraction Pgi Id Source 3.2. Process id source (optional)
Define a property that should be used to identify your process.
- Process
Type string - Note: Not all types can be detected at startup.. Restrict this rule to specific process types to avoid mixing deep monitored properties leading to confusing results. Possible values:
PROCESS_TYPE_APACHE_HTTPD,PROCESS_TYPE_GLASSFISH,PROCESS_TYPE_GO,PROCESS_TYPE_IBM_CICS_REGION,PROCESS_TYPE_IBM_IMS_CONTROL,PROCESS_TYPE_IBM_IMS_MPR,PROCESS_TYPE_IIS_APP_POOL,PROCESS_TYPE_JAVA,PROCESS_TYPE_JBOSS,PROCESS_TYPE_NGINX,PROCESS_TYPE_NODE_JS,PROCESS_TYPE_PHP,PROCESS_TYPE_RUBY,PROCESS_TYPE_TOMCAT,PROCESS_TYPE_WEBLOGIC,PROCESS_TYPE_WEBSPHERE
- detection object
2. Define detection rules
Define process detection rules to select processes on which this rule will apply to. At least one rule must be defined.
- pg_
id_ objectsource 3. Define grouping rules
3.1. Process group id source
- report string
- Auto reports only processes which are important - meaning deep monitored or with high resource usage. Possible values:
always,auto,never - name string
- When this field is empty, OneAgent will automatically assign the process group name based on process type and properties like executable name. If you expect that multiple processes will be matched by the rule, it is highly recommended that you fill this field because it is unspecified which process will be used as the group name source.
- pgi_
id_ objectsource 3.2. Process id source (optional)
Define a property that should be used to identify your process.
- process_
type string - Note: Not all types can be detected at startup.. Restrict this rule to specific process types to avoid mixing deep monitored properties leading to confusing results. Possible values:
PROCESS_TYPE_APACHE_HTTPD,PROCESS_TYPE_GLASSFISH,PROCESS_TYPE_GO,PROCESS_TYPE_IBM_CICS_REGION,PROCESS_TYPE_IBM_IMS_CONTROL,PROCESS_TYPE_IBM_IMS_MPR,PROCESS_TYPE_IIS_APP_POOL,PROCESS_TYPE_JAVA,PROCESS_TYPE_JBOSS,PROCESS_TYPE_NGINX,PROCESS_TYPE_NODE_JS,PROCESS_TYPE_PHP,PROCESS_TYPE_RUBY,PROCESS_TYPE_TOMCAT,PROCESS_TYPE_WEBLOGIC,PROCESS_TYPE_WEBSPHERE
- detection
Process
Grouping Rules Pg Extraction Process Group Extraction Detection 2. Define detection rules
Define process detection rules to select processes on which this rule will apply to. At least one rule must be defined.
- pg
Id ProcessSource Grouping Rules Pg Extraction Process Group Extraction Pg Id Source 3. Define grouping rules
3.1. Process group id source
- report String
- Auto reports only processes which are important - meaning deep monitored or with high resource usage. Possible values:
always,auto,never - name String
- When this field is empty, OneAgent will automatically assign the process group name based on process type and properties like executable name. If you expect that multiple processes will be matched by the rule, it is highly recommended that you fill this field because it is unspecified which process will be used as the group name source.
- pgi
Id ProcessSource Grouping Rules Pg Extraction Process Group Extraction Pgi Id Source 3.2. Process id source (optional)
Define a property that should be used to identify your process.
- process
Type String - Note: Not all types can be detected at startup.. Restrict this rule to specific process types to avoid mixing deep monitored properties leading to confusing results. Possible values:
PROCESS_TYPE_APACHE_HTTPD,PROCESS_TYPE_GLASSFISH,PROCESS_TYPE_GO,PROCESS_TYPE_IBM_CICS_REGION,PROCESS_TYPE_IBM_IMS_CONTROL,PROCESS_TYPE_IBM_IMS_MPR,PROCESS_TYPE_IIS_APP_POOL,PROCESS_TYPE_JAVA,PROCESS_TYPE_JBOSS,PROCESS_TYPE_NGINX,PROCESS_TYPE_NODE_JS,PROCESS_TYPE_PHP,PROCESS_TYPE_RUBY,PROCESS_TYPE_TOMCAT,PROCESS_TYPE_WEBLOGIC,PROCESS_TYPE_WEBSPHERE
- detection
Process
Grouping Rules Pg Extraction Process Group Extraction Detection 2. Define detection rules
Define process detection rules to select processes on which this rule will apply to. At least one rule must be defined.
- pg
Id ProcessSource Grouping Rules Pg Extraction Process Group Extraction Pg Id Source 3. Define grouping rules
3.1. Process group id source
- report string
- Auto reports only processes which are important - meaning deep monitored or with high resource usage. Possible values:
always,auto,never - name string
- When this field is empty, OneAgent will automatically assign the process group name based on process type and properties like executable name. If you expect that multiple processes will be matched by the rule, it is highly recommended that you fill this field because it is unspecified which process will be used as the group name source.
- pgi
Id ProcessSource Grouping Rules Pg Extraction Process Group Extraction Pgi Id Source 3.2. Process id source (optional)
Define a property that should be used to identify your process.
- process
Type string - Note: Not all types can be detected at startup.. Restrict this rule to specific process types to avoid mixing deep monitored properties leading to confusing results. Possible values:
PROCESS_TYPE_APACHE_HTTPD,PROCESS_TYPE_GLASSFISH,PROCESS_TYPE_GO,PROCESS_TYPE_IBM_CICS_REGION,PROCESS_TYPE_IBM_IMS_CONTROL,PROCESS_TYPE_IBM_IMS_MPR,PROCESS_TYPE_IIS_APP_POOL,PROCESS_TYPE_JAVA,PROCESS_TYPE_JBOSS,PROCESS_TYPE_NGINX,PROCESS_TYPE_NODE_JS,PROCESS_TYPE_PHP,PROCESS_TYPE_RUBY,PROCESS_TYPE_TOMCAT,PROCESS_TYPE_WEBLOGIC,PROCESS_TYPE_WEBSPHERE
- detection
Process
Grouping Rules Pg Extraction Process Group Extraction Detection 2. Define detection rules
Define process detection rules to select processes on which this rule will apply to. At least one rule must be defined.
- pg_
id_ Processsource Grouping Rules Pg Extraction Process Group Extraction Pg Id Source 3. Define grouping rules
3.1. Process group id source
- report str
- Auto reports only processes which are important - meaning deep monitored or with high resource usage. Possible values:
always,auto,never - name str
- When this field is empty, OneAgent will automatically assign the process group name based on process type and properties like executable name. If you expect that multiple processes will be matched by the rule, it is highly recommended that you fill this field because it is unspecified which process will be used as the group name source.
- pgi_
id_ Processsource Grouping Rules Pg Extraction Process Group Extraction Pgi Id Source 3.2. Process id source (optional)
Define a property that should be used to identify your process.
- process_
type str - Note: Not all types can be detected at startup.. Restrict this rule to specific process types to avoid mixing deep monitored properties leading to confusing results. Possible values:
PROCESS_TYPE_APACHE_HTTPD,PROCESS_TYPE_GLASSFISH,PROCESS_TYPE_GO,PROCESS_TYPE_IBM_CICS_REGION,PROCESS_TYPE_IBM_IMS_CONTROL,PROCESS_TYPE_IBM_IMS_MPR,PROCESS_TYPE_IIS_APP_POOL,PROCESS_TYPE_JAVA,PROCESS_TYPE_JBOSS,PROCESS_TYPE_NGINX,PROCESS_TYPE_NODE_JS,PROCESS_TYPE_PHP,PROCESS_TYPE_RUBY,PROCESS_TYPE_TOMCAT,PROCESS_TYPE_WEBLOGIC,PROCESS_TYPE_WEBSPHERE
- detection Property Map
2. Define detection rules
Define process detection rules to select processes on which this rule will apply to. At least one rule must be defined.
- pg
Id Property MapSource 3. Define grouping rules
3.1. Process group id source
- report String
- Auto reports only processes which are important - meaning deep monitored or with high resource usage. Possible values:
always,auto,never - name String
- When this field is empty, OneAgent will automatically assign the process group name based on process type and properties like executable name. If you expect that multiple processes will be matched by the rule, it is highly recommended that you fill this field because it is unspecified which process will be used as the group name source.
- pgi
Id Property MapSource 3.2. Process id source (optional)
Define a property that should be used to identify your process.
- process
Type String - Note: Not all types can be detected at startup.. Restrict this rule to specific process types to avoid mixing deep monitored properties leading to confusing results. Possible values:
PROCESS_TYPE_APACHE_HTTPD,PROCESS_TYPE_GLASSFISH,PROCESS_TYPE_GO,PROCESS_TYPE_IBM_CICS_REGION,PROCESS_TYPE_IBM_IMS_CONTROL,PROCESS_TYPE_IBM_IMS_MPR,PROCESS_TYPE_IIS_APP_POOL,PROCESS_TYPE_JAVA,PROCESS_TYPE_JBOSS,PROCESS_TYPE_NGINX,PROCESS_TYPE_NODE_JS,PROCESS_TYPE_PHP,PROCESS_TYPE_RUBY,PROCESS_TYPE_TOMCAT,PROCESS_TYPE_WEBLOGIC,PROCESS_TYPE_WEBSPHERE
ProcessGroupingRulesPgExtractionProcessGroupExtractionDetection, ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionArgs
ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionCondition, ProcessGroupingRulesPgExtractionProcessGroupExtractionDetectionDetectionConditionArgs
- Case
Sensitive bool - When enabled, matching conditions are case sensitive. When disabled, matching conditions are case insensitive
- Property string
- 2.1. Property
- Condition string
- $contains(svc) – Matches if svc appears anywhere in the process property value.
- $eq(svc.exe) – Matches if svc.exe matches the process property value exactly.
- $prefix(svc) – Matches if app matches the prefix of the process property value.
- $suffix(svc.py) – Matches if svc.py matches the suffix of the process property value.
For example, $suffix(svc.py) would detect processes named loyaltysvc.py and paymentssvc.py.
For more details, see documentation.
- Name string
- If Dynatrace detects this property at startup of a process, it will be matched to this grouping rule.
- Case
Sensitive bool - When enabled, matching conditions are case sensitive. When disabled, matching conditions are case insensitive
- Property string
- 2.1. Property
- Condition string
- $contains(svc) – Matches if svc appears anywhere in the process property value.
- $eq(svc.exe) – Matches if svc.exe matches the process property value exactly.
- $prefix(svc) – Matches if app matches the prefix of the process property value.
- $suffix(svc.py) – Matches if svc.py matches the suffix of the process property value.
For example, $suffix(svc.py) would detect processes named loyaltysvc.py and paymentssvc.py.
For more details, see documentation.
- Name string
- If Dynatrace detects this property at startup of a process, it will be matched to this grouping rule.
- case_
sensitive bool - When enabled, matching conditions are case sensitive. When disabled, matching conditions are case insensitive
- property string
- 2.1. Property
- condition string
- $contains(svc) – Matches if svc appears anywhere in the process property value.
- $eq(svc.exe) – Matches if svc.exe matches the process property value exactly.
- $prefix(svc) – Matches if app matches the prefix of the process property value.
- $suffix(svc.py) – Matches if svc.py matches the suffix of the process property value.
For example, $suffix(svc.py) would detect processes named loyaltysvc.py and paymentssvc.py.
For more details, see documentation.
- name string
- If Dynatrace detects this property at startup of a process, it will be matched to this grouping rule.
- case
Sensitive Boolean - When enabled, matching conditions are case sensitive. When disabled, matching conditions are case insensitive
- property String
- 2.1. Property
- condition String
- $contains(svc) – Matches if svc appears anywhere in the process property value.
- $eq(svc.exe) – Matches if svc.exe matches the process property value exactly.
- $prefix(svc) – Matches if app matches the prefix of the process property value.
- $suffix(svc.py) – Matches if svc.py matches the suffix of the process property value.
For example, $suffix(svc.py) would detect processes named loyaltysvc.py and paymentssvc.py.
For more details, see documentation.
- name String
- If Dynatrace detects this property at startup of a process, it will be matched to this grouping rule.
- case
Sensitive boolean - When enabled, matching conditions are case sensitive. When disabled, matching conditions are case insensitive
- property string
- 2.1. Property
- condition string
- $contains(svc) – Matches if svc appears anywhere in the process property value.
- $eq(svc.exe) – Matches if svc.exe matches the process property value exactly.
- $prefix(svc) – Matches if app matches the prefix of the process property value.
- $suffix(svc.py) – Matches if svc.py matches the suffix of the process property value.
For example, $suffix(svc.py) would detect processes named loyaltysvc.py and paymentssvc.py.
For more details, see documentation.
- name string
- If Dynatrace detects this property at startup of a process, it will be matched to this grouping rule.
- case_
sensitive bool - When enabled, matching conditions are case sensitive. When disabled, matching conditions are case insensitive
- property str
- 2.1. Property
- condition str
- $contains(svc) – Matches if svc appears anywhere in the process property value.
- $eq(svc.exe) – Matches if svc.exe matches the process property value exactly.
- $prefix(svc) – Matches if app matches the prefix of the process property value.
- $suffix(svc.py) – Matches if svc.py matches the suffix of the process property value.
For example, $suffix(svc.py) would detect processes named loyaltysvc.py and paymentssvc.py.
For more details, see documentation.
- name str
- If Dynatrace detects this property at startup of a process, it will be matched to this grouping rule.
- case
Sensitive Boolean - When enabled, matching conditions are case sensitive. When disabled, matching conditions are case insensitive
- property String
- 2.1. Property
- condition String
- $contains(svc) – Matches if svc appears anywhere in the process property value.
- $eq(svc.exe) – Matches if svc.exe matches the process property value exactly.
- $prefix(svc) – Matches if app matches the prefix of the process property value.
- $suffix(svc.py) – Matches if svc.py matches the suffix of the process property value.
For example, $suffix(svc.py) would detect processes named loyaltysvc.py and paymentssvc.py.
For more details, see documentation.
- name String
- If Dynatrace detects this property at startup of a process, it will be matched to this grouping rule.
ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSource, ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceArgs
- Standalone
Rule bool Valid only for deep monitored processes.. If this option is selected, the default Dynatrace behavior is disabled for the detected processes. Only this rule is used to separate the process group.
If this option is not selected, this rule contributes to the default Dynatrace process group detection.
- Type string
- Pick which property should be used to identify your process group. You can pick a custom variable or pick an existing process property. Possible values:
CUSTOM,EXISTING - Advanced
Settings Pulumiverse.Dynatrace. Inputs. Process Grouping Rules Pg Extraction Process Group Extraction Pg Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- Id string
- This identifier is used by Dynatrace to recognize this process group.
- Name string
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups.
- Property string
- 3.1.2. Property
- Standalone
Rule bool Valid only for deep monitored processes.. If this option is selected, the default Dynatrace behavior is disabled for the detected processes. Only this rule is used to separate the process group.
If this option is not selected, this rule contributes to the default Dynatrace process group detection.
- Type string
- Pick which property should be used to identify your process group. You can pick a custom variable or pick an existing process property. Possible values:
CUSTOM,EXISTING - Advanced
Settings ProcessGrouping Rules Pg Extraction Process Group Extraction Pg Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- Id string
- This identifier is used by Dynatrace to recognize this process group.
- Name string
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups.
- Property string
- 3.1.2. Property
- standalone_
rule bool Valid only for deep monitored processes.. If this option is selected, the default Dynatrace behavior is disabled for the detected processes. Only this rule is used to separate the process group.
If this option is not selected, this rule contributes to the default Dynatrace process group detection.
- type string
- Pick which property should be used to identify your process group. You can pick a custom variable or pick an existing process property. Possible values:
CUSTOM,EXISTING - advanced_
settings object Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- id string
- This identifier is used by Dynatrace to recognize this process group.
- name string
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups.
- property string
- 3.1.2. Property
- standalone
Rule Boolean Valid only for deep monitored processes.. If this option is selected, the default Dynatrace behavior is disabled for the detected processes. Only this rule is used to separate the process group.
If this option is not selected, this rule contributes to the default Dynatrace process group detection.
- type String
- Pick which property should be used to identify your process group. You can pick a custom variable or pick an existing process property. Possible values:
CUSTOM,EXISTING - advanced
Settings ProcessGrouping Rules Pg Extraction Process Group Extraction Pg Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- id String
- This identifier is used by Dynatrace to recognize this process group.
- name String
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups.
- property String
- 3.1.2. Property
- standalone
Rule boolean Valid only for deep monitored processes.. If this option is selected, the default Dynatrace behavior is disabled for the detected processes. Only this rule is used to separate the process group.
If this option is not selected, this rule contributes to the default Dynatrace process group detection.
- type string
- Pick which property should be used to identify your process group. You can pick a custom variable or pick an existing process property. Possible values:
CUSTOM,EXISTING - advanced
Settings ProcessGrouping Rules Pg Extraction Process Group Extraction Pg Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- id string
- This identifier is used by Dynatrace to recognize this process group.
- name string
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups.
- property string
- 3.1.2. Property
- standalone_
rule bool Valid only for deep monitored processes.. If this option is selected, the default Dynatrace behavior is disabled for the detected processes. Only this rule is used to separate the process group.
If this option is not selected, this rule contributes to the default Dynatrace process group detection.
- type str
- Pick which property should be used to identify your process group. You can pick a custom variable or pick an existing process property. Possible values:
CUSTOM,EXISTING - advanced_
settings ProcessGrouping Rules Pg Extraction Process Group Extraction Pg Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- id str
- This identifier is used by Dynatrace to recognize this process group.
- name str
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups.
- property str
- 3.1.2. Property
- standalone
Rule Boolean Valid only for deep monitored processes.. If this option is selected, the default Dynatrace behavior is disabled for the detected processes. Only this rule is used to separate the process group.
If this option is not selected, this rule contributes to the default Dynatrace process group detection.
- type String
- Pick which property should be used to identify your process group. You can pick a custom variable or pick an existing process property. Possible values:
CUSTOM,EXISTING - advanced
Settings Property Map Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- id String
- This identifier is used by Dynatrace to recognize this process group.
- name String
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups.
- property String
- 3.1.2. Property
ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceAdvancedSettings, ProcessGroupingRulesPgExtractionProcessGroupExtractionPgIdSourceAdvancedSettingsArgs
- Ignore
Numbers bool - (e.g. versions, hex, dates, and build numbers)
- From string
- Delimit from (optional)
- To string
- Delimit to (optional)
- Ignore
Numbers bool - (e.g. versions, hex, dates, and build numbers)
- From string
- Delimit from (optional)
- To string
- Delimit to (optional)
- ignore_
numbers bool - (e.g. versions, hex, dates, and build numbers)
- from string
- Delimit from (optional)
- to string
- Delimit to (optional)
- ignore
Numbers Boolean - (e.g. versions, hex, dates, and build numbers)
- from String
- Delimit from (optional)
- to String
- Delimit to (optional)
- ignore
Numbers boolean - (e.g. versions, hex, dates, and build numbers)
- from string
- Delimit from (optional)
- to string
- Delimit to (optional)
- ignore_
numbers bool - (e.g. versions, hex, dates, and build numbers)
- from_ str
- Delimit from (optional)
- to str
- Delimit to (optional)
- ignore
Numbers Boolean - (e.g. versions, hex, dates, and build numbers)
- from String
- Delimit from (optional)
- to String
- Delimit to (optional)
ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSource, ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceArgs
- Advanced
Settings Pulumiverse.Dynatrace. Inputs. Process Grouping Rules Pg Extraction Process Group Extraction Pgi Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- Name string
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups more granular.
- Property string
- 3.2.1. Property
- Advanced
Settings ProcessGrouping Rules Pg Extraction Process Group Extraction Pgi Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- Name string
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups more granular.
- Property string
- 3.2.1. Property
- advanced_
settings object Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- name string
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups more granular.
- property string
- 3.2.1. Property
- advanced
Settings ProcessGrouping Rules Pg Extraction Process Group Extraction Pgi Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- name String
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups more granular.
- property String
- 3.2.1. Property
- advanced
Settings ProcessGrouping Rules Pg Extraction Process Group Extraction Pgi Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- name string
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups more granular.
- property string
- 3.2.1. Property
- advanced_
settings ProcessGrouping Rules Pg Extraction Process Group Extraction Pgi Id Source Advanced Settings Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- name str
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups more granular.
- property str
- 3.2.1. Property
- advanced
Settings Property Map Set advanced options to customize delimiters and control how property values are processed.. Consider an environment with processes such as:
python myScript.py --env=prod12 --id=12python myScript.py --env=dev2 --id=2- etc.
To group production (prod) and development (dev) processes together you could use Command line property with:
- Delimiter from
--env=to--idto extractprod12anddev2 - Enable Ignore numbers to transform
prod12toprod*anddev2todev*.
- name String
- If Dynatrace detects this property at startup of a process, it will use its value to identify process groups more granular.
- property String
- 3.2.1. Property
ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceAdvancedSettings, ProcessGroupingRulesPgExtractionProcessGroupExtractionPgiIdSourceAdvancedSettingsArgs
- Ignore
Numbers bool - (e.g. versions, hex, dates, and build numbers)
- From string
- Delimit from (optional)
- To string
- Delimit to (optional)
- Ignore
Numbers bool - (e.g. versions, hex, dates, and build numbers)
- From string
- Delimit from (optional)
- To string
- Delimit to (optional)
- ignore_
numbers bool - (e.g. versions, hex, dates, and build numbers)
- from string
- Delimit from (optional)
- to string
- Delimit to (optional)
- ignore
Numbers Boolean - (e.g. versions, hex, dates, and build numbers)
- from String
- Delimit from (optional)
- to String
- Delimit to (optional)
- ignore
Numbers boolean - (e.g. versions, hex, dates, and build numbers)
- from string
- Delimit from (optional)
- to string
- Delimit to (optional)
- ignore_
numbers bool - (e.g. versions, hex, dates, and build numbers)
- from_ str
- Delimit from (optional)
- to str
- Delimit to (optional)
- ignore
Numbers Boolean - (e.g. versions, hex, dates, and build numbers)
- from String
- Delimit from (optional)
- to String
- Delimit to (optional)
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dynatraceTerraform Provider.
published on Tuesday, Jun 23, 2026 by Pulumiverse