Sign in Dashboard Get started
  1. Packages
  2. Packages
  3. Bytepluscc Provider
  4. API Docs
  5. tls
  6. HostGroup
Viewing docs for bytepluscc v0.0.42
published on Monday, Jul 20, 2026 by Byteplus
Schema (JSON)
byteplus-sdk/pulumi-bytepluscc

bytepluscc.tls.HostGroup

bytepluscc logo
Viewing docs for bytepluscc v0.0.42
published on Monday, Jul 20, 2026 by Byteplus
Schema (JSON)
byteplus-sdk/pulumi-bytepluscc

    Machine group in Log Service, used to manage a group of log collection machines.

    Example Usage

    import * as pulumi from "@pulumi/pulumi";
import * as bytepluscc from "@byteplus/pulumi-bytepluscc";

const tLSHostGroupDemo = new bytepluscc.tls.HostGroup("TLSHostGroupDemo", {
    autoUpdate: true,
    hostGroupName: "ccapi-test-1",
    hostGroupType: "IP",
    hostIpLists: [
        "192.168.1.1",
        "192.168.1.2",
    ],
    serviceLogging: false,
    updateEndTime: "06:00",
    updateStartTime: "00:00",
    iamProjectName: "default",
});

    import pulumi
import pulumi_bytepluscc as bytepluscc

t_ls_host_group_demo = bytepluscc.tls.HostGroup("TLSHostGroupDemo",
    auto_update=True,
    host_group_name="ccapi-test-1",
    host_group_type="IP",
    host_ip_lists=[
        "192.168.1.1",
        "192.168.1.2",
    ],
    service_logging=False,
    update_end_time="06:00",
    update_start_time="00:00",
    iam_project_name="default")

    package main

import (
	"github.com/byteplus-sdk/pulumi-bytepluscc/sdk/go/bytepluscc/tls"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := tls.NewHostGroup(ctx, "TLSHostGroupDemo", &tls.HostGroupArgs{
			AutoUpdate:    pulumi.Bool(true),
			HostGroupName: pulumi.String("ccapi-test-1"),
			HostGroupType: pulumi.String("IP"),
			HostIpLists: pulumi.StringArray{
				pulumi.String("192.168.1.1"),
				pulumi.String("192.168.1.2"),
			},
			ServiceLogging:  pulumi.Bool(false),
			UpdateEndTime:   pulumi.String("06:00"),
			UpdateStartTime: pulumi.String("00:00"),
			IamProjectName:  pulumi.String("default"),
		})
		if err != nil {
			return err
		}
		return nil
	})
}

    using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Bytepluscc = Byteplus.Pulumi.Bytepluscc;

return await Deployment.RunAsync(() => 
{
    var tLSHostGroupDemo = new Bytepluscc.Tls.HostGroup("TLSHostGroupDemo", new()
    {
        AutoUpdate = true,
        HostGroupName = "ccapi-test-1",
        HostGroupType = "IP",
        HostIpLists = new[]
        {
            "192.168.1.1",
            "192.168.1.2",
        },
        ServiceLogging = false,
        UpdateEndTime = "06:00",
        UpdateStartTime = "00:00",
        IamProjectName = "default",
    });

});

    package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.byteplus.bytepluscc.tls.HostGroup;
import com.byteplus.bytepluscc.tls.HostGroupArgs;
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 tLSHostGroupDemo = new HostGroup("tLSHostGroupDemo", HostGroupArgs.builder()
            .autoUpdate(true)
            .hostGroupName("ccapi-test-1")
            .hostGroupType("IP")
            .hostIpLists(            
                "192.168.1.1",
                "192.168.1.2")
            .serviceLogging(false)
            .updateEndTime("06:00")
            .updateStartTime("00:00")
            .iamProjectName("default")
            .build());

    }
}

    resources:
  tLSHostGroupDemo:
    type: bytepluscc:tls:HostGroup
    name: TLSHostGroupDemo
    properties:
      autoUpdate: true
      hostGroupName: ccapi-test-1
      hostGroupType: IP
      hostIpLists:
        - 192.168.1.1
        - 192.168.1.2
      serviceLogging: false
      updateEndTime: 06:00
      updateStartTime: 00:00
      iamProjectName: default

    pulumi {
  required_providers {
    bytepluscc = {
      source = "pulumi/bytepluscc"
    }
  }
}

resource "bytepluscc_tls_hostgroup" "TLSHostGroupDemo" {
  auto_update       = true
  host_group_name   = "ccapi-test-1"
  host_group_type   = "IP"
  host_ip_lists     = ["192.168.1.1", "192.168.1.2"]
  service_logging   = false
  update_end_time   = "06:00"
  update_start_time = "00:00"
  iam_project_name  = "default"
}

    Create HostGroup Resource

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

    Constructor syntax

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

@overload
def HostGroup(resource_name: str,
              opts: Optional[ResourceOptions] = None,
              host_group_name: Optional[str] = None,
              host_group_type: Optional[str] = None,
              auto_update: Optional[bool] = None,
              delete_abnormal_hosts: Optional[bool] = None,
              host_identifier: Optional[str] = None,
              host_ip_lists: Optional[Sequence[str]] = None,
              iam_project_name: Optional[str] = None,
              service_logging: Optional[bool] = None,
              update_end_time: Optional[str] = None,
              update_start_time: Optional[str] = None)
    func NewHostGroup(ctx *Context, name string, args HostGroupArgs, opts ...ResourceOption) (*HostGroup, error)
    public HostGroup(string name, HostGroupArgs args, CustomResourceOptions? opts = null)
    public HostGroup(String name, HostGroupArgs args)
public HostGroup(String name, HostGroupArgs args, CustomResourceOptions options)

    type: bytepluscc:tls:HostGroup
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.


    resource "bytepluscc_tls_host_group" "name" {
    # resource properties
}

    Parameters

    name string
    The unique name of the resource.
    args HostGroupArgs
    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 HostGroupArgs
    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 HostGroupArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args HostGroupArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args HostGroupArgs
    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 hostGroupResource = new Bytepluscc.Tls.HostGroup("hostGroupResource", new()
{
    HostGroupName = "string",
    HostGroupType = "string",
    AutoUpdate = false,
    DeleteAbnormalHosts = false,
    HostIdentifier = "string",
    HostIpLists = new[]
    {
        "string",
    },
    IamProjectName = "string",
    ServiceLogging = false,
    UpdateEndTime = "string",
    UpdateStartTime = "string",
});

    example, err := tls.NewHostGroup(ctx, "hostGroupResource", &tls.HostGroupArgs{
	HostGroupName:       pulumi.String("string"),
	HostGroupType:       pulumi.String("string"),
	AutoUpdate:          pulumi.Bool(false),
	DeleteAbnormalHosts: pulumi.Bool(false),
	HostIdentifier:      pulumi.String("string"),
	HostIpLists: pulumi.StringArray{
		pulumi.String("string"),
	},
	IamProjectName:  pulumi.String("string"),
	ServiceLogging:  pulumi.Bool(false),
	UpdateEndTime:   pulumi.String("string"),
	UpdateStartTime: pulumi.String("string"),
})

    resource "bytepluscc_tls_host_group" "hostGroupResource" {
  lifecycle {
    create_before_destroy = true
  }
  host_group_name       = "string"
  host_group_type       = "string"
  auto_update           = false
  delete_abnormal_hosts = false
  host_identifier       = "string"
  host_ip_lists         = ["string"]
  iam_project_name      = "string"
  service_logging       = false
  update_end_time       = "string"
  update_start_time     = "string"
}

    var hostGroupResource = new com.byteplus.bytepluscc.tls.HostGroup("hostGroupResource", com.byteplus.bytepluscc.tls.HostGroupArgs.builder()
    .hostGroupName("string")
    .hostGroupType("string")
    .autoUpdate(false)
    .deleteAbnormalHosts(false)
    .hostIdentifier("string")
    .hostIpLists("string")
    .iamProjectName("string")
    .serviceLogging(false)
    .updateEndTime("string")
    .updateStartTime("string")
    .build());

    host_group_resource = bytepluscc.tls.HostGroup("hostGroupResource",
    host_group_name="string",
    host_group_type="string",
    auto_update=False,
    delete_abnormal_hosts=False,
    host_identifier="string",
    host_ip_lists=["string"],
    iam_project_name="string",
    service_logging=False,
    update_end_time="string",
    update_start_time="string")

    const hostGroupResource = new bytepluscc.tls.HostGroup("hostGroupResource", {
    hostGroupName: "string",
    hostGroupType: "string",
    autoUpdate: false,
    deleteAbnormalHosts: false,
    hostIdentifier: "string",
    hostIpLists: ["string"],
    iamProjectName: "string",
    serviceLogging: false,
    updateEndTime: "string",
    updateStartTime: "string",
});

    type: bytepluscc:tls:HostGroup
properties:
    autoUpdate: false
    deleteAbnormalHosts: false
    hostGroupName: string
    hostGroupType: string
    hostIdentifier: string
    hostIpLists:
        - string
    iamProjectName: string
    serviceLogging: false
    updateEndTime: string
    updateStartTime: string

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

    HostGroupName string
    Host group name
    HostGroupType string
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    AutoUpdate bool
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    DeleteAbnormalHosts bool
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    HostIdentifier string
    Machine identifier. Required when HostGroupType is Label.
    HostIpLists List<string>
    List of IP addresses for the host group. Required when HostGroupType is IP.
    IamProjectName string
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    ServiceLogging bool
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    UpdateEndTime string
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    UpdateStartTime string
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    HostGroupName string
    Host group name
    HostGroupType string
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    AutoUpdate bool
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    DeleteAbnormalHosts bool
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    HostIdentifier string
    Machine identifier. Required when HostGroupType is Label.
    HostIpLists []string
    List of IP addresses for the host group. Required when HostGroupType is IP.
    IamProjectName string
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    ServiceLogging bool
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    UpdateEndTime string
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    UpdateStartTime string
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    host_group_name string
    Host group name
    host_group_type string
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    auto_update bool
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    delete_abnormal_hosts bool
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    host_identifier string
    Machine identifier. Required when HostGroupType is Label.
    host_ip_lists list(string)
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iam_project_name string
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    service_logging bool
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    update_end_time string
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    update_start_time string
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    hostGroupName String
    Host group name
    hostGroupType String
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    autoUpdate Boolean
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    deleteAbnormalHosts Boolean
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    hostIdentifier String
    Machine identifier. Required when HostGroupType is Label.
    hostIpLists List<String>
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iamProjectName String
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    serviceLogging Boolean
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    updateEndTime String
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    updateStartTime String
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    hostGroupName string
    Host group name
    hostGroupType string
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    autoUpdate boolean
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    deleteAbnormalHosts boolean
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    hostIdentifier string
    Machine identifier. Required when HostGroupType is Label.
    hostIpLists string[]
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iamProjectName string
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    serviceLogging boolean
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    updateEndTime string
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    updateStartTime string
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    host_group_name str
    Host group name
    host_group_type str
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    auto_update bool
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    delete_abnormal_hosts bool
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    host_identifier str
    Machine identifier. Required when HostGroupType is Label.
    host_ip_lists Sequence[str]
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iam_project_name str
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    service_logging bool
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    update_end_time str
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    update_start_time str
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    hostGroupName String
    Host group name
    hostGroupType String
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    autoUpdate Boolean
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    deleteAbnormalHosts Boolean
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    hostIdentifier String
    Machine identifier. Required when HostGroupType is Label.
    hostIpLists List<String>
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iamProjectName String
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    serviceLogging Boolean
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    updateEndTime String
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    updateStartTime String
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.

    Outputs

    All input properties are implicitly available as output properties. Additionally, the HostGroup resource produces the following output properties:

    AbnormalHeartbeatStatusNumber int
    Number of abnormal machines.
    AgentLatestVersion string
    Latest agent version.
    CreateTime string
    Creation time.
    HostCount int
    Number of machines.
    HostGroupId string
    Host group ID
    Id string
    The provider-assigned unique ID for this managed resource.
    ModifyTime string
    Modification time.
    NormalHeartbeatStatusNumber int
    Number of healthy machines.
    RuleCount int
    Number of rules
    Rules List<Byteplus.HostGroupRule>
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    AbnormalHeartbeatStatusNumber int
    Number of abnormal machines.
    AgentLatestVersion string
    Latest agent version.
    CreateTime string
    Creation time.
    HostCount int
    Number of machines.
    HostGroupId string
    Host group ID
    Id string
    The provider-assigned unique ID for this managed resource.
    ModifyTime string
    Modification time.
    NormalHeartbeatStatusNumber int
    Number of healthy machines.
    RuleCount int
    Number of rules
    Rules []HostGroupRule
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    abnormal_heartbeat_status_number number
    Number of abnormal machines.
    agent_latest_version string
    Latest agent version.
    create_time string
    Creation time.
    host_count number
    Number of machines.
    host_group_id string
    Host group ID
    id string
    The provider-assigned unique ID for this managed resource.
    modify_time string
    Modification time.
    normal_heartbeat_status_number number
    Number of healthy machines.
    rule_count number
    Number of rules
    rules list(object)
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    abnormalHeartbeatStatusNumber Integer
    Number of abnormal machines.
    agentLatestVersion String
    Latest agent version.
    createTime String
    Creation time.
    hostCount Integer
    Number of machines.
    hostGroupId String
    Host group ID
    id String
    The provider-assigned unique ID for this managed resource.
    modifyTime String
    Modification time.
    normalHeartbeatStatusNumber Integer
    Number of healthy machines.
    ruleCount Integer
    Number of rules
    rules List<HostGroupRule>
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    abnormalHeartbeatStatusNumber number
    Number of abnormal machines.
    agentLatestVersion string
    Latest agent version.
    createTime string
    Creation time.
    hostCount number
    Number of machines.
    hostGroupId string
    Host group ID
    id string
    The provider-assigned unique ID for this managed resource.
    modifyTime string
    Modification time.
    normalHeartbeatStatusNumber number
    Number of healthy machines.
    ruleCount number
    Number of rules
    rules HostGroupRule[]
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    abnormal_heartbeat_status_number int
    Number of abnormal machines.
    agent_latest_version str
    Latest agent version.
    create_time str
    Creation time.
    host_count int
    Number of machines.
    host_group_id str
    Host group ID
    id str
    The provider-assigned unique ID for this managed resource.
    modify_time str
    Modification time.
    normal_heartbeat_status_number int
    Number of healthy machines.
    rule_count int
    Number of rules
    rules Sequence[HostGroupRule]
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    abnormalHeartbeatStatusNumber Number
    Number of abnormal machines.
    agentLatestVersion String
    Latest agent version.
    createTime String
    Creation time.
    hostCount Number
    Number of machines.
    hostGroupId String
    Host group ID
    id String
    The provider-assigned unique ID for this managed resource.
    modifyTime String
    Modification time.
    normalHeartbeatStatusNumber Number
    Number of healthy machines.
    ruleCount Number
    Number of rules
    rules List<Property Map>
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.

    Look up Existing HostGroup Resource

    Get an existing HostGroup 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?: HostGroupState, opts?: CustomResourceOptions): HostGroup
    @staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        abnormal_heartbeat_status_number: Optional[int] = None,
        agent_latest_version: Optional[str] = None,
        auto_update: Optional[bool] = None,
        create_time: Optional[str] = None,
        delete_abnormal_hosts: Optional[bool] = None,
        host_count: Optional[int] = None,
        host_group_id: Optional[str] = None,
        host_group_name: Optional[str] = None,
        host_group_type: Optional[str] = None,
        host_identifier: Optional[str] = None,
        host_ip_lists: Optional[Sequence[str]] = None,
        iam_project_name: Optional[str] = None,
        modify_time: Optional[str] = None,
        normal_heartbeat_status_number: Optional[int] = None,
        rule_count: Optional[int] = None,
        rules: Optional[Sequence[HostGroupRuleArgs]] = None,
        service_logging: Optional[bool] = None,
        update_end_time: Optional[str] = None,
        update_start_time: Optional[str] = None) -> HostGroup
    func GetHostGroup(ctx *Context, name string, id IDInput, state *HostGroupState, opts ...ResourceOption) (*HostGroup, error)
    public static HostGroup Get(string name, Input<string> id, HostGroupState? state, CustomResourceOptions? opts = null)
    public static HostGroup get(String name, Output<String> id, HostGroupState state, CustomResourceOptions options)
    resources:  _:    type: bytepluscc:tls:HostGroup    get:      id: ${id}
    import {
  to = bytepluscc_tls_host_group.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.
    The following state arguments are supported:
    AbnormalHeartbeatStatusNumber int
    Number of abnormal machines.
    AgentLatestVersion string
    Latest agent version.
    AutoUpdate bool
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    CreateTime string
    Creation time.
    DeleteAbnormalHosts bool
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    HostCount int
    Number of machines.
    HostGroupId string
    Host group ID
    HostGroupName string
    Host group name
    HostGroupType string
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    HostIdentifier string
    Machine identifier. Required when HostGroupType is Label.
    HostIpLists List<string>
    List of IP addresses for the host group. Required when HostGroupType is IP.
    IamProjectName string
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    ModifyTime string
    Modification time.
    NormalHeartbeatStatusNumber int
    Number of healthy machines.
    RuleCount int
    Number of rules
    Rules List<Byteplus.HostGroupRule>
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ServiceLogging bool
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    UpdateEndTime string
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    UpdateStartTime string
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    AbnormalHeartbeatStatusNumber int
    Number of abnormal machines.
    AgentLatestVersion string
    Latest agent version.
    AutoUpdate bool
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    CreateTime string
    Creation time.
    DeleteAbnormalHosts bool
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    HostCount int
    Number of machines.
    HostGroupId string
    Host group ID
    HostGroupName string
    Host group name
    HostGroupType string
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    HostIdentifier string
    Machine identifier. Required when HostGroupType is Label.
    HostIpLists []string
    List of IP addresses for the host group. Required when HostGroupType is IP.
    IamProjectName string
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    ModifyTime string
    Modification time.
    NormalHeartbeatStatusNumber int
    Number of healthy machines.
    RuleCount int
    Number of rules
    Rules []HostGroupRuleArgs
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ServiceLogging bool
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    UpdateEndTime string
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    UpdateStartTime string
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    abnormal_heartbeat_status_number number
    Number of abnormal machines.
    agent_latest_version string
    Latest agent version.
    auto_update bool
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    create_time string
    Creation time.
    delete_abnormal_hosts bool
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    host_count number
    Number of machines.
    host_group_id string
    Host group ID
    host_group_name string
    Host group name
    host_group_type string
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    host_identifier string
    Machine identifier. Required when HostGroupType is Label.
    host_ip_lists list(string)
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iam_project_name string
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    modify_time string
    Modification time.
    normal_heartbeat_status_number number
    Number of healthy machines.
    rule_count number
    Number of rules
    rules list(object)
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    service_logging bool
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    update_end_time string
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    update_start_time string
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    abnormalHeartbeatStatusNumber Integer
    Number of abnormal machines.
    agentLatestVersion String
    Latest agent version.
    autoUpdate Boolean
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    createTime String
    Creation time.
    deleteAbnormalHosts Boolean
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    hostCount Integer
    Number of machines.
    hostGroupId String
    Host group ID
    hostGroupName String
    Host group name
    hostGroupType String
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    hostIdentifier String
    Machine identifier. Required when HostGroupType is Label.
    hostIpLists List<String>
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iamProjectName String
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    modifyTime String
    Modification time.
    normalHeartbeatStatusNumber Integer
    Number of healthy machines.
    ruleCount Integer
    Number of rules
    rules List<HostGroupRule>
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    serviceLogging Boolean
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    updateEndTime String
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    updateStartTime String
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    abnormalHeartbeatStatusNumber number
    Number of abnormal machines.
    agentLatestVersion string
    Latest agent version.
    autoUpdate boolean
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    createTime string
    Creation time.
    deleteAbnormalHosts boolean
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    hostCount number
    Number of machines.
    hostGroupId string
    Host group ID
    hostGroupName string
    Host group name
    hostGroupType string
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    hostIdentifier string
    Machine identifier. Required when HostGroupType is Label.
    hostIpLists string[]
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iamProjectName string
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    modifyTime string
    Modification time.
    normalHeartbeatStatusNumber number
    Number of healthy machines.
    ruleCount number
    Number of rules
    rules HostGroupRule[]
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    serviceLogging boolean
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    updateEndTime string
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    updateStartTime string
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    abnormal_heartbeat_status_number int
    Number of abnormal machines.
    agent_latest_version str
    Latest agent version.
    auto_update bool
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    create_time str
    Creation time.
    delete_abnormal_hosts bool
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    host_count int
    Number of machines.
    host_group_id str
    Host group ID
    host_group_name str
    Host group name
    host_group_type str
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    host_identifier str
    Machine identifier. Required when HostGroupType is Label.
    host_ip_lists Sequence[str]
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iam_project_name str
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    modify_time str
    Modification time.
    normal_heartbeat_status_number int
    Number of healthy machines.
    rule_count int
    Number of rules
    rules Sequence[HostGroupRuleArgs]
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    service_logging bool
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    update_end_time str
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    update_start_time str
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.
    abnormalHeartbeatStatusNumber Number
    Number of abnormal machines.
    agentLatestVersion String
    Latest agent version.
    autoUpdate Boolean
    Whether LogCollector installed on machine group servers enables automatic upgrade. true: Log Service will check for upgrade conditions during the specified time period each day. If conditions are met, LogCollector upgrades automatically without manual intervention. false: (default) LogCollector does not upgrade automatically. Only LogCollector V1.0.8 and later versions support automatic upgrade.
    createTime String
    Creation time.
    deleteAbnormalHosts Boolean
    Clean all machines with abnormal heartbeat in the machine group with one click. Machines without heartbeat records cannot be deleted currently
    hostCount Number
    Number of machines.
    hostGroupId String
    Host group ID
    hostGroupName String
    Host group name
    hostGroupType String
    Type of machine group. Includes: IP: machine IP. Set the machine IP list using the HostIpList parameter. Label: machine identifier. Set the machine identifier using the HostIdentifier parameter.
    hostIdentifier String
    Machine identifier. Required when HostGroupType is Label.
    hostIpLists List<String>
    List of IP addresses for the host group. Required when HostGroupType is IP.
    iamProjectName String
    IAM project name. If this parameter is not specified, Log Service adds the machine group to the IAM project named default.
    modifyTime String
    Modification time.
    normalHeartbeatStatusNumber Number
    Number of healthy machines.
    ruleCount Number
    Number of rules
    rules List<Property Map>
    Collection configuration information list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    serviceLogging Boolean
    Enable Logcollector service log feature. true: enabled. false: (default) disabled.
    updateEndTime String
    Auto upgrade end time in HH:MM format. Required only when AutoUpdate is set to true. It is recommended to schedule auto upgrade during off-peak business hours. LogCollector may restart during the auto upgrade, but logs will not be lost.
    updateStartTime String
    Automatic upgrade start time, in HH:MM format. Only required when AutoUpdate is set to true. It is recommended to schedule automatic upgrades during off-peak hours. LogCollector may restart during the upgrade, but logs will not be lost.

    Supporting Types

    HostGroupRule, HostGroupRuleArgs

    ContainerRule Byteplus.HostGroupRuleContainerRule
    Container collection rules
    CreateTime string
    Time when the collection configuration was created.
    ExcludePaths List<Byteplus.HostGroupRuleExcludePath>
    Extraction rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ExtractRule Byteplus.HostGroupRuleExtractRule
    Extraction rules
    InputType int
    Collection type. 0: Host log file. 1: K8s container standard output. 2: Log file inside K8s container.
    LogSample string
    Log sample.
    LogType string
    Collection modes. minimalistlog: single-line full mode. jsonlog: JSON mode. delimiterlog: delimiter mode. multilinelog: multi-line full mode. fullregex_log: full regex mode.
    ModifyTime string
    Time when the collection configuration was modified.
    Paths List<string>
    Data collection path list
    Pause int
    Running status of the collection configuration. 0: Running. 1: Paused.
    RuleId string
    Collection configuration ID.
    RuleName string
    Name of the collection configuration.
    TopicId string
    ID of the log topic to which the collection configuration belongs.
    TopicName string
    Name of the log topic associated with the collection configuration
    UserDefineRule Byteplus.HostGroupRuleUserDefineRule
    User-defined collection rules.
    ContainerRule HostGroupRuleContainerRule
    Container collection rules
    CreateTime string
    Time when the collection configuration was created.
    ExcludePaths []HostGroupRuleExcludePath
    Extraction rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ExtractRule HostGroupRuleExtractRule
    Extraction rules
    InputType int
    Collection type. 0: Host log file. 1: K8s container standard output. 2: Log file inside K8s container.
    LogSample string
    Log sample.
    LogType string
    Collection modes. minimalistlog: single-line full mode. jsonlog: JSON mode. delimiterlog: delimiter mode. multilinelog: multi-line full mode. fullregex_log: full regex mode.
    ModifyTime string
    Time when the collection configuration was modified.
    Paths []string
    Data collection path list
    Pause int
    Running status of the collection configuration. 0: Running. 1: Paused.
    RuleId string
    Collection configuration ID.
    RuleName string
    Name of the collection configuration.
    TopicId string
    ID of the log topic to which the collection configuration belongs.
    TopicName string
    Name of the log topic associated with the collection configuration
    UserDefineRule HostGroupRuleUserDefineRule
    User-defined collection rules.
    container_rule object
    Container collection rules
    create_time string
    Time when the collection configuration was created.
    exclude_paths list(object)
    Extraction rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    extract_rule object
    Extraction rules
    input_type number
    Collection type. 0: Host log file. 1: K8s container standard output. 2: Log file inside K8s container.
    log_sample string
    Log sample.
    log_type string
    Collection modes. minimalistlog: single-line full mode. jsonlog: JSON mode. delimiterlog: delimiter mode. multilinelog: multi-line full mode. fullregex_log: full regex mode.
    modify_time string
    Time when the collection configuration was modified.
    paths list(string)
    Data collection path list
    pause number
    Running status of the collection configuration. 0: Running. 1: Paused.
    rule_id string
    Collection configuration ID.
    rule_name string
    Name of the collection configuration.
    topic_id string
    ID of the log topic to which the collection configuration belongs.
    topic_name string
    Name of the log topic associated with the collection configuration
    user_define_rule object
    User-defined collection rules.
    containerRule HostGroupRuleContainerRule
    Container collection rules
    createTime String
    Time when the collection configuration was created.
    excludePaths List<HostGroupRuleExcludePath>
    Extraction rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    extractRule HostGroupRuleExtractRule
    Extraction rules
    inputType Integer
    Collection type. 0: Host log file. 1: K8s container standard output. 2: Log file inside K8s container.
    logSample String
    Log sample.
    logType String
    Collection modes. minimalistlog: single-line full mode. jsonlog: JSON mode. delimiterlog: delimiter mode. multilinelog: multi-line full mode. fullregex_log: full regex mode.
    modifyTime String
    Time when the collection configuration was modified.
    paths List<String>
    Data collection path list
    pause Integer
    Running status of the collection configuration. 0: Running. 1: Paused.
    ruleId String
    Collection configuration ID.
    ruleName String
    Name of the collection configuration.
    topicId String
    ID of the log topic to which the collection configuration belongs.
    topicName String
    Name of the log topic associated with the collection configuration
    userDefineRule HostGroupRuleUserDefineRule
    User-defined collection rules.
    containerRule HostGroupRuleContainerRule
    Container collection rules
    createTime string
    Time when the collection configuration was created.
    excludePaths HostGroupRuleExcludePath[]
    Extraction rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    extractRule HostGroupRuleExtractRule
    Extraction rules
    inputType number
    Collection type. 0: Host log file. 1: K8s container standard output. 2: Log file inside K8s container.
    logSample string
    Log sample.
    logType string
    Collection modes. minimalistlog: single-line full mode. jsonlog: JSON mode. delimiterlog: delimiter mode. multilinelog: multi-line full mode. fullregex_log: full regex mode.
    modifyTime string
    Time when the collection configuration was modified.
    paths string[]
    Data collection path list
    pause number
    Running status of the collection configuration. 0: Running. 1: Paused.
    ruleId string
    Collection configuration ID.
    ruleName string
    Name of the collection configuration.
    topicId string
    ID of the log topic to which the collection configuration belongs.
    topicName string
    Name of the log topic associated with the collection configuration
    userDefineRule HostGroupRuleUserDefineRule
    User-defined collection rules.
    container_rule HostGroupRuleContainerRule
    Container collection rules
    create_time str
    Time when the collection configuration was created.
    exclude_paths Sequence[HostGroupRuleExcludePath]
    Extraction rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    extract_rule HostGroupRuleExtractRule
    Extraction rules
    input_type int
    Collection type. 0: Host log file. 1: K8s container standard output. 2: Log file inside K8s container.
    log_sample str
    Log sample.
    log_type str
    Collection modes. minimalistlog: single-line full mode. jsonlog: JSON mode. delimiterlog: delimiter mode. multilinelog: multi-line full mode. fullregex_log: full regex mode.
    modify_time str
    Time when the collection configuration was modified.
    paths Sequence[str]
    Data collection path list
    pause int
    Running status of the collection configuration. 0: Running. 1: Paused.
    rule_id str
    Collection configuration ID.
    rule_name str
    Name of the collection configuration.
    topic_id str
    ID of the log topic to which the collection configuration belongs.
    topic_name str
    Name of the log topic associated with the collection configuration
    user_define_rule HostGroupRuleUserDefineRule
    User-defined collection rules.
    containerRule Property Map
    Container collection rules
    createTime String
    Time when the collection configuration was created.
    excludePaths List<Property Map>
    Extraction rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    extractRule Property Map
    Extraction rules
    inputType Number
    Collection type. 0: Host log file. 1: K8s container standard output. 2: Log file inside K8s container.
    logSample String
    Log sample.
    logType String
    Collection modes. minimalistlog: single-line full mode. jsonlog: JSON mode. delimiterlog: delimiter mode. multilinelog: multi-line full mode. fullregex_log: full regex mode.
    modifyTime String
    Time when the collection configuration was modified.
    paths List<String>
    Data collection path list
    pause Number
    Running status of the collection configuration. 0: Running. 1: Paused.
    ruleId String
    Collection configuration ID.
    ruleName String
    Name of the collection configuration.
    topicId String
    ID of the log topic to which the collection configuration belongs.
    topicName String
    Name of the log topic associated with the collection configuration
    userDefineRule Property Map
    User-defined collection rules.

    HostGroupRuleContainerRule, HostGroupRuleContainerRuleArgs

    ContainerNameRegex string
    Container name to collect. If no container name is specified, all containers in the machine group are collected. Supports regular expressions. For example, setting the container name to ^(container-test)$ collects all containers named container-test.
    EnvTags List<Byteplus.HostGroupRuleContainerRuleEnvTag>
    Whether to add environment variables as log tags to the raw log data. When enabled, Log Service adds container environment variable fields to logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the container has the environment variable source=DC, Log Service adds the field tagdata_source_*: DC to the log. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ExcludeContainerEnvRegexes List<Byteplus.HostGroupRuleContainerRuleExcludeContainerEnvRegex>
    Container environment variable denylist/blocklist specifies containers to exclude from collection. If the denylist/blocklist is not enabled, all containers are collected. If enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in their environment variables are excluded. If Value is not empty, only containers matching the key-value pair are excluded—that is, containers with the specified Key and a Value matching the given pattern. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR: any container matching any pair is excluded from collection. When the denylist/blocklist is enabled, Keys cannot be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ExcludeContainerLabelRegexes List<Byteplus.HostGroupRuleContainerRuleExcludeContainerLabelRegex>
    The container Label denylist specifies which containers to exclude from collection. If not enabled, all containers are collected. If the container Label denylist is enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the container Label are excluded. If Value is not empty, only containers matching the Key-Value pair are excluded, meaning only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to app and Value to ^(test1|test2)$ to exclude containers with app:test1 or app:test2 in the container Label. The logical relationship between multiple Key-Value pairs is OR, meaning any container Label matching any pair will be excluded from collection. When enabling the container Label denylist, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    IncludeContainerEnvRegexes List<Byteplus.HostGroupRuleContainerRuleIncludeContainerEnvRegex>
    The container environment variable allowlist specifies which containers to collect by using environment variables as criteria. If the allowlist is not enabled, all containers are collected. When the container environment variable allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty: collect all containers that contain the Key in their environment variables. If Value is not empty: only collect containers where the Key exists and its value matches Value. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR; any container environment variable matching any key-value pair will be included in the collection scope. When the container environment variable allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    IncludeContainerLabelRegexes List<Byteplus.HostGroupRuleContainerRuleIncludeContainerLabelRegex>
    The container Label allowlist specifies which containers to collect based on container Labels. If the allowlist is not enabled, all containers are collected. When the container Label allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty, all containers with the specified Key in their container Label are collected. If Value is not empty, only containers with the specified Key and a Value matching the Value field are collected. Value supports regular expressions. For example, set Key to app and Value to ^(test1|test2)$ to collect only containers with app:test1 or app:test2 in their container Label. The logical relationship between multiple key-value pairs is OR; any container Label matching any key-value pair will be included in the collection scope. When the container Label allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    KubernetesRule Byteplus.HostGroupRuleContainerRuleKubernetesRule
    Kubernetes container collection rules.
    Stream string
    Collection information. stdout: Container standard output (stdout). stderr: Container standard error (stderr). all: Both container standard output (stdout) and standard error (stderr).
    ContainerNameRegex string
    Container name to collect. If no container name is specified, all containers in the machine group are collected. Supports regular expressions. For example, setting the container name to ^(container-test)$ collects all containers named container-test.
    EnvTags []HostGroupRuleContainerRuleEnvTag
    Whether to add environment variables as log tags to the raw log data. When enabled, Log Service adds container environment variable fields to logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the container has the environment variable source=DC, Log Service adds the field tagdata_source_*: DC to the log. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ExcludeContainerEnvRegexes []HostGroupRuleContainerRuleExcludeContainerEnvRegex
    Container environment variable denylist/blocklist specifies containers to exclude from collection. If the denylist/blocklist is not enabled, all containers are collected. If enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in their environment variables are excluded. If Value is not empty, only containers matching the key-value pair are excluded—that is, containers with the specified Key and a Value matching the given pattern. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR: any container matching any pair is excluded from collection. When the denylist/blocklist is enabled, Keys cannot be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ExcludeContainerLabelRegexes []HostGroupRuleContainerRuleExcludeContainerLabelRegex
    The container Label denylist specifies which containers to exclude from collection. If not enabled, all containers are collected. If the container Label denylist is enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the container Label are excluded. If Value is not empty, only containers matching the Key-Value pair are excluded, meaning only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to app and Value to ^(test1|test2)$ to exclude containers with app:test1 or app:test2 in the container Label. The logical relationship between multiple Key-Value pairs is OR, meaning any container Label matching any pair will be excluded from collection. When enabling the container Label denylist, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    IncludeContainerEnvRegexes []HostGroupRuleContainerRuleIncludeContainerEnvRegex
    The container environment variable allowlist specifies which containers to collect by using environment variables as criteria. If the allowlist is not enabled, all containers are collected. When the container environment variable allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty: collect all containers that contain the Key in their environment variables. If Value is not empty: only collect containers where the Key exists and its value matches Value. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR; any container environment variable matching any key-value pair will be included in the collection scope. When the container environment variable allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    IncludeContainerLabelRegexes []HostGroupRuleContainerRuleIncludeContainerLabelRegex
    The container Label allowlist specifies which containers to collect based on container Labels. If the allowlist is not enabled, all containers are collected. When the container Label allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty, all containers with the specified Key in their container Label are collected. If Value is not empty, only containers with the specified Key and a Value matching the Value field are collected. Value supports regular expressions. For example, set Key to app and Value to ^(test1|test2)$ to collect only containers with app:test1 or app:test2 in their container Label. The logical relationship between multiple key-value pairs is OR; any container Label matching any key-value pair will be included in the collection scope. When the container Label allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    KubernetesRule HostGroupRuleContainerRuleKubernetesRule
    Kubernetes container collection rules.
    Stream string
    Collection information. stdout: Container standard output (stdout). stderr: Container standard error (stderr). all: Both container standard output (stdout) and standard error (stderr).
    container_name_regex string
    Container name to collect. If no container name is specified, all containers in the machine group are collected. Supports regular expressions. For example, setting the container name to ^(container-test)$ collects all containers named container-test.
    env_tags list(object)
    Whether to add environment variables as log tags to the raw log data. When enabled, Log Service adds container environment variable fields to logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the container has the environment variable source=DC, Log Service adds the field tagdata_source_*: DC to the log. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    exclude_container_env_regexes list(object)
    Container environment variable denylist/blocklist specifies containers to exclude from collection. If the denylist/blocklist is not enabled, all containers are collected. If enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in their environment variables are excluded. If Value is not empty, only containers matching the key-value pair are excluded—that is, containers with the specified Key and a Value matching the given pattern. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR: any container matching any pair is excluded from collection. When the denylist/blocklist is enabled, Keys cannot be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    exclude_container_label_regexes list(object)
    The container Label denylist specifies which containers to exclude from collection. If not enabled, all containers are collected. If the container Label denylist is enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the container Label are excluded. If Value is not empty, only containers matching the Key-Value pair are excluded, meaning only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to app and Value to ^(test1|test2)$ to exclude containers with app:test1 or app:test2 in the container Label. The logical relationship between multiple Key-Value pairs is OR, meaning any container Label matching any pair will be excluded from collection. When enabling the container Label denylist, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    include_container_env_regexes list(object)
    The container environment variable allowlist specifies which containers to collect by using environment variables as criteria. If the allowlist is not enabled, all containers are collected. When the container environment variable allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty: collect all containers that contain the Key in their environment variables. If Value is not empty: only collect containers where the Key exists and its value matches Value. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR; any container environment variable matching any key-value pair will be included in the collection scope. When the container environment variable allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    include_container_label_regexes list(object)
    The container Label allowlist specifies which containers to collect based on container Labels. If the allowlist is not enabled, all containers are collected. When the container Label allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty, all containers with the specified Key in their container Label are collected. If Value is not empty, only containers with the specified Key and a Value matching the Value field are collected. Value supports regular expressions. For example, set Key to app and Value to ^(test1|test2)$ to collect only containers with app:test1 or app:test2 in their container Label. The logical relationship between multiple key-value pairs is OR; any container Label matching any key-value pair will be included in the collection scope. When the container Label allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    kubernetes_rule object
    Kubernetes container collection rules.
    stream string
    Collection information. stdout: Container standard output (stdout). stderr: Container standard error (stderr). all: Both container standard output (stdout) and standard error (stderr).
    containerNameRegex String
    Container name to collect. If no container name is specified, all containers in the machine group are collected. Supports regular expressions. For example, setting the container name to ^(container-test)$ collects all containers named container-test.
    envTags List<HostGroupRuleContainerRuleEnvTag>
    Whether to add environment variables as log tags to the raw log data. When enabled, Log Service adds container environment variable fields to logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the container has the environment variable source=DC, Log Service adds the field tagdata_source_*: DC to the log. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    excludeContainerEnvRegexes List<HostGroupRuleContainerRuleExcludeContainerEnvRegex>
    Container environment variable denylist/blocklist specifies containers to exclude from collection. If the denylist/blocklist is not enabled, all containers are collected. If enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in their environment variables are excluded. If Value is not empty, only containers matching the key-value pair are excluded—that is, containers with the specified Key and a Value matching the given pattern. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR: any container matching any pair is excluded from collection. When the denylist/blocklist is enabled, Keys cannot be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    excludeContainerLabelRegexes List<HostGroupRuleContainerRuleExcludeContainerLabelRegex>
    The container Label denylist specifies which containers to exclude from collection. If not enabled, all containers are collected. If the container Label denylist is enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the container Label are excluded. If Value is not empty, only containers matching the Key-Value pair are excluded, meaning only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to app and Value to ^(test1|test2)$ to exclude containers with app:test1 or app:test2 in the container Label. The logical relationship between multiple Key-Value pairs is OR, meaning any container Label matching any pair will be excluded from collection. When enabling the container Label denylist, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includeContainerEnvRegexes List<HostGroupRuleContainerRuleIncludeContainerEnvRegex>
    The container environment variable allowlist specifies which containers to collect by using environment variables as criteria. If the allowlist is not enabled, all containers are collected. When the container environment variable allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty: collect all containers that contain the Key in their environment variables. If Value is not empty: only collect containers where the Key exists and its value matches Value. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR; any container environment variable matching any key-value pair will be included in the collection scope. When the container environment variable allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includeContainerLabelRegexes List<HostGroupRuleContainerRuleIncludeContainerLabelRegex>
    The container Label allowlist specifies which containers to collect based on container Labels. If the allowlist is not enabled, all containers are collected. When the container Label allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty, all containers with the specified Key in their container Label are collected. If Value is not empty, only containers with the specified Key and a Value matching the Value field are collected. Value supports regular expressions. For example, set Key to app and Value to ^(test1|test2)$ to collect only containers with app:test1 or app:test2 in their container Label. The logical relationship between multiple key-value pairs is OR; any container Label matching any key-value pair will be included in the collection scope. When the container Label allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    kubernetesRule HostGroupRuleContainerRuleKubernetesRule
    Kubernetes container collection rules.
    stream String
    Collection information. stdout: Container standard output (stdout). stderr: Container standard error (stderr). all: Both container standard output (stdout) and standard error (stderr).
    containerNameRegex string
    Container name to collect. If no container name is specified, all containers in the machine group are collected. Supports regular expressions. For example, setting the container name to ^(container-test)$ collects all containers named container-test.
    envTags HostGroupRuleContainerRuleEnvTag[]
    Whether to add environment variables as log tags to the raw log data. When enabled, Log Service adds container environment variable fields to logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the container has the environment variable source=DC, Log Service adds the field tagdata_source_*: DC to the log. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    excludeContainerEnvRegexes HostGroupRuleContainerRuleExcludeContainerEnvRegex[]
    Container environment variable denylist/blocklist specifies containers to exclude from collection. If the denylist/blocklist is not enabled, all containers are collected. If enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in their environment variables are excluded. If Value is not empty, only containers matching the key-value pair are excluded—that is, containers with the specified Key and a Value matching the given pattern. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR: any container matching any pair is excluded from collection. When the denylist/blocklist is enabled, Keys cannot be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    excludeContainerLabelRegexes HostGroupRuleContainerRuleExcludeContainerLabelRegex[]
    The container Label denylist specifies which containers to exclude from collection. If not enabled, all containers are collected. If the container Label denylist is enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the container Label are excluded. If Value is not empty, only containers matching the Key-Value pair are excluded, meaning only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to app and Value to ^(test1|test2)$ to exclude containers with app:test1 or app:test2 in the container Label. The logical relationship between multiple Key-Value pairs is OR, meaning any container Label matching any pair will be excluded from collection. When enabling the container Label denylist, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includeContainerEnvRegexes HostGroupRuleContainerRuleIncludeContainerEnvRegex[]
    The container environment variable allowlist specifies which containers to collect by using environment variables as criteria. If the allowlist is not enabled, all containers are collected. When the container environment variable allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty: collect all containers that contain the Key in their environment variables. If Value is not empty: only collect containers where the Key exists and its value matches Value. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR; any container environment variable matching any key-value pair will be included in the collection scope. When the container environment variable allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includeContainerLabelRegexes HostGroupRuleContainerRuleIncludeContainerLabelRegex[]
    The container Label allowlist specifies which containers to collect based on container Labels. If the allowlist is not enabled, all containers are collected. When the container Label allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty, all containers with the specified Key in their container Label are collected. If Value is not empty, only containers with the specified Key and a Value matching the Value field are collected. Value supports regular expressions. For example, set Key to app and Value to ^(test1|test2)$ to collect only containers with app:test1 or app:test2 in their container Label. The logical relationship between multiple key-value pairs is OR; any container Label matching any key-value pair will be included in the collection scope. When the container Label allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    kubernetesRule HostGroupRuleContainerRuleKubernetesRule
    Kubernetes container collection rules.
    stream string
    Collection information. stdout: Container standard output (stdout). stderr: Container standard error (stderr). all: Both container standard output (stdout) and standard error (stderr).
    container_name_regex str
    Container name to collect. If no container name is specified, all containers in the machine group are collected. Supports regular expressions. For example, setting the container name to ^(container-test)$ collects all containers named container-test.
    env_tags Sequence[HostGroupRuleContainerRuleEnvTag]
    Whether to add environment variables as log tags to the raw log data. When enabled, Log Service adds container environment variable fields to logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the container has the environment variable source=DC, Log Service adds the field tagdata_source_*: DC to the log. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    exclude_container_env_regexes Sequence[HostGroupRuleContainerRuleExcludeContainerEnvRegex]
    Container environment variable denylist/blocklist specifies containers to exclude from collection. If the denylist/blocklist is not enabled, all containers are collected. If enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in their environment variables are excluded. If Value is not empty, only containers matching the key-value pair are excluded—that is, containers with the specified Key and a Value matching the given pattern. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR: any container matching any pair is excluded from collection. When the denylist/blocklist is enabled, Keys cannot be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    exclude_container_label_regexes Sequence[HostGroupRuleContainerRuleExcludeContainerLabelRegex]
    The container Label denylist specifies which containers to exclude from collection. If not enabled, all containers are collected. If the container Label denylist is enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the container Label are excluded. If Value is not empty, only containers matching the Key-Value pair are excluded, meaning only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to app and Value to ^(test1|test2)$ to exclude containers with app:test1 or app:test2 in the container Label. The logical relationship between multiple Key-Value pairs is OR, meaning any container Label matching any pair will be excluded from collection. When enabling the container Label denylist, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    include_container_env_regexes Sequence[HostGroupRuleContainerRuleIncludeContainerEnvRegex]
    The container environment variable allowlist specifies which containers to collect by using environment variables as criteria. If the allowlist is not enabled, all containers are collected. When the container environment variable allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty: collect all containers that contain the Key in their environment variables. If Value is not empty: only collect containers where the Key exists and its value matches Value. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR; any container environment variable matching any key-value pair will be included in the collection scope. When the container environment variable allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    include_container_label_regexes Sequence[HostGroupRuleContainerRuleIncludeContainerLabelRegex]
    The container Label allowlist specifies which containers to collect based on container Labels. If the allowlist is not enabled, all containers are collected. When the container Label allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty, all containers with the specified Key in their container Label are collected. If Value is not empty, only containers with the specified Key and a Value matching the Value field are collected. Value supports regular expressions. For example, set Key to app and Value to ^(test1|test2)$ to collect only containers with app:test1 or app:test2 in their container Label. The logical relationship between multiple key-value pairs is OR; any container Label matching any key-value pair will be included in the collection scope. When the container Label allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    kubernetes_rule HostGroupRuleContainerRuleKubernetesRule
    Kubernetes container collection rules.
    stream str
    Collection information. stdout: Container standard output (stdout). stderr: Container standard error (stderr). all: Both container standard output (stdout) and standard error (stderr).
    containerNameRegex String
    Container name to collect. If no container name is specified, all containers in the machine group are collected. Supports regular expressions. For example, setting the container name to ^(container-test)$ collects all containers named container-test.
    envTags List<Property Map>
    Whether to add environment variables as log tags to the raw log data. When enabled, Log Service adds container environment variable fields to logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the container has the environment variable source=DC, Log Service adds the field tagdata_source_*: DC to the log. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    excludeContainerEnvRegexes List<Property Map>
    Container environment variable denylist/blocklist specifies containers to exclude from collection. If the denylist/blocklist is not enabled, all containers are collected. If enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in their environment variables are excluded. If Value is not empty, only containers matching the key-value pair are excluded—that is, containers with the specified Key and a Value matching the given pattern. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR: any container matching any pair is excluded from collection. When the denylist/blocklist is enabled, Keys cannot be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    excludeContainerLabelRegexes List<Property Map>
    The container Label denylist specifies which containers to exclude from collection. If not enabled, all containers are collected. If the container Label denylist is enabled, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the container Label are excluded. If Value is not empty, only containers matching the Key-Value pair are excluded, meaning only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to app and Value to ^(test1|test2)$ to exclude containers with app:test1 or app:test2 in the container Label. The logical relationship between multiple Key-Value pairs is OR, meaning any container Label matching any pair will be excluded from collection. When enabling the container Label denylist, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includeContainerEnvRegexes List<Property Map>
    The container environment variable allowlist specifies which containers to collect by using environment variables as criteria. If the allowlist is not enabled, all containers are collected. When the container environment variable allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty: collect all containers that contain the Key in their environment variables. If Value is not empty: only collect containers where the Key exists and its value matches Value. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their environment variables. Multiple key-value pairs use logical OR; any container environment variable matching any key-value pair will be included in the collection scope. When the container environment variable allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includeContainerLabelRegexes List<Property Map>
    The container Label allowlist specifies which containers to collect based on container Labels. If the allowlist is not enabled, all containers are collected. When the container Label allowlist is enabled, you must enter key-value pairs. Key is required; Value is optional. If Value is empty, all containers with the specified Key in their container Label are collected. If Value is not empty, only containers with the specified Key and a Value matching the Value field are collected. Value supports regular expressions. For example, set Key to app and Value to ^(test1|test2)$ to collect only containers with app:test1 or app:test2 in their container Label. The logical relationship between multiple key-value pairs is OR; any container Label matching any key-value pair will be included in the collection scope. When the container Label allowlist is enabled, Keys must not be duplicated. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    kubernetesRule Property Map
    Kubernetes container collection rules.
    stream String
    Collection information. stdout: Container standard output (stdout). stderr: Container standard error (stderr). all: Both container standard output (stdout) and standard error (stderr).

    HostGroupRuleContainerRuleEnvTag, HostGroupRuleContainerRuleEnvTagArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleExcludeContainerEnvRegex, HostGroupRuleContainerRuleExcludeContainerEnvRegexArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleExcludeContainerLabelRegex, HostGroupRuleContainerRuleExcludeContainerLabelRegexArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleIncludeContainerEnvRegex, HostGroupRuleContainerRuleIncludeContainerEnvRegexArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleIncludeContainerLabelRegex, HostGroupRuleContainerRuleIncludeContainerLabelRegexArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleKubernetesRule, HostGroupRuleContainerRuleKubernetesRuleArgs

    AnnotationTags List<Byteplus.HostGroupRuleContainerRuleKubernetesRuleAnnotationTag>
    Whether to add Kubernetes Annotations as log tags to the raw log data. When enabled, the log service adds Kubernetes Pod Annotation fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to sink and Value to data_sink. If the Pod contains the Annotation sink=ck, the log will include the field tagdata_sink_*: ck. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    EnableAllLabelTag bool
    Whether to add all Kubernetes Labels as log tags to the raw log data. When enabled, the log service adds fields for all Labels in the Kubernetes Pod to the log. For example, if the Pod has Label source=DC and destination=CS, the log will include fields tagsource__: DC and **tag**destination__: CS.
    ExcludePodAnnotationRegexes List<Byteplus.HostGroupRuleContainerRuleKubernetesRuleExcludePodAnnotationRegex>
    Pod Annotation denylist is used to specify containers that are not collected. If you need to set a Pod Annotation denylist, Key is required and Value is optional. If Value is empty, all containers under Pods whose Pod Annotation contains the Key will be excluded. If Value is not empty, only containers under Pods whose Pod Annotation contains the Key and whose value matches the Value will be excluded. By default, Value uses string matching, meaning only when Value and the Pod Annotation value are exactly the same will it match. If the value starts with ^ and ends with $, it is treated as a regular expression match. For example, set Key to app and Value to ^(test1|test2)$ to match containers under Pods whose Pod Annotation contains app:test1 or app:test2. Note: The logical relationship between multiple Key-Value pairs is OR, meaning as long as the Pod Annotation matches any pair, it will be included in the collection scope. When enabling the Pod Annotation denylist, Keys must not be duplicated. For fuzzy regular expression matching, you must add .. For example, ^(http.)$ matches strings that start with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ExcludePodLabelRegexes List<Byteplus.HostGroupRuleContainerRuleKubernetesRuleExcludePodLabelRegex>
    Specify containers to exclude from collection using the Pod Label denylist. If not enabled, all containers are collected. To set a Pod Label denylist, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the Pod Label are excluded from collection. If Value is not empty, only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in the Pod Label. Note: The logical relationship between multiple Key-Value pairs is OR, meaning any Pod Label matching any pair will be excluded from collection. When enabling the Pod Label denylist, Keys must not be duplicated. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches any string starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    IncludePodAnnotationRegexes List<Byteplus.HostGroupRuleContainerRuleKubernetesRuleIncludePodAnnotationRegex>
    Pod Annotation Allowlist specifies which containers to collect. If you need to set a Pod Annotation Allowlist, Key is required and Value is optional. If Value is empty, all containers in Pods with the specified Key in their Pod Annotation are matched. If Value is not empty, only containers in Pods where the Pod Annotation contains the Key and its value matches Value are matched. By default, Value uses string matching, meaning only exact matches between Value and the Pod Annotation value are considered. If Value starts with ^ and ends with $, it uses regex matching. For example, set Key to app and Value to ^(test1|test2)$ to match containers in Pods with Pod Annotation app:test1 or app:test2. Note: Multiple Key-Value pairs use logical OR, so any Pod Annotation matching any pair will be included in the collection scope. When enabling the Pod Annotation Allowlist, Keys must not be duplicated. For regex fuzzy matching, you must add .. For example, ^(http.)$ matches values starting with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    IncludePodLabelRegexes List<Byteplus.HostGroupRuleContainerRuleKubernetesRuleIncludePodLabelRegex>
    Pod label allowlist specifies which containers to collect. If the Pod label allowlist is not enabled, all containers are collected. To set a Pod label allowlist, Key is required. If Value is empty, all containers with the Key in their Pod label are collected. If Value is not empty, only containers with the Key in their Pod label and a Value matching the specified pattern are collected. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their Pod label. Note: The logical relationship between multiple key-value pairs is OR, meaning any matching pair will include the Pod in the collection scope. When the Pod label allowlist is enabled, Keys must be unique. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches strings starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    LabelTags List<Byteplus.HostGroupRuleContainerRuleKubernetesRuleLabelTag>
    Choose whether to add Kubernetes labels as log tags to the original log data. When enabled, the log service adds Kubernetes Pod label fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the Pod contains the label source=DC, the log will include the field tagdata_source_*: DC. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    NamespaceNameRegex string
    Name of the Kubernetes Namespace to be collected. If not specified, all containers are collected. Namespace names support regular expression matching. For example, setting the Namespace name to ^(tcp|udp)$ collects all containers under the tcp and udp namespaces.
    PodNameRegex string
    Pod name is used to specify the Pod(s) to be collected. If the Pod name is not specified, all containers are collected. Pod name supports regex matching. For example, setting the Pod name to ^(http.*)$ collects all containers under Pods whose names start with http.
    WorkloadNameRegex string
    Specify the container to collect by workload name. If no workload name is specified, all containers are collected. Workload names support regular expressions. For example, setting the workload name to ^(http.*)$ collects all containers under workloads starting with http.
    WorkloadType string
    Specify containers to collect by workload type. Only one type can be selected. If no type is specified, containers of all types will be collected. Supported workload types are: Deployment: stateless workload StatefulSet: stateful workload DaemonSet: daemon process Job: job CronJob: scheduled job
    AnnotationTags []HostGroupRuleContainerRuleKubernetesRuleAnnotationTag
    Whether to add Kubernetes Annotations as log tags to the raw log data. When enabled, the log service adds Kubernetes Pod Annotation fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to sink and Value to data_sink. If the Pod contains the Annotation sink=ck, the log will include the field tagdata_sink_*: ck. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    EnableAllLabelTag bool
    Whether to add all Kubernetes Labels as log tags to the raw log data. When enabled, the log service adds fields for all Labels in the Kubernetes Pod to the log. For example, if the Pod has Label source=DC and destination=CS, the log will include fields tagsource__: DC and **tag**destination__: CS.
    ExcludePodAnnotationRegexes []HostGroupRuleContainerRuleKubernetesRuleExcludePodAnnotationRegex
    Pod Annotation denylist is used to specify containers that are not collected. If you need to set a Pod Annotation denylist, Key is required and Value is optional. If Value is empty, all containers under Pods whose Pod Annotation contains the Key will be excluded. If Value is not empty, only containers under Pods whose Pod Annotation contains the Key and whose value matches the Value will be excluded. By default, Value uses string matching, meaning only when Value and the Pod Annotation value are exactly the same will it match. If the value starts with ^ and ends with $, it is treated as a regular expression match. For example, set Key to app and Value to ^(test1|test2)$ to match containers under Pods whose Pod Annotation contains app:test1 or app:test2. Note: The logical relationship between multiple Key-Value pairs is OR, meaning as long as the Pod Annotation matches any pair, it will be included in the collection scope. When enabling the Pod Annotation denylist, Keys must not be duplicated. For fuzzy regular expression matching, you must add .. For example, ^(http.)$ matches strings that start with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    ExcludePodLabelRegexes []HostGroupRuleContainerRuleKubernetesRuleExcludePodLabelRegex
    Specify containers to exclude from collection using the Pod Label denylist. If not enabled, all containers are collected. To set a Pod Label denylist, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the Pod Label are excluded from collection. If Value is not empty, only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in the Pod Label. Note: The logical relationship between multiple Key-Value pairs is OR, meaning any Pod Label matching any pair will be excluded from collection. When enabling the Pod Label denylist, Keys must not be duplicated. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches any string starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    IncludePodAnnotationRegexes []HostGroupRuleContainerRuleKubernetesRuleIncludePodAnnotationRegex
    Pod Annotation Allowlist specifies which containers to collect. If you need to set a Pod Annotation Allowlist, Key is required and Value is optional. If Value is empty, all containers in Pods with the specified Key in their Pod Annotation are matched. If Value is not empty, only containers in Pods where the Pod Annotation contains the Key and its value matches Value are matched. By default, Value uses string matching, meaning only exact matches between Value and the Pod Annotation value are considered. If Value starts with ^ and ends with $, it uses regex matching. For example, set Key to app and Value to ^(test1|test2)$ to match containers in Pods with Pod Annotation app:test1 or app:test2. Note: Multiple Key-Value pairs use logical OR, so any Pod Annotation matching any pair will be included in the collection scope. When enabling the Pod Annotation Allowlist, Keys must not be duplicated. For regex fuzzy matching, you must add .. For example, ^(http.)$ matches values starting with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    IncludePodLabelRegexes []HostGroupRuleContainerRuleKubernetesRuleIncludePodLabelRegex
    Pod label allowlist specifies which containers to collect. If the Pod label allowlist is not enabled, all containers are collected. To set a Pod label allowlist, Key is required. If Value is empty, all containers with the Key in their Pod label are collected. If Value is not empty, only containers with the Key in their Pod label and a Value matching the specified pattern are collected. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their Pod label. Note: The logical relationship between multiple key-value pairs is OR, meaning any matching pair will include the Pod in the collection scope. When the Pod label allowlist is enabled, Keys must be unique. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches strings starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    LabelTags []HostGroupRuleContainerRuleKubernetesRuleLabelTag
    Choose whether to add Kubernetes labels as log tags to the original log data. When enabled, the log service adds Kubernetes Pod label fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the Pod contains the label source=DC, the log will include the field tagdata_source_*: DC. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    NamespaceNameRegex string
    Name of the Kubernetes Namespace to be collected. If not specified, all containers are collected. Namespace names support regular expression matching. For example, setting the Namespace name to ^(tcp|udp)$ collects all containers under the tcp and udp namespaces.
    PodNameRegex string
    Pod name is used to specify the Pod(s) to be collected. If the Pod name is not specified, all containers are collected. Pod name supports regex matching. For example, setting the Pod name to ^(http.*)$ collects all containers under Pods whose names start with http.
    WorkloadNameRegex string
    Specify the container to collect by workload name. If no workload name is specified, all containers are collected. Workload names support regular expressions. For example, setting the workload name to ^(http.*)$ collects all containers under workloads starting with http.
    WorkloadType string
    Specify containers to collect by workload type. Only one type can be selected. If no type is specified, containers of all types will be collected. Supported workload types are: Deployment: stateless workload StatefulSet: stateful workload DaemonSet: daemon process Job: job CronJob: scheduled job
    annotation_tags list(object)
    Whether to add Kubernetes Annotations as log tags to the raw log data. When enabled, the log service adds Kubernetes Pod Annotation fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to sink and Value to data_sink. If the Pod contains the Annotation sink=ck, the log will include the field tagdata_sink_*: ck. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    enable_all_label_tag bool
    Whether to add all Kubernetes Labels as log tags to the raw log data. When enabled, the log service adds fields for all Labels in the Kubernetes Pod to the log. For example, if the Pod has Label source=DC and destination=CS, the log will include fields tagsource__: DC and **tag**destination__: CS.
    exclude_pod_annotation_regexes list(object)
    Pod Annotation denylist is used to specify containers that are not collected. If you need to set a Pod Annotation denylist, Key is required and Value is optional. If Value is empty, all containers under Pods whose Pod Annotation contains the Key will be excluded. If Value is not empty, only containers under Pods whose Pod Annotation contains the Key and whose value matches the Value will be excluded. By default, Value uses string matching, meaning only when Value and the Pod Annotation value are exactly the same will it match. If the value starts with ^ and ends with $, it is treated as a regular expression match. For example, set Key to app and Value to ^(test1|test2)$ to match containers under Pods whose Pod Annotation contains app:test1 or app:test2. Note: The logical relationship between multiple Key-Value pairs is OR, meaning as long as the Pod Annotation matches any pair, it will be included in the collection scope. When enabling the Pod Annotation denylist, Keys must not be duplicated. For fuzzy regular expression matching, you must add .. For example, ^(http.)$ matches strings that start with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    exclude_pod_label_regexes list(object)
    Specify containers to exclude from collection using the Pod Label denylist. If not enabled, all containers are collected. To set a Pod Label denylist, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the Pod Label are excluded from collection. If Value is not empty, only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in the Pod Label. Note: The logical relationship between multiple Key-Value pairs is OR, meaning any Pod Label matching any pair will be excluded from collection. When enabling the Pod Label denylist, Keys must not be duplicated. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches any string starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    include_pod_annotation_regexes list(object)
    Pod Annotation Allowlist specifies which containers to collect. If you need to set a Pod Annotation Allowlist, Key is required and Value is optional. If Value is empty, all containers in Pods with the specified Key in their Pod Annotation are matched. If Value is not empty, only containers in Pods where the Pod Annotation contains the Key and its value matches Value are matched. By default, Value uses string matching, meaning only exact matches between Value and the Pod Annotation value are considered. If Value starts with ^ and ends with $, it uses regex matching. For example, set Key to app and Value to ^(test1|test2)$ to match containers in Pods with Pod Annotation app:test1 or app:test2. Note: Multiple Key-Value pairs use logical OR, so any Pod Annotation matching any pair will be included in the collection scope. When enabling the Pod Annotation Allowlist, Keys must not be duplicated. For regex fuzzy matching, you must add .. For example, ^(http.)$ matches values starting with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    include_pod_label_regexes list(object)
    Pod label allowlist specifies which containers to collect. If the Pod label allowlist is not enabled, all containers are collected. To set a Pod label allowlist, Key is required. If Value is empty, all containers with the Key in their Pod label are collected. If Value is not empty, only containers with the Key in their Pod label and a Value matching the specified pattern are collected. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their Pod label. Note: The logical relationship between multiple key-value pairs is OR, meaning any matching pair will include the Pod in the collection scope. When the Pod label allowlist is enabled, Keys must be unique. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches strings starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    label_tags list(object)
    Choose whether to add Kubernetes labels as log tags to the original log data. When enabled, the log service adds Kubernetes Pod label fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the Pod contains the label source=DC, the log will include the field tagdata_source_*: DC. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    namespace_name_regex string
    Name of the Kubernetes Namespace to be collected. If not specified, all containers are collected. Namespace names support regular expression matching. For example, setting the Namespace name to ^(tcp|udp)$ collects all containers under the tcp and udp namespaces.
    pod_name_regex string
    Pod name is used to specify the Pod(s) to be collected. If the Pod name is not specified, all containers are collected. Pod name supports regex matching. For example, setting the Pod name to ^(http.*)$ collects all containers under Pods whose names start with http.
    workload_name_regex string
    Specify the container to collect by workload name. If no workload name is specified, all containers are collected. Workload names support regular expressions. For example, setting the workload name to ^(http.*)$ collects all containers under workloads starting with http.
    workload_type string
    Specify containers to collect by workload type. Only one type can be selected. If no type is specified, containers of all types will be collected. Supported workload types are: Deployment: stateless workload StatefulSet: stateful workload DaemonSet: daemon process Job: job CronJob: scheduled job
    annotationTags List<HostGroupRuleContainerRuleKubernetesRuleAnnotationTag>
    Whether to add Kubernetes Annotations as log tags to the raw log data. When enabled, the log service adds Kubernetes Pod Annotation fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to sink and Value to data_sink. If the Pod contains the Annotation sink=ck, the log will include the field tagdata_sink_*: ck. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    enableAllLabelTag Boolean
    Whether to add all Kubernetes Labels as log tags to the raw log data. When enabled, the log service adds fields for all Labels in the Kubernetes Pod to the log. For example, if the Pod has Label source=DC and destination=CS, the log will include fields tagsource__: DC and **tag**destination__: CS.
    excludePodAnnotationRegexes List<HostGroupRuleContainerRuleKubernetesRuleExcludePodAnnotationRegex>
    Pod Annotation denylist is used to specify containers that are not collected. If you need to set a Pod Annotation denylist, Key is required and Value is optional. If Value is empty, all containers under Pods whose Pod Annotation contains the Key will be excluded. If Value is not empty, only containers under Pods whose Pod Annotation contains the Key and whose value matches the Value will be excluded. By default, Value uses string matching, meaning only when Value and the Pod Annotation value are exactly the same will it match. If the value starts with ^ and ends with $, it is treated as a regular expression match. For example, set Key to app and Value to ^(test1|test2)$ to match containers under Pods whose Pod Annotation contains app:test1 or app:test2. Note: The logical relationship between multiple Key-Value pairs is OR, meaning as long as the Pod Annotation matches any pair, it will be included in the collection scope. When enabling the Pod Annotation denylist, Keys must not be duplicated. For fuzzy regular expression matching, you must add .. For example, ^(http.)$ matches strings that start with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    excludePodLabelRegexes List<HostGroupRuleContainerRuleKubernetesRuleExcludePodLabelRegex>
    Specify containers to exclude from collection using the Pod Label denylist. If not enabled, all containers are collected. To set a Pod Label denylist, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the Pod Label are excluded from collection. If Value is not empty, only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in the Pod Label. Note: The logical relationship between multiple Key-Value pairs is OR, meaning any Pod Label matching any pair will be excluded from collection. When enabling the Pod Label denylist, Keys must not be duplicated. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches any string starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includePodAnnotationRegexes List<HostGroupRuleContainerRuleKubernetesRuleIncludePodAnnotationRegex>
    Pod Annotation Allowlist specifies which containers to collect. If you need to set a Pod Annotation Allowlist, Key is required and Value is optional. If Value is empty, all containers in Pods with the specified Key in their Pod Annotation are matched. If Value is not empty, only containers in Pods where the Pod Annotation contains the Key and its value matches Value are matched. By default, Value uses string matching, meaning only exact matches between Value and the Pod Annotation value are considered. If Value starts with ^ and ends with $, it uses regex matching. For example, set Key to app and Value to ^(test1|test2)$ to match containers in Pods with Pod Annotation app:test1 or app:test2. Note: Multiple Key-Value pairs use logical OR, so any Pod Annotation matching any pair will be included in the collection scope. When enabling the Pod Annotation Allowlist, Keys must not be duplicated. For regex fuzzy matching, you must add .. For example, ^(http.)$ matches values starting with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includePodLabelRegexes List<HostGroupRuleContainerRuleKubernetesRuleIncludePodLabelRegex>
    Pod label allowlist specifies which containers to collect. If the Pod label allowlist is not enabled, all containers are collected. To set a Pod label allowlist, Key is required. If Value is empty, all containers with the Key in their Pod label are collected. If Value is not empty, only containers with the Key in their Pod label and a Value matching the specified pattern are collected. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their Pod label. Note: The logical relationship between multiple key-value pairs is OR, meaning any matching pair will include the Pod in the collection scope. When the Pod label allowlist is enabled, Keys must be unique. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches strings starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    labelTags List<HostGroupRuleContainerRuleKubernetesRuleLabelTag>
    Choose whether to add Kubernetes labels as log tags to the original log data. When enabled, the log service adds Kubernetes Pod label fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the Pod contains the label source=DC, the log will include the field tagdata_source_*: DC. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    namespaceNameRegex String
    Name of the Kubernetes Namespace to be collected. If not specified, all containers are collected. Namespace names support regular expression matching. For example, setting the Namespace name to ^(tcp|udp)$ collects all containers under the tcp and udp namespaces.
    podNameRegex String
    Pod name is used to specify the Pod(s) to be collected. If the Pod name is not specified, all containers are collected. Pod name supports regex matching. For example, setting the Pod name to ^(http.*)$ collects all containers under Pods whose names start with http.
    workloadNameRegex String
    Specify the container to collect by workload name. If no workload name is specified, all containers are collected. Workload names support regular expressions. For example, setting the workload name to ^(http.*)$ collects all containers under workloads starting with http.
    workloadType String
    Specify containers to collect by workload type. Only one type can be selected. If no type is specified, containers of all types will be collected. Supported workload types are: Deployment: stateless workload StatefulSet: stateful workload DaemonSet: daemon process Job: job CronJob: scheduled job
    annotationTags HostGroupRuleContainerRuleKubernetesRuleAnnotationTag[]
    Whether to add Kubernetes Annotations as log tags to the raw log data. When enabled, the log service adds Kubernetes Pod Annotation fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to sink and Value to data_sink. If the Pod contains the Annotation sink=ck, the log will include the field tagdata_sink_*: ck. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    enableAllLabelTag boolean
    Whether to add all Kubernetes Labels as log tags to the raw log data. When enabled, the log service adds fields for all Labels in the Kubernetes Pod to the log. For example, if the Pod has Label source=DC and destination=CS, the log will include fields tagsource__: DC and **tag**destination__: CS.
    excludePodAnnotationRegexes HostGroupRuleContainerRuleKubernetesRuleExcludePodAnnotationRegex[]
    Pod Annotation denylist is used to specify containers that are not collected. If you need to set a Pod Annotation denylist, Key is required and Value is optional. If Value is empty, all containers under Pods whose Pod Annotation contains the Key will be excluded. If Value is not empty, only containers under Pods whose Pod Annotation contains the Key and whose value matches the Value will be excluded. By default, Value uses string matching, meaning only when Value and the Pod Annotation value are exactly the same will it match. If the value starts with ^ and ends with $, it is treated as a regular expression match. For example, set Key to app and Value to ^(test1|test2)$ to match containers under Pods whose Pod Annotation contains app:test1 or app:test2. Note: The logical relationship between multiple Key-Value pairs is OR, meaning as long as the Pod Annotation matches any pair, it will be included in the collection scope. When enabling the Pod Annotation denylist, Keys must not be duplicated. For fuzzy regular expression matching, you must add .. For example, ^(http.)$ matches strings that start with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    excludePodLabelRegexes HostGroupRuleContainerRuleKubernetesRuleExcludePodLabelRegex[]
    Specify containers to exclude from collection using the Pod Label denylist. If not enabled, all containers are collected. To set a Pod Label denylist, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the Pod Label are excluded from collection. If Value is not empty, only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in the Pod Label. Note: The logical relationship between multiple Key-Value pairs is OR, meaning any Pod Label matching any pair will be excluded from collection. When enabling the Pod Label denylist, Keys must not be duplicated. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches any string starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includePodAnnotationRegexes HostGroupRuleContainerRuleKubernetesRuleIncludePodAnnotationRegex[]
    Pod Annotation Allowlist specifies which containers to collect. If you need to set a Pod Annotation Allowlist, Key is required and Value is optional. If Value is empty, all containers in Pods with the specified Key in their Pod Annotation are matched. If Value is not empty, only containers in Pods where the Pod Annotation contains the Key and its value matches Value are matched. By default, Value uses string matching, meaning only exact matches between Value and the Pod Annotation value are considered. If Value starts with ^ and ends with $, it uses regex matching. For example, set Key to app and Value to ^(test1|test2)$ to match containers in Pods with Pod Annotation app:test1 or app:test2. Note: Multiple Key-Value pairs use logical OR, so any Pod Annotation matching any pair will be included in the collection scope. When enabling the Pod Annotation Allowlist, Keys must not be duplicated. For regex fuzzy matching, you must add .. For example, ^(http.)$ matches values starting with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includePodLabelRegexes HostGroupRuleContainerRuleKubernetesRuleIncludePodLabelRegex[]
    Pod label allowlist specifies which containers to collect. If the Pod label allowlist is not enabled, all containers are collected. To set a Pod label allowlist, Key is required. If Value is empty, all containers with the Key in their Pod label are collected. If Value is not empty, only containers with the Key in their Pod label and a Value matching the specified pattern are collected. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their Pod label. Note: The logical relationship between multiple key-value pairs is OR, meaning any matching pair will include the Pod in the collection scope. When the Pod label allowlist is enabled, Keys must be unique. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches strings starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    labelTags HostGroupRuleContainerRuleKubernetesRuleLabelTag[]
    Choose whether to add Kubernetes labels as log tags to the original log data. When enabled, the log service adds Kubernetes Pod label fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the Pod contains the label source=DC, the log will include the field tagdata_source_*: DC. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    namespaceNameRegex string
    Name of the Kubernetes Namespace to be collected. If not specified, all containers are collected. Namespace names support regular expression matching. For example, setting the Namespace name to ^(tcp|udp)$ collects all containers under the tcp and udp namespaces.
    podNameRegex string
    Pod name is used to specify the Pod(s) to be collected. If the Pod name is not specified, all containers are collected. Pod name supports regex matching. For example, setting the Pod name to ^(http.*)$ collects all containers under Pods whose names start with http.
    workloadNameRegex string
    Specify the container to collect by workload name. If no workload name is specified, all containers are collected. Workload names support regular expressions. For example, setting the workload name to ^(http.*)$ collects all containers under workloads starting with http.
    workloadType string
    Specify containers to collect by workload type. Only one type can be selected. If no type is specified, containers of all types will be collected. Supported workload types are: Deployment: stateless workload StatefulSet: stateful workload DaemonSet: daemon process Job: job CronJob: scheduled job
    annotation_tags Sequence[HostGroupRuleContainerRuleKubernetesRuleAnnotationTag]
    Whether to add Kubernetes Annotations as log tags to the raw log data. When enabled, the log service adds Kubernetes Pod Annotation fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to sink and Value to data_sink. If the Pod contains the Annotation sink=ck, the log will include the field tagdata_sink_*: ck. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    enable_all_label_tag bool
    Whether to add all Kubernetes Labels as log tags to the raw log data. When enabled, the log service adds fields for all Labels in the Kubernetes Pod to the log. For example, if the Pod has Label source=DC and destination=CS, the log will include fields tagsource__: DC and **tag**destination__: CS.
    exclude_pod_annotation_regexes Sequence[HostGroupRuleContainerRuleKubernetesRuleExcludePodAnnotationRegex]
    Pod Annotation denylist is used to specify containers that are not collected. If you need to set a Pod Annotation denylist, Key is required and Value is optional. If Value is empty, all containers under Pods whose Pod Annotation contains the Key will be excluded. If Value is not empty, only containers under Pods whose Pod Annotation contains the Key and whose value matches the Value will be excluded. By default, Value uses string matching, meaning only when Value and the Pod Annotation value are exactly the same will it match. If the value starts with ^ and ends with $, it is treated as a regular expression match. For example, set Key to app and Value to ^(test1|test2)$ to match containers under Pods whose Pod Annotation contains app:test1 or app:test2. Note: The logical relationship between multiple Key-Value pairs is OR, meaning as long as the Pod Annotation matches any pair, it will be included in the collection scope. When enabling the Pod Annotation denylist, Keys must not be duplicated. For fuzzy regular expression matching, you must add .. For example, ^(http.)$ matches strings that start with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    exclude_pod_label_regexes Sequence[HostGroupRuleContainerRuleKubernetesRuleExcludePodLabelRegex]
    Specify containers to exclude from collection using the Pod Label denylist. If not enabled, all containers are collected. To set a Pod Label denylist, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the Pod Label are excluded from collection. If Value is not empty, only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in the Pod Label. Note: The logical relationship between multiple Key-Value pairs is OR, meaning any Pod Label matching any pair will be excluded from collection. When enabling the Pod Label denylist, Keys must not be duplicated. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches any string starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    include_pod_annotation_regexes Sequence[HostGroupRuleContainerRuleKubernetesRuleIncludePodAnnotationRegex]
    Pod Annotation Allowlist specifies which containers to collect. If you need to set a Pod Annotation Allowlist, Key is required and Value is optional. If Value is empty, all containers in Pods with the specified Key in their Pod Annotation are matched. If Value is not empty, only containers in Pods where the Pod Annotation contains the Key and its value matches Value are matched. By default, Value uses string matching, meaning only exact matches between Value and the Pod Annotation value are considered. If Value starts with ^ and ends with $, it uses regex matching. For example, set Key to app and Value to ^(test1|test2)$ to match containers in Pods with Pod Annotation app:test1 or app:test2. Note: Multiple Key-Value pairs use logical OR, so any Pod Annotation matching any pair will be included in the collection scope. When enabling the Pod Annotation Allowlist, Keys must not be duplicated. For regex fuzzy matching, you must add .. For example, ^(http.)$ matches values starting with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    include_pod_label_regexes Sequence[HostGroupRuleContainerRuleKubernetesRuleIncludePodLabelRegex]
    Pod label allowlist specifies which containers to collect. If the Pod label allowlist is not enabled, all containers are collected. To set a Pod label allowlist, Key is required. If Value is empty, all containers with the Key in their Pod label are collected. If Value is not empty, only containers with the Key in their Pod label and a Value matching the specified pattern are collected. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their Pod label. Note: The logical relationship between multiple key-value pairs is OR, meaning any matching pair will include the Pod in the collection scope. When the Pod label allowlist is enabled, Keys must be unique. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches strings starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    label_tags Sequence[HostGroupRuleContainerRuleKubernetesRuleLabelTag]
    Choose whether to add Kubernetes labels as log tags to the original log data. When enabled, the log service adds Kubernetes Pod label fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the Pod contains the label source=DC, the log will include the field tagdata_source_*: DC. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    namespace_name_regex str
    Name of the Kubernetes Namespace to be collected. If not specified, all containers are collected. Namespace names support regular expression matching. For example, setting the Namespace name to ^(tcp|udp)$ collects all containers under the tcp and udp namespaces.
    pod_name_regex str
    Pod name is used to specify the Pod(s) to be collected. If the Pod name is not specified, all containers are collected. Pod name supports regex matching. For example, setting the Pod name to ^(http.*)$ collects all containers under Pods whose names start with http.
    workload_name_regex str
    Specify the container to collect by workload name. If no workload name is specified, all containers are collected. Workload names support regular expressions. For example, setting the workload name to ^(http.*)$ collects all containers under workloads starting with http.
    workload_type str
    Specify containers to collect by workload type. Only one type can be selected. If no type is specified, containers of all types will be collected. Supported workload types are: Deployment: stateless workload StatefulSet: stateful workload DaemonSet: daemon process Job: job CronJob: scheduled job
    annotationTags List<Property Map>
    Whether to add Kubernetes Annotations as log tags to the raw log data. When enabled, the log service adds Kubernetes Pod Annotation fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to sink and Value to data_sink. If the Pod contains the Annotation sink=ck, the log will include the field tagdata_sink_*: ck. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    enableAllLabelTag Boolean
    Whether to add all Kubernetes Labels as log tags to the raw log data. When enabled, the log service adds fields for all Labels in the Kubernetes Pod to the log. For example, if the Pod has Label source=DC and destination=CS, the log will include fields tagsource__: DC and **tag**destination__: CS.
    excludePodAnnotationRegexes List<Property Map>
    Pod Annotation denylist is used to specify containers that are not collected. If you need to set a Pod Annotation denylist, Key is required and Value is optional. If Value is empty, all containers under Pods whose Pod Annotation contains the Key will be excluded. If Value is not empty, only containers under Pods whose Pod Annotation contains the Key and whose value matches the Value will be excluded. By default, Value uses string matching, meaning only when Value and the Pod Annotation value are exactly the same will it match. If the value starts with ^ and ends with $, it is treated as a regular expression match. For example, set Key to app and Value to ^(test1|test2)$ to match containers under Pods whose Pod Annotation contains app:test1 or app:test2. Note: The logical relationship between multiple Key-Value pairs is OR, meaning as long as the Pod Annotation matches any pair, it will be included in the collection scope. When enabling the Pod Annotation denylist, Keys must not be duplicated. For fuzzy regular expression matching, you must add .. For example, ^(http.)$ matches strings that start with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    excludePodLabelRegexes List<Property Map>
    Specify containers to exclude from collection using the Pod Label denylist. If not enabled, all containers are collected. To set a Pod Label denylist, Key is required and Value is optional. If Value is empty, all containers with the specified Key in the Pod Label are excluded from collection. If Value is not empty, only containers with the specified Key and a Value matching the pattern are excluded. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in the Pod Label. Note: The logical relationship between multiple Key-Value pairs is OR, meaning any Pod Label matching any pair will be excluded from collection. When enabling the Pod Label denylist, Keys must not be duplicated. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches any string starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includePodAnnotationRegexes List<Property Map>
    Pod Annotation Allowlist specifies which containers to collect. If you need to set a Pod Annotation Allowlist, Key is required and Value is optional. If Value is empty, all containers in Pods with the specified Key in their Pod Annotation are matched. If Value is not empty, only containers in Pods where the Pod Annotation contains the Key and its value matches Value are matched. By default, Value uses string matching, meaning only exact matches between Value and the Pod Annotation value are considered. If Value starts with ^ and ends with $, it uses regex matching. For example, set Key to app and Value to ^(test1|test2)$ to match containers in Pods with Pod Annotation app:test1 or app:test2. Note: Multiple Key-Value pairs use logical OR, so any Pod Annotation matching any pair will be included in the collection scope. When enabling the Pod Annotation Allowlist, Keys must not be duplicated. For regex fuzzy matching, you must add .. For example, ^(http.)$ matches values starting with http Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    includePodLabelRegexes List<Property Map>
    Pod label allowlist specifies which containers to collect. If the Pod label allowlist is not enabled, all containers are collected. To set a Pod label allowlist, Key is required. If Value is empty, all containers with the Key in their Pod label are collected. If Value is not empty, only containers with the Key in their Pod label and a Value matching the specified pattern are collected. Value supports regex matching. For example, set Key to module and Value to ^(tcp|udp)$ to collect only containers with module:tcp or module:udp in their Pod label. Note: The logical relationship between multiple key-value pairs is OR, meaning any matching pair will include the Pod in the collection scope. When the Pod label allowlist is enabled, Keys must be unique. For fuzzy regex matching, you must add .. For example, ^(http.)$ matches strings starting with http. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    labelTags List<Property Map>
    Choose whether to add Kubernetes labels as log tags to the original log data. When enabled, the log service adds Kubernetes Pod label fields to the logs. Setting multiple key-value pairs adds multiple fields. For example, set Key to source and Value to data_source. If the Pod contains the label source=DC, the log will include the field tagdata_source_*: DC. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    namespaceNameRegex String
    Name of the Kubernetes Namespace to be collected. If not specified, all containers are collected. Namespace names support regular expression matching. For example, setting the Namespace name to ^(tcp|udp)$ collects all containers under the tcp and udp namespaces.
    podNameRegex String
    Pod name is used to specify the Pod(s) to be collected. If the Pod name is not specified, all containers are collected. Pod name supports regex matching. For example, setting the Pod name to ^(http.*)$ collects all containers under Pods whose names start with http.
    workloadNameRegex String
    Specify the container to collect by workload name. If no workload name is specified, all containers are collected. Workload names support regular expressions. For example, setting the workload name to ^(http.*)$ collects all containers under workloads starting with http.
    workloadType String
    Specify containers to collect by workload type. Only one type can be selected. If no type is specified, containers of all types will be collected. Supported workload types are: Deployment: stateless workload StatefulSet: stateful workload DaemonSet: daemon process Job: job CronJob: scheduled job

    HostGroupRuleContainerRuleKubernetesRuleAnnotationTag, HostGroupRuleContainerRuleKubernetesRuleAnnotationTagArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleKubernetesRuleExcludePodAnnotationRegex, HostGroupRuleContainerRuleKubernetesRuleExcludePodAnnotationRegexArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleKubernetesRuleExcludePodLabelRegex, HostGroupRuleContainerRuleKubernetesRuleExcludePodLabelRegexArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleKubernetesRuleIncludePodAnnotationRegex, HostGroupRuleContainerRuleKubernetesRuleIncludePodAnnotationRegexArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleKubernetesRuleIncludePodLabelRegex, HostGroupRuleContainerRuleKubernetesRuleIncludePodLabelRegexArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleContainerRuleKubernetesRuleLabelTag, HostGroupRuleContainerRuleKubernetesRuleLabelTagArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleExcludePath, HostGroupRuleExcludePathArgs

    Type string
    Collection path type. File: file name. Path: directory.
    Value string
    Collection path. Must be specified as an absolute path. When Type is Path, Value indicates a directory. When Type is File, Value indicates a file name.
    Type string
    Collection path type. File: file name. Path: directory.
    Value string
    Collection path. Must be specified as an absolute path. When Type is Path, Value indicates a directory. When Type is File, Value indicates a file name.
    type string
    Collection path type. File: file name. Path: directory.
    value string
    Collection path. Must be specified as an absolute path. When Type is Path, Value indicates a directory. When Type is File, Value indicates a file name.
    type String
    Collection path type. File: file name. Path: directory.
    value String
    Collection path. Must be specified as an absolute path. When Type is Path, Value indicates a directory. When Type is File, Value indicates a file name.
    type string
    Collection path type. File: file name. Path: directory.
    value string
    Collection path. Must be specified as an absolute path. When Type is Path, Value indicates a directory. When Type is File, Value indicates a file name.
    type str
    Collection path type. File: file name. Path: directory.
    value str
    Collection path. Must be specified as an absolute path. When Type is Path, Value indicates a directory. When Type is File, Value indicates a file name.
    type String
    Collection path type. File: file name. Path: directory.
    value String
    Collection path. Must be specified as an absolute path. When Type is Path, Value indicates a directory. When Type is File, Value indicates a file name.

    HostGroupRuleExtractRule, HostGroupRuleExtractRuleArgs

    BeginRegex string
    The regex pattern required to match the first line of the log. This is valid only when LogType is multilinelog or fullregexlog. The pattern must be a valid regular expression.
    Delimiter string
    Log delimiter. Valid only when LogType is delimiter_log.
    EnableNanosecond bool
    Enable nanosecond precision time. When enabled, log time parsing will report time with nanosecond precision. true: Enable nanosecond precision time. false: Disable nanosecond precision time.
    FilterKeyRegexes List<Byteplus.HostGroupRuleExtractRuleFilterKeyRegex>
    Filter rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    Keys List<string>
    List of log field names (Keys).
    LogRegex string
    The entire log entry must match the regular expression. This is only valid when the log type is fullregex_log. The regular expression must be valid.
    LogTemplate Byteplus.HostGroupRuleExtractRuleLogTemplate
    Automatically extract log fields based on the specified log template.
    Quote string
    Quotation mark. Content enclosed by quotation marks is parsed as a complete field and not separated. Only valid when LogType is delimiter_log.
    TimeExtractRegex string
    Regular expression for extracting time, used to extract the time value from the TimeKey field and parse it as the collection time.
    TimeFormat string
    Parsing format for the time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    TimeKey string
    Field name for the log time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    TimeSample string
    Sample time. Used to verify whether the specified time parsing format is correct.
    TimeZone string
    Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC.
    UnMatchLogKey string
    Key name for logs that failed to parse when uploading
    UnMatchUpLoadSwitch bool
    Upload logs that failed to parse. UnMatchUpLoadSwitch=true and UnMatchLogKey must be used together. true: Upload logs that failed to parse. false: Do not upload logs that failed to parse.
    BeginRegex string
    The regex pattern required to match the first line of the log. This is valid only when LogType is multilinelog or fullregexlog. The pattern must be a valid regular expression.
    Delimiter string
    Log delimiter. Valid only when LogType is delimiter_log.
    EnableNanosecond bool
    Enable nanosecond precision time. When enabled, log time parsing will report time with nanosecond precision. true: Enable nanosecond precision time. false: Disable nanosecond precision time.
    FilterKeyRegexes []HostGroupRuleExtractRuleFilterKeyRegex
    Filter rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    Keys []string
    List of log field names (Keys).
    LogRegex string
    The entire log entry must match the regular expression. This is only valid when the log type is fullregex_log. The regular expression must be valid.
    LogTemplate HostGroupRuleExtractRuleLogTemplate
    Automatically extract log fields based on the specified log template.
    Quote string
    Quotation mark. Content enclosed by quotation marks is parsed as a complete field and not separated. Only valid when LogType is delimiter_log.
    TimeExtractRegex string
    Regular expression for extracting time, used to extract the time value from the TimeKey field and parse it as the collection time.
    TimeFormat string
    Parsing format for the time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    TimeKey string
    Field name for the log time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    TimeSample string
    Sample time. Used to verify whether the specified time parsing format is correct.
    TimeZone string
    Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC.
    UnMatchLogKey string
    Key name for logs that failed to parse when uploading
    UnMatchUpLoadSwitch bool
    Upload logs that failed to parse. UnMatchUpLoadSwitch=true and UnMatchLogKey must be used together. true: Upload logs that failed to parse. false: Do not upload logs that failed to parse.
    begin_regex string
    The regex pattern required to match the first line of the log. This is valid only when LogType is multilinelog or fullregexlog. The pattern must be a valid regular expression.
    delimiter string
    Log delimiter. Valid only when LogType is delimiter_log.
    enable_nanosecond bool
    Enable nanosecond precision time. When enabled, log time parsing will report time with nanosecond precision. true: Enable nanosecond precision time. false: Disable nanosecond precision time.
    filter_key_regexes list(object)
    Filter rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    keys list(string)
    List of log field names (Keys).
    log_regex string
    The entire log entry must match the regular expression. This is only valid when the log type is fullregex_log. The regular expression must be valid.
    log_template object
    Automatically extract log fields based on the specified log template.
    quote string
    Quotation mark. Content enclosed by quotation marks is parsed as a complete field and not separated. Only valid when LogType is delimiter_log.
    time_extract_regex string
    Regular expression for extracting time, used to extract the time value from the TimeKey field and parse it as the collection time.
    time_format string
    Parsing format for the time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    time_key string
    Field name for the log time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    time_sample string
    Sample time. Used to verify whether the specified time parsing format is correct.
    time_zone string
    Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC.
    un_match_log_key string
    Key name for logs that failed to parse when uploading
    un_match_up_load_switch bool
    Upload logs that failed to parse. UnMatchUpLoadSwitch=true and UnMatchLogKey must be used together. true: Upload logs that failed to parse. false: Do not upload logs that failed to parse.
    beginRegex String
    The regex pattern required to match the first line of the log. This is valid only when LogType is multilinelog or fullregexlog. The pattern must be a valid regular expression.
    delimiter String
    Log delimiter. Valid only when LogType is delimiter_log.
    enableNanosecond Boolean
    Enable nanosecond precision time. When enabled, log time parsing will report time with nanosecond precision. true: Enable nanosecond precision time. false: Disable nanosecond precision time.
    filterKeyRegexes List<HostGroupRuleExtractRuleFilterKeyRegex>
    Filter rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    keys List<String>
    List of log field names (Keys).
    logRegex String
    The entire log entry must match the regular expression. This is only valid when the log type is fullregex_log. The regular expression must be valid.
    logTemplate HostGroupRuleExtractRuleLogTemplate
    Automatically extract log fields based on the specified log template.
    quote String
    Quotation mark. Content enclosed by quotation marks is parsed as a complete field and not separated. Only valid when LogType is delimiter_log.
    timeExtractRegex String
    Regular expression for extracting time, used to extract the time value from the TimeKey field and parse it as the collection time.
    timeFormat String
    Parsing format for the time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    timeKey String
    Field name for the log time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    timeSample String
    Sample time. Used to verify whether the specified time parsing format is correct.
    timeZone String
    Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC.
    unMatchLogKey String
    Key name for logs that failed to parse when uploading
    unMatchUpLoadSwitch Boolean
    Upload logs that failed to parse. UnMatchUpLoadSwitch=true and UnMatchLogKey must be used together. true: Upload logs that failed to parse. false: Do not upload logs that failed to parse.
    beginRegex string
    The regex pattern required to match the first line of the log. This is valid only when LogType is multilinelog or fullregexlog. The pattern must be a valid regular expression.
    delimiter string
    Log delimiter. Valid only when LogType is delimiter_log.
    enableNanosecond boolean
    Enable nanosecond precision time. When enabled, log time parsing will report time with nanosecond precision. true: Enable nanosecond precision time. false: Disable nanosecond precision time.
    filterKeyRegexes HostGroupRuleExtractRuleFilterKeyRegex[]
    Filter rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    keys string[]
    List of log field names (Keys).
    logRegex string
    The entire log entry must match the regular expression. This is only valid when the log type is fullregex_log. The regular expression must be valid.
    logTemplate HostGroupRuleExtractRuleLogTemplate
    Automatically extract log fields based on the specified log template.
    quote string
    Quotation mark. Content enclosed by quotation marks is parsed as a complete field and not separated. Only valid when LogType is delimiter_log.
    timeExtractRegex string
    Regular expression for extracting time, used to extract the time value from the TimeKey field and parse it as the collection time.
    timeFormat string
    Parsing format for the time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    timeKey string
    Field name for the log time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    timeSample string
    Sample time. Used to verify whether the specified time parsing format is correct.
    timeZone string
    Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC.
    unMatchLogKey string
    Key name for logs that failed to parse when uploading
    unMatchUpLoadSwitch boolean
    Upload logs that failed to parse. UnMatchUpLoadSwitch=true and UnMatchLogKey must be used together. true: Upload logs that failed to parse. false: Do not upload logs that failed to parse.
    begin_regex str
    The regex pattern required to match the first line of the log. This is valid only when LogType is multilinelog or fullregexlog. The pattern must be a valid regular expression.
    delimiter str
    Log delimiter. Valid only when LogType is delimiter_log.
    enable_nanosecond bool
    Enable nanosecond precision time. When enabled, log time parsing will report time with nanosecond precision. true: Enable nanosecond precision time. false: Disable nanosecond precision time.
    filter_key_regexes Sequence[HostGroupRuleExtractRuleFilterKeyRegex]
    Filter rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    keys Sequence[str]
    List of log field names (Keys).
    log_regex str
    The entire log entry must match the regular expression. This is only valid when the log type is fullregex_log. The regular expression must be valid.
    log_template HostGroupRuleExtractRuleLogTemplate
    Automatically extract log fields based on the specified log template.
    quote str
    Quotation mark. Content enclosed by quotation marks is parsed as a complete field and not separated. Only valid when LogType is delimiter_log.
    time_extract_regex str
    Regular expression for extracting time, used to extract the time value from the TimeKey field and parse it as the collection time.
    time_format str
    Parsing format for the time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    time_key str
    Field name for the log time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    time_sample str
    Sample time. Used to verify whether the specified time parsing format is correct.
    time_zone str
    Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC.
    un_match_log_key str
    Key name for logs that failed to parse when uploading
    un_match_up_load_switch bool
    Upload logs that failed to parse. UnMatchUpLoadSwitch=true and UnMatchLogKey must be used together. true: Upload logs that failed to parse. false: Do not upload logs that failed to parse.
    beginRegex String
    The regex pattern required to match the first line of the log. This is valid only when LogType is multilinelog or fullregexlog. The pattern must be a valid regular expression.
    delimiter String
    Log delimiter. Valid only when LogType is delimiter_log.
    enableNanosecond Boolean
    Enable nanosecond precision time. When enabled, log time parsing will report time with nanosecond precision. true: Enable nanosecond precision time. false: Disable nanosecond precision time.
    filterKeyRegexes List<Property Map>
    Filter rule list. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    keys List<String>
    List of log field names (Keys).
    logRegex String
    The entire log entry must match the regular expression. This is only valid when the log type is fullregex_log. The regular expression must be valid.
    logTemplate Property Map
    Automatically extract log fields based on the specified log template.
    quote String
    Quotation mark. Content enclosed by quotation marks is parsed as a complete field and not separated. Only valid when LogType is delimiter_log.
    timeExtractRegex String
    Regular expression for extracting time, used to extract the time value from the TimeKey field and parse it as the collection time.
    timeFormat String
    Parsing format for the time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    timeKey String
    Field name for the log time field. If a specified time field in the log is used as the log timestamp, you must provide TimeKey and TimeFormat.
    timeSample String
    Sample time. Used to verify whether the specified time parsing format is correct.
    timeZone String
    Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC.
    unMatchLogKey String
    Key name for logs that failed to parse when uploading
    unMatchUpLoadSwitch Boolean
    Upload logs that failed to parse. UnMatchUpLoadSwitch=true and UnMatchLogKey must be used together. true: Upload logs that failed to parse. false: Do not upload logs that failed to parse.

    HostGroupRuleExtractRuleFilterKeyRegex, HostGroupRuleExtractRuleFilterKeyRegexArgs

    Key string
    Name of the filter field.
    Regex string
    The log content of the filter field must match the specified regular expression.
    Key string
    Name of the filter field.
    Regex string
    The log content of the filter field must match the specified regular expression.
    key string
    Name of the filter field.
    regex string
    The log content of the filter field must match the specified regular expression.
    key String
    Name of the filter field.
    regex String
    The log content of the filter field must match the specified regular expression.
    key string
    Name of the filter field.
    regex string
    The log content of the filter field must match the specified regular expression.
    key str
    Name of the filter field.
    regex str
    The log content of the filter field must match the specified regular expression.
    key String
    Name of the filter field.
    regex String
    The log content of the filter field must match the specified regular expression.

    HostGroupRuleExtractRuleLogTemplate, HostGroupRuleExtractRuleLogTemplateArgs

    Format string
    Log template format
    Type string
    Log template type. Supported types: Nginx (Nginx log template type).
    Format string
    Log template format
    Type string
    Log template type. Supported types: Nginx (Nginx log template type).
    format string
    Log template format
    type string
    Log template type. Supported types: Nginx (Nginx log template type).
    format String
    Log template format
    type String
    Log template type. Supported types: Nginx (Nginx log template type).
    format string
    Log template format
    type string
    Log template type. Supported types: Nginx (Nginx log template type).
    format str
    Log template format
    type str
    Log template type. Supported types: Nginx (Nginx log template type).
    format String
    Log template format
    type String
    Log template type. Supported types: Nginx (Nginx log template type).

    HostGroupRuleUserDefineRule, HostGroupRuleUserDefineRuleArgs

    Advanced Byteplus.HostGroupRuleUserDefineRuleAdvanced
    Advanced parameters are used for extended configuration. After enabling extended configuration, you can customize advanced behaviors of LogCollector, such as when to release file handles. Note: If multiple conditions for releasing handles are specified, the handle will be released and log file monitoring will end as soon as any condition is met.
    EnableHostGroupLabel bool
    Whether to upload the Label information of the host group to the log service. Disabled by default. true: LogCollector uploads the Label information of the host group to the specified field. You can specify the field name in the HostGroupLabelKey parameter. false (default): LogCollector does not upload the Label information of the host group.
    EnableHostname bool
    Whether to upload the hostname field. Default is disabled. true: Adds a field to the original log to record the log source's hostname. Specify the hostname field name using HostnameKey. false (default): Does not add the hostname field.
    EnableRawLog bool
    Whether to upload raw logs. true: Upload raw logs. false (default): Do not upload raw logs.
    Fields List<Byteplus.HostGroupRuleUserDefineRuleField>
    Add constant fields to logs. Constant fields must follow these restrictions: Up to 5 constant fields can be uploaded. Field name (Key) must be unique and not empty. Length: 1–128 characters, including letters, numbers, and special characters (-*./), and cannot start with an underscore. Field value (Value) must not be empty, maximum length is 512 KiB. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    HostGroupLabelKey string
    Field name used to store machine group label information.
    HostnameKey string
    hostname field name. Only required when EnableHostname is set to true.
    IgnoreOlder int
    Ignore log files that have not been updated for a specified duration, in hours.
    MultiCollectsType string
    Allows multiple log file collections. Empty: Uses the log file ID (including file inode, device, and checksum of the first N bytes) to uniquely identify the log file. RuleID: Uses the collection rule ID and log file ID to uniquely identify the log file. TopicIDRuleName: Uses the log topic ID, collection rule Name, and log file ID to uniquely identify the log file.
    ParsePathRule Byteplus.HostGroupRuleUserDefineRuleParsePathRule
    Rules for parsing the collection path. After setting the rule, fields in the collection path are extracted using the specified regex and added as metadata to the log data. Note: This parameter is not supported when collecting container standard output.
    Plugin Byteplus.HostGroupRuleUserDefineRulePlugin
    LogCollector plugin configuration. After enabling plugin configuration, you can add one or more LogCollector processor plugins to parse logs with complex or variable structures.
    RawLogKey string
    Original log field name. Only effective when EnableRawLog is set to true. RawLogKey defaults to raw, meaning the original log data will be encapsulated in the raw field and uploaded to the log service together with the parsed log data
    ShardHashKey Byteplus.HostGroupRuleUserDefineRuleShardHashKey
    Rules for routing log partitions. If this parameter is not set, logs are written using the default load balancing mode, and packets are written to any available Shard. If set, logs are collected using the HashKey routing Shard mode, and the log service writes data to the Shard containing the specified Key value.
    TailFiles bool
    LogCollector collection strategy, specifying whether LogCollector collects incremental logs or full logs. The default is false, which means full log collection. true: incremental collection. When LogCollector collects logs, it only collects newly added content in the file. When a monitored log file receives new log entries, LogCollector is triggered to collect logs. For log files being collected for the first time, LogCollector automatically determines the collection position based on the incremental threshold TailSizeKb you specify. If the new file size does not exceed the incremental threshold, collection starts from the beginning of the new file. If the new file size exceeds the incremental threshold, collection starts from the position at the end of the file minus the incremental threshold, meaning only incremental logs are collected. For log files that are not being collected for the first time, LogCollector determines the collection position based on the Checkpoint and continues collecting. false: (default) full collection. LogCollector collects logs from the beginning of each file, including historical log data.
    TailSizeKb int
    Incremental collection backtracking threshold, in KiB. When LogCollector uses incremental collection, for the first collection of a log file: if the new log file size does not exceed the TailSizeKb value, collection starts from the beginning of the file. If the new log file size exceeds the TailSizeKb value, collection starts from the position TailSizeKb from the end of the file.
    Advanced HostGroupRuleUserDefineRuleAdvanced
    Advanced parameters are used for extended configuration. After enabling extended configuration, you can customize advanced behaviors of LogCollector, such as when to release file handles. Note: If multiple conditions for releasing handles are specified, the handle will be released and log file monitoring will end as soon as any condition is met.
    EnableHostGroupLabel bool
    Whether to upload the Label information of the host group to the log service. Disabled by default. true: LogCollector uploads the Label information of the host group to the specified field. You can specify the field name in the HostGroupLabelKey parameter. false (default): LogCollector does not upload the Label information of the host group.
    EnableHostname bool
    Whether to upload the hostname field. Default is disabled. true: Adds a field to the original log to record the log source's hostname. Specify the hostname field name using HostnameKey. false (default): Does not add the hostname field.
    EnableRawLog bool
    Whether to upload raw logs. true: Upload raw logs. false (default): Do not upload raw logs.
    Fields []HostGroupRuleUserDefineRuleField
    Add constant fields to logs. Constant fields must follow these restrictions: Up to 5 constant fields can be uploaded. Field name (Key) must be unique and not empty. Length: 1–128 characters, including letters, numbers, and special characters (-*./), and cannot start with an underscore. Field value (Value) must not be empty, maximum length is 512 KiB. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    HostGroupLabelKey string
    Field name used to store machine group label information.
    HostnameKey string
    hostname field name. Only required when EnableHostname is set to true.
    IgnoreOlder int
    Ignore log files that have not been updated for a specified duration, in hours.
    MultiCollectsType string
    Allows multiple log file collections. Empty: Uses the log file ID (including file inode, device, and checksum of the first N bytes) to uniquely identify the log file. RuleID: Uses the collection rule ID and log file ID to uniquely identify the log file. TopicIDRuleName: Uses the log topic ID, collection rule Name, and log file ID to uniquely identify the log file.
    ParsePathRule HostGroupRuleUserDefineRuleParsePathRule
    Rules for parsing the collection path. After setting the rule, fields in the collection path are extracted using the specified regex and added as metadata to the log data. Note: This parameter is not supported when collecting container standard output.
    Plugin HostGroupRuleUserDefineRulePlugin
    LogCollector plugin configuration. After enabling plugin configuration, you can add one or more LogCollector processor plugins to parse logs with complex or variable structures.
    RawLogKey string
    Original log field name. Only effective when EnableRawLog is set to true. RawLogKey defaults to raw, meaning the original log data will be encapsulated in the raw field and uploaded to the log service together with the parsed log data
    ShardHashKey HostGroupRuleUserDefineRuleShardHashKey
    Rules for routing log partitions. If this parameter is not set, logs are written using the default load balancing mode, and packets are written to any available Shard. If set, logs are collected using the HashKey routing Shard mode, and the log service writes data to the Shard containing the specified Key value.
    TailFiles bool
    LogCollector collection strategy, specifying whether LogCollector collects incremental logs or full logs. The default is false, which means full log collection. true: incremental collection. When LogCollector collects logs, it only collects newly added content in the file. When a monitored log file receives new log entries, LogCollector is triggered to collect logs. For log files being collected for the first time, LogCollector automatically determines the collection position based on the incremental threshold TailSizeKb you specify. If the new file size does not exceed the incremental threshold, collection starts from the beginning of the new file. If the new file size exceeds the incremental threshold, collection starts from the position at the end of the file minus the incremental threshold, meaning only incremental logs are collected. For log files that are not being collected for the first time, LogCollector determines the collection position based on the Checkpoint and continues collecting. false: (default) full collection. LogCollector collects logs from the beginning of each file, including historical log data.
    TailSizeKb int
    Incremental collection backtracking threshold, in KiB. When LogCollector uses incremental collection, for the first collection of a log file: if the new log file size does not exceed the TailSizeKb value, collection starts from the beginning of the file. If the new log file size exceeds the TailSizeKb value, collection starts from the position TailSizeKb from the end of the file.
    advanced object
    Advanced parameters are used for extended configuration. After enabling extended configuration, you can customize advanced behaviors of LogCollector, such as when to release file handles. Note: If multiple conditions for releasing handles are specified, the handle will be released and log file monitoring will end as soon as any condition is met.
    enable_host_group_label bool
    Whether to upload the Label information of the host group to the log service. Disabled by default. true: LogCollector uploads the Label information of the host group to the specified field. You can specify the field name in the HostGroupLabelKey parameter. false (default): LogCollector does not upload the Label information of the host group.
    enable_hostname bool
    Whether to upload the hostname field. Default is disabled. true: Adds a field to the original log to record the log source's hostname. Specify the hostname field name using HostnameKey. false (default): Does not add the hostname field.
    enable_raw_log bool
    Whether to upload raw logs. true: Upload raw logs. false (default): Do not upload raw logs.
    fields list(object)
    Add constant fields to logs. Constant fields must follow these restrictions: Up to 5 constant fields can be uploaded. Field name (Key) must be unique and not empty. Length: 1–128 characters, including letters, numbers, and special characters (-*./), and cannot start with an underscore. Field value (Value) must not be empty, maximum length is 512 KiB. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    host_group_label_key string
    Field name used to store machine group label information.
    hostname_key string
    hostname field name. Only required when EnableHostname is set to true.
    ignore_older number
    Ignore log files that have not been updated for a specified duration, in hours.
    multi_collects_type string
    Allows multiple log file collections. Empty: Uses the log file ID (including file inode, device, and checksum of the first N bytes) to uniquely identify the log file. RuleID: Uses the collection rule ID and log file ID to uniquely identify the log file. TopicIDRuleName: Uses the log topic ID, collection rule Name, and log file ID to uniquely identify the log file.
    parse_path_rule object
    Rules for parsing the collection path. After setting the rule, fields in the collection path are extracted using the specified regex and added as metadata to the log data. Note: This parameter is not supported when collecting container standard output.
    plugin object
    LogCollector plugin configuration. After enabling plugin configuration, you can add one or more LogCollector processor plugins to parse logs with complex or variable structures.
    raw_log_key string
    Original log field name. Only effective when EnableRawLog is set to true. RawLogKey defaults to raw, meaning the original log data will be encapsulated in the raw field and uploaded to the log service together with the parsed log data
    shard_hash_key object
    Rules for routing log partitions. If this parameter is not set, logs are written using the default load balancing mode, and packets are written to any available Shard. If set, logs are collected using the HashKey routing Shard mode, and the log service writes data to the Shard containing the specified Key value.
    tail_files bool
    LogCollector collection strategy, specifying whether LogCollector collects incremental logs or full logs. The default is false, which means full log collection. true: incremental collection. When LogCollector collects logs, it only collects newly added content in the file. When a monitored log file receives new log entries, LogCollector is triggered to collect logs. For log files being collected for the first time, LogCollector automatically determines the collection position based on the incremental threshold TailSizeKb you specify. If the new file size does not exceed the incremental threshold, collection starts from the beginning of the new file. If the new file size exceeds the incremental threshold, collection starts from the position at the end of the file minus the incremental threshold, meaning only incremental logs are collected. For log files that are not being collected for the first time, LogCollector determines the collection position based on the Checkpoint and continues collecting. false: (default) full collection. LogCollector collects logs from the beginning of each file, including historical log data.
    tail_size_kb number
    Incremental collection backtracking threshold, in KiB. When LogCollector uses incremental collection, for the first collection of a log file: if the new log file size does not exceed the TailSizeKb value, collection starts from the beginning of the file. If the new log file size exceeds the TailSizeKb value, collection starts from the position TailSizeKb from the end of the file.
    advanced HostGroupRuleUserDefineRuleAdvanced
    Advanced parameters are used for extended configuration. After enabling extended configuration, you can customize advanced behaviors of LogCollector, such as when to release file handles. Note: If multiple conditions for releasing handles are specified, the handle will be released and log file monitoring will end as soon as any condition is met.
    enableHostGroupLabel Boolean
    Whether to upload the Label information of the host group to the log service. Disabled by default. true: LogCollector uploads the Label information of the host group to the specified field. You can specify the field name in the HostGroupLabelKey parameter. false (default): LogCollector does not upload the Label information of the host group.
    enableHostname Boolean
    Whether to upload the hostname field. Default is disabled. true: Adds a field to the original log to record the log source's hostname. Specify the hostname field name using HostnameKey. false (default): Does not add the hostname field.
    enableRawLog Boolean
    Whether to upload raw logs. true: Upload raw logs. false (default): Do not upload raw logs.
    fields List<HostGroupRuleUserDefineRuleField>
    Add constant fields to logs. Constant fields must follow these restrictions: Up to 5 constant fields can be uploaded. Field name (Key) must be unique and not empty. Length: 1–128 characters, including letters, numbers, and special characters (-*./), and cannot start with an underscore. Field value (Value) must not be empty, maximum length is 512 KiB. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    hostGroupLabelKey String
    Field name used to store machine group label information.
    hostnameKey String
    hostname field name. Only required when EnableHostname is set to true.
    ignoreOlder Integer
    Ignore log files that have not been updated for a specified duration, in hours.
    multiCollectsType String
    Allows multiple log file collections. Empty: Uses the log file ID (including file inode, device, and checksum of the first N bytes) to uniquely identify the log file. RuleID: Uses the collection rule ID and log file ID to uniquely identify the log file. TopicIDRuleName: Uses the log topic ID, collection rule Name, and log file ID to uniquely identify the log file.
    parsePathRule HostGroupRuleUserDefineRuleParsePathRule
    Rules for parsing the collection path. After setting the rule, fields in the collection path are extracted using the specified regex and added as metadata to the log data. Note: This parameter is not supported when collecting container standard output.
    plugin HostGroupRuleUserDefineRulePlugin
    LogCollector plugin configuration. After enabling plugin configuration, you can add one or more LogCollector processor plugins to parse logs with complex or variable structures.
    rawLogKey String
    Original log field name. Only effective when EnableRawLog is set to true. RawLogKey defaults to raw, meaning the original log data will be encapsulated in the raw field and uploaded to the log service together with the parsed log data
    shardHashKey HostGroupRuleUserDefineRuleShardHashKey
    Rules for routing log partitions. If this parameter is not set, logs are written using the default load balancing mode, and packets are written to any available Shard. If set, logs are collected using the HashKey routing Shard mode, and the log service writes data to the Shard containing the specified Key value.
    tailFiles Boolean
    LogCollector collection strategy, specifying whether LogCollector collects incremental logs or full logs. The default is false, which means full log collection. true: incremental collection. When LogCollector collects logs, it only collects newly added content in the file. When a monitored log file receives new log entries, LogCollector is triggered to collect logs. For log files being collected for the first time, LogCollector automatically determines the collection position based on the incremental threshold TailSizeKb you specify. If the new file size does not exceed the incremental threshold, collection starts from the beginning of the new file. If the new file size exceeds the incremental threshold, collection starts from the position at the end of the file minus the incremental threshold, meaning only incremental logs are collected. For log files that are not being collected for the first time, LogCollector determines the collection position based on the Checkpoint and continues collecting. false: (default) full collection. LogCollector collects logs from the beginning of each file, including historical log data.
    tailSizeKb Integer
    Incremental collection backtracking threshold, in KiB. When LogCollector uses incremental collection, for the first collection of a log file: if the new log file size does not exceed the TailSizeKb value, collection starts from the beginning of the file. If the new log file size exceeds the TailSizeKb value, collection starts from the position TailSizeKb from the end of the file.
    advanced HostGroupRuleUserDefineRuleAdvanced
    Advanced parameters are used for extended configuration. After enabling extended configuration, you can customize advanced behaviors of LogCollector, such as when to release file handles. Note: If multiple conditions for releasing handles are specified, the handle will be released and log file monitoring will end as soon as any condition is met.
    enableHostGroupLabel boolean
    Whether to upload the Label information of the host group to the log service. Disabled by default. true: LogCollector uploads the Label information of the host group to the specified field. You can specify the field name in the HostGroupLabelKey parameter. false (default): LogCollector does not upload the Label information of the host group.
    enableHostname boolean
    Whether to upload the hostname field. Default is disabled. true: Adds a field to the original log to record the log source's hostname. Specify the hostname field name using HostnameKey. false (default): Does not add the hostname field.
    enableRawLog boolean
    Whether to upload raw logs. true: Upload raw logs. false (default): Do not upload raw logs.
    fields HostGroupRuleUserDefineRuleField[]
    Add constant fields to logs. Constant fields must follow these restrictions: Up to 5 constant fields can be uploaded. Field name (Key) must be unique and not empty. Length: 1–128 characters, including letters, numbers, and special characters (-*./), and cannot start with an underscore. Field value (Value) must not be empty, maximum length is 512 KiB. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    hostGroupLabelKey string
    Field name used to store machine group label information.
    hostnameKey string
    hostname field name. Only required when EnableHostname is set to true.
    ignoreOlder number
    Ignore log files that have not been updated for a specified duration, in hours.
    multiCollectsType string
    Allows multiple log file collections. Empty: Uses the log file ID (including file inode, device, and checksum of the first N bytes) to uniquely identify the log file. RuleID: Uses the collection rule ID and log file ID to uniquely identify the log file. TopicIDRuleName: Uses the log topic ID, collection rule Name, and log file ID to uniquely identify the log file.
    parsePathRule HostGroupRuleUserDefineRuleParsePathRule
    Rules for parsing the collection path. After setting the rule, fields in the collection path are extracted using the specified regex and added as metadata to the log data. Note: This parameter is not supported when collecting container standard output.
    plugin HostGroupRuleUserDefineRulePlugin
    LogCollector plugin configuration. After enabling plugin configuration, you can add one or more LogCollector processor plugins to parse logs with complex or variable structures.
    rawLogKey string
    Original log field name. Only effective when EnableRawLog is set to true. RawLogKey defaults to raw, meaning the original log data will be encapsulated in the raw field and uploaded to the log service together with the parsed log data
    shardHashKey HostGroupRuleUserDefineRuleShardHashKey
    Rules for routing log partitions. If this parameter is not set, logs are written using the default load balancing mode, and packets are written to any available Shard. If set, logs are collected using the HashKey routing Shard mode, and the log service writes data to the Shard containing the specified Key value.
    tailFiles boolean
    LogCollector collection strategy, specifying whether LogCollector collects incremental logs or full logs. The default is false, which means full log collection. true: incremental collection. When LogCollector collects logs, it only collects newly added content in the file. When a monitored log file receives new log entries, LogCollector is triggered to collect logs. For log files being collected for the first time, LogCollector automatically determines the collection position based on the incremental threshold TailSizeKb you specify. If the new file size does not exceed the incremental threshold, collection starts from the beginning of the new file. If the new file size exceeds the incremental threshold, collection starts from the position at the end of the file minus the incremental threshold, meaning only incremental logs are collected. For log files that are not being collected for the first time, LogCollector determines the collection position based on the Checkpoint and continues collecting. false: (default) full collection. LogCollector collects logs from the beginning of each file, including historical log data.
    tailSizeKb number
    Incremental collection backtracking threshold, in KiB. When LogCollector uses incremental collection, for the first collection of a log file: if the new log file size does not exceed the TailSizeKb value, collection starts from the beginning of the file. If the new log file size exceeds the TailSizeKb value, collection starts from the position TailSizeKb from the end of the file.
    advanced HostGroupRuleUserDefineRuleAdvanced
    Advanced parameters are used for extended configuration. After enabling extended configuration, you can customize advanced behaviors of LogCollector, such as when to release file handles. Note: If multiple conditions for releasing handles are specified, the handle will be released and log file monitoring will end as soon as any condition is met.
    enable_host_group_label bool
    Whether to upload the Label information of the host group to the log service. Disabled by default. true: LogCollector uploads the Label information of the host group to the specified field. You can specify the field name in the HostGroupLabelKey parameter. false (default): LogCollector does not upload the Label information of the host group.
    enable_hostname bool
    Whether to upload the hostname field. Default is disabled. true: Adds a field to the original log to record the log source's hostname. Specify the hostname field name using HostnameKey. false (default): Does not add the hostname field.
    enable_raw_log bool
    Whether to upload raw logs. true: Upload raw logs. false (default): Do not upload raw logs.
    fields Sequence[HostGroupRuleUserDefineRuleField]
    Add constant fields to logs. Constant fields must follow these restrictions: Up to 5 constant fields can be uploaded. Field name (Key) must be unique and not empty. Length: 1–128 characters, including letters, numbers, and special characters (-*./), and cannot start with an underscore. Field value (Value) must not be empty, maximum length is 512 KiB. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    host_group_label_key str
    Field name used to store machine group label information.
    hostname_key str
    hostname field name. Only required when EnableHostname is set to true.
    ignore_older int
    Ignore log files that have not been updated for a specified duration, in hours.
    multi_collects_type str
    Allows multiple log file collections. Empty: Uses the log file ID (including file inode, device, and checksum of the first N bytes) to uniquely identify the log file. RuleID: Uses the collection rule ID and log file ID to uniquely identify the log file. TopicIDRuleName: Uses the log topic ID, collection rule Name, and log file ID to uniquely identify the log file.
    parse_path_rule HostGroupRuleUserDefineRuleParsePathRule
    Rules for parsing the collection path. After setting the rule, fields in the collection path are extracted using the specified regex and added as metadata to the log data. Note: This parameter is not supported when collecting container standard output.
    plugin HostGroupRuleUserDefineRulePlugin
    LogCollector plugin configuration. After enabling plugin configuration, you can add one or more LogCollector processor plugins to parse logs with complex or variable structures.
    raw_log_key str
    Original log field name. Only effective when EnableRawLog is set to true. RawLogKey defaults to raw, meaning the original log data will be encapsulated in the raw field and uploaded to the log service together with the parsed log data
    shard_hash_key HostGroupRuleUserDefineRuleShardHashKey
    Rules for routing log partitions. If this parameter is not set, logs are written using the default load balancing mode, and packets are written to any available Shard. If set, logs are collected using the HashKey routing Shard mode, and the log service writes data to the Shard containing the specified Key value.
    tail_files bool
    LogCollector collection strategy, specifying whether LogCollector collects incremental logs or full logs. The default is false, which means full log collection. true: incremental collection. When LogCollector collects logs, it only collects newly added content in the file. When a monitored log file receives new log entries, LogCollector is triggered to collect logs. For log files being collected for the first time, LogCollector automatically determines the collection position based on the incremental threshold TailSizeKb you specify. If the new file size does not exceed the incremental threshold, collection starts from the beginning of the new file. If the new file size exceeds the incremental threshold, collection starts from the position at the end of the file minus the incremental threshold, meaning only incremental logs are collected. For log files that are not being collected for the first time, LogCollector determines the collection position based on the Checkpoint and continues collecting. false: (default) full collection. LogCollector collects logs from the beginning of each file, including historical log data.
    tail_size_kb int
    Incremental collection backtracking threshold, in KiB. When LogCollector uses incremental collection, for the first collection of a log file: if the new log file size does not exceed the TailSizeKb value, collection starts from the beginning of the file. If the new log file size exceeds the TailSizeKb value, collection starts from the position TailSizeKb from the end of the file.
    advanced Property Map
    Advanced parameters are used for extended configuration. After enabling extended configuration, you can customize advanced behaviors of LogCollector, such as when to release file handles. Note: If multiple conditions for releasing handles are specified, the handle will be released and log file monitoring will end as soon as any condition is met.
    enableHostGroupLabel Boolean
    Whether to upload the Label information of the host group to the log service. Disabled by default. true: LogCollector uploads the Label information of the host group to the specified field. You can specify the field name in the HostGroupLabelKey parameter. false (default): LogCollector does not upload the Label information of the host group.
    enableHostname Boolean
    Whether to upload the hostname field. Default is disabled. true: Adds a field to the original log to record the log source's hostname. Specify the hostname field name using HostnameKey. false (default): Does not add the hostname field.
    enableRawLog Boolean
    Whether to upload raw logs. true: Upload raw logs. false (default): Do not upload raw logs.
    fields List<Property Map>
    Add constant fields to logs. Constant fields must follow these restrictions: Up to 5 constant fields can be uploaded. Field name (Key) must be unique and not empty. Length: 1–128 characters, including letters, numbers, and special characters (-*./), and cannot start with an underscore. Field value (Value) must not be empty, maximum length is 512 KiB. Important Note: When using SetNestedAttribute, you must fully define all attributes of its nested structure. Incomplete definitions may cause Terraform to detect unexpected differences during plan comparison, triggering unnecessary resource updates and affecting resource stability and predictability.
    hostGroupLabelKey String
    Field name used to store machine group label information.
    hostnameKey String
    hostname field name. Only required when EnableHostname is set to true.
    ignoreOlder Number
    Ignore log files that have not been updated for a specified duration, in hours.
    multiCollectsType String
    Allows multiple log file collections. Empty: Uses the log file ID (including file inode, device, and checksum of the first N bytes) to uniquely identify the log file. RuleID: Uses the collection rule ID and log file ID to uniquely identify the log file. TopicIDRuleName: Uses the log topic ID, collection rule Name, and log file ID to uniquely identify the log file.
    parsePathRule Property Map
    Rules for parsing the collection path. After setting the rule, fields in the collection path are extracted using the specified regex and added as metadata to the log data. Note: This parameter is not supported when collecting container standard output.
    plugin Property Map
    LogCollector plugin configuration. After enabling plugin configuration, you can add one or more LogCollector processor plugins to parse logs with complex or variable structures.
    rawLogKey String
    Original log field name. Only effective when EnableRawLog is set to true. RawLogKey defaults to raw, meaning the original log data will be encapsulated in the raw field and uploaded to the log service together with the parsed log data
    shardHashKey Property Map
    Rules for routing log partitions. If this parameter is not set, logs are written using the default load balancing mode, and packets are written to any available Shard. If set, logs are collected using the HashKey routing Shard mode, and the log service writes data to the Shard containing the specified Key value.
    tailFiles Boolean
    LogCollector collection strategy, specifying whether LogCollector collects incremental logs or full logs. The default is false, which means full log collection. true: incremental collection. When LogCollector collects logs, it only collects newly added content in the file. When a monitored log file receives new log entries, LogCollector is triggered to collect logs. For log files being collected for the first time, LogCollector automatically determines the collection position based on the incremental threshold TailSizeKb you specify. If the new file size does not exceed the incremental threshold, collection starts from the beginning of the new file. If the new file size exceeds the incremental threshold, collection starts from the position at the end of the file minus the incremental threshold, meaning only incremental logs are collected. For log files that are not being collected for the first time, LogCollector determines the collection position based on the Checkpoint and continues collecting. false: (default) full collection. LogCollector collects logs from the beginning of each file, including historical log data.
    tailSizeKb Number
    Incremental collection backtracking threshold, in KiB. When LogCollector uses incremental collection, for the first collection of a log file: if the new log file size does not exceed the TailSizeKb value, collection starts from the beginning of the file. If the new log file size exceeds the TailSizeKb value, collection starts from the position TailSizeKb from the end of the file.

    HostGroupRuleUserDefineRuleAdvanced, HostGroupRuleUserDefineRuleAdvancedArgs

    CloseEof bool
    After reading to the end of the log file, whether to release the file handle. Default is false.
    CloseInactive int
    Wait time before releasing log file handles. If no new logs are written to a log file for the specified duration, the handle for that log file is released. Unit: seconds. Range: 1–300 seconds. Default: 60 seconds.
    CloseRemoved bool
    Whether to release the handle of the log file after it is removed. Default is false.
    CloseRenamed bool
    Whether to release the handle of the log file after it is renamed. Default is false.
    CloseTimeout int
    Maximum duration for LogCollector to monitor log files, in seconds. The default is 0 seconds, meaning LogCollector does not limit the monitoring duration. Timing starts when LogCollector begins monitoring the log file. After the specified duration is exceeded, regardless of whether the log file has been fully read, LogCollector immediately releases the file handle and stops monitoring.
    NoLineTerminatorEofMaxTime int
    Maximum wait time when LogCollector does not read a line break. Unit: seconds. Default: 5s. LogCollector starts timing when it begins reading log file content. If no line break is read within the specified time, it will send the buffered logs. If the file write interval is large, a complete log entry may be split into two parts and written separately. Adjust this parameter based on your log write interval.
    CloseEof bool
    After reading to the end of the log file, whether to release the file handle. Default is false.
    CloseInactive int
    Wait time before releasing log file handles. If no new logs are written to a log file for the specified duration, the handle for that log file is released. Unit: seconds. Range: 1–300 seconds. Default: 60 seconds.
    CloseRemoved bool
    Whether to release the handle of the log file after it is removed. Default is false.
    CloseRenamed bool
    Whether to release the handle of the log file after it is renamed. Default is false.
    CloseTimeout int
    Maximum duration for LogCollector to monitor log files, in seconds. The default is 0 seconds, meaning LogCollector does not limit the monitoring duration. Timing starts when LogCollector begins monitoring the log file. After the specified duration is exceeded, regardless of whether the log file has been fully read, LogCollector immediately releases the file handle and stops monitoring.
    NoLineTerminatorEofMaxTime int
    Maximum wait time when LogCollector does not read a line break. Unit: seconds. Default: 5s. LogCollector starts timing when it begins reading log file content. If no line break is read within the specified time, it will send the buffered logs. If the file write interval is large, a complete log entry may be split into two parts and written separately. Adjust this parameter based on your log write interval.
    close_eof bool
    After reading to the end of the log file, whether to release the file handle. Default is false.
    close_inactive number
    Wait time before releasing log file handles. If no new logs are written to a log file for the specified duration, the handle for that log file is released. Unit: seconds. Range: 1–300 seconds. Default: 60 seconds.
    close_removed bool
    Whether to release the handle of the log file after it is removed. Default is false.
    close_renamed bool
    Whether to release the handle of the log file after it is renamed. Default is false.
    close_timeout number
    Maximum duration for LogCollector to monitor log files, in seconds. The default is 0 seconds, meaning LogCollector does not limit the monitoring duration. Timing starts when LogCollector begins monitoring the log file. After the specified duration is exceeded, regardless of whether the log file has been fully read, LogCollector immediately releases the file handle and stops monitoring.
    no_line_terminator_eof_max_time number
    Maximum wait time when LogCollector does not read a line break. Unit: seconds. Default: 5s. LogCollector starts timing when it begins reading log file content. If no line break is read within the specified time, it will send the buffered logs. If the file write interval is large, a complete log entry may be split into two parts and written separately. Adjust this parameter based on your log write interval.
    closeEof Boolean
    After reading to the end of the log file, whether to release the file handle. Default is false.
    closeInactive Integer
    Wait time before releasing log file handles. If no new logs are written to a log file for the specified duration, the handle for that log file is released. Unit: seconds. Range: 1–300 seconds. Default: 60 seconds.
    closeRemoved Boolean
    Whether to release the handle of the log file after it is removed. Default is false.
    closeRenamed Boolean
    Whether to release the handle of the log file after it is renamed. Default is false.
    closeTimeout Integer
    Maximum duration for LogCollector to monitor log files, in seconds. The default is 0 seconds, meaning LogCollector does not limit the monitoring duration. Timing starts when LogCollector begins monitoring the log file. After the specified duration is exceeded, regardless of whether the log file has been fully read, LogCollector immediately releases the file handle and stops monitoring.
    noLineTerminatorEofMaxTime Integer
    Maximum wait time when LogCollector does not read a line break. Unit: seconds. Default: 5s. LogCollector starts timing when it begins reading log file content. If no line break is read within the specified time, it will send the buffered logs. If the file write interval is large, a complete log entry may be split into two parts and written separately. Adjust this parameter based on your log write interval.
    closeEof boolean
    After reading to the end of the log file, whether to release the file handle. Default is false.
    closeInactive number
    Wait time before releasing log file handles. If no new logs are written to a log file for the specified duration, the handle for that log file is released. Unit: seconds. Range: 1–300 seconds. Default: 60 seconds.
    closeRemoved boolean
    Whether to release the handle of the log file after it is removed. Default is false.
    closeRenamed boolean
    Whether to release the handle of the log file after it is renamed. Default is false.
    closeTimeout number
    Maximum duration for LogCollector to monitor log files, in seconds. The default is 0 seconds, meaning LogCollector does not limit the monitoring duration. Timing starts when LogCollector begins monitoring the log file. After the specified duration is exceeded, regardless of whether the log file has been fully read, LogCollector immediately releases the file handle and stops monitoring.
    noLineTerminatorEofMaxTime number
    Maximum wait time when LogCollector does not read a line break. Unit: seconds. Default: 5s. LogCollector starts timing when it begins reading log file content. If no line break is read within the specified time, it will send the buffered logs. If the file write interval is large, a complete log entry may be split into two parts and written separately. Adjust this parameter based on your log write interval.
    close_eof bool
    After reading to the end of the log file, whether to release the file handle. Default is false.
    close_inactive int
    Wait time before releasing log file handles. If no new logs are written to a log file for the specified duration, the handle for that log file is released. Unit: seconds. Range: 1–300 seconds. Default: 60 seconds.
    close_removed bool
    Whether to release the handle of the log file after it is removed. Default is false.
    close_renamed bool
    Whether to release the handle of the log file after it is renamed. Default is false.
    close_timeout int
    Maximum duration for LogCollector to monitor log files, in seconds. The default is 0 seconds, meaning LogCollector does not limit the monitoring duration. Timing starts when LogCollector begins monitoring the log file. After the specified duration is exceeded, regardless of whether the log file has been fully read, LogCollector immediately releases the file handle and stops monitoring.
    no_line_terminator_eof_max_time int
    Maximum wait time when LogCollector does not read a line break. Unit: seconds. Default: 5s. LogCollector starts timing when it begins reading log file content. If no line break is read within the specified time, it will send the buffered logs. If the file write interval is large, a complete log entry may be split into two parts and written separately. Adjust this parameter based on your log write interval.
    closeEof Boolean
    After reading to the end of the log file, whether to release the file handle. Default is false.
    closeInactive Number
    Wait time before releasing log file handles. If no new logs are written to a log file for the specified duration, the handle for that log file is released. Unit: seconds. Range: 1–300 seconds. Default: 60 seconds.
    closeRemoved Boolean
    Whether to release the handle of the log file after it is removed. Default is false.
    closeRenamed Boolean
    Whether to release the handle of the log file after it is renamed. Default is false.
    closeTimeout Number
    Maximum duration for LogCollector to monitor log files, in seconds. The default is 0 seconds, meaning LogCollector does not limit the monitoring duration. Timing starts when LogCollector begins monitoring the log file. After the specified duration is exceeded, regardless of whether the log file has been fully read, LogCollector immediately releases the file handle and stops monitoring.
    noLineTerminatorEofMaxTime Number
    Maximum wait time when LogCollector does not read a line break. Unit: seconds. Default: 5s. LogCollector starts timing when it begins reading log file content. If no line break is read within the specified time, it will send the buffered logs. If the file write interval is large, a complete log entry may be split into two parts and written separately. Adjust this parameter based on your log write interval.

    HostGroupRuleUserDefineRuleField, HostGroupRuleUserDefineRuleFieldArgs

    Key string
    Key.
    Val string
    Value.
    Key string
    Key.
    Val string
    Value.
    key string
    Key.
    val string
    Value.
    key String
    Key.
    val String
    Value.
    key string
    Key.
    val string
    Value.
    key str
    Key.
    val str
    Value.
    key String
    Key.
    val String
    Value.

    HostGroupRuleUserDefineRuleParsePathRule, HostGroupRuleUserDefineRuleParsePathRuleArgs

    Keys List<string>
    List of field names. Log Service parses PathSample into multiple fields using regular expressions (Regex). Keys specify the name of each field. You can configure up to 100 field names. Field names cannot be empty or duplicated.
    PathSample string
    Sample collection path for actual scenarios. The sample path must be an absolute path. Wildcards *, ?, ** are not allowed in the sample path.
    Regex string
    Regular expression used to extract the path field. It must match the example collection path; otherwise, extraction will fail.
    Keys []string
    List of field names. Log Service parses PathSample into multiple fields using regular expressions (Regex). Keys specify the name of each field. You can configure up to 100 field names. Field names cannot be empty or duplicated.
    PathSample string
    Sample collection path for actual scenarios. The sample path must be an absolute path. Wildcards *, ?, ** are not allowed in the sample path.
    Regex string
    Regular expression used to extract the path field. It must match the example collection path; otherwise, extraction will fail.
    keys list(string)
    List of field names. Log Service parses PathSample into multiple fields using regular expressions (Regex). Keys specify the name of each field. You can configure up to 100 field names. Field names cannot be empty or duplicated.
    path_sample string
    Sample collection path for actual scenarios. The sample path must be an absolute path. Wildcards *, ?, ** are not allowed in the sample path.
    regex string
    Regular expression used to extract the path field. It must match the example collection path; otherwise, extraction will fail.
    keys List<String>
    List of field names. Log Service parses PathSample into multiple fields using regular expressions (Regex). Keys specify the name of each field. You can configure up to 100 field names. Field names cannot be empty or duplicated.
    pathSample String
    Sample collection path for actual scenarios. The sample path must be an absolute path. Wildcards *, ?, ** are not allowed in the sample path.
    regex String
    Regular expression used to extract the path field. It must match the example collection path; otherwise, extraction will fail.
    keys string[]
    List of field names. Log Service parses PathSample into multiple fields using regular expressions (Regex). Keys specify the name of each field. You can configure up to 100 field names. Field names cannot be empty or duplicated.
    pathSample string
    Sample collection path for actual scenarios. The sample path must be an absolute path. Wildcards *, ?, ** are not allowed in the sample path.
    regex string
    Regular expression used to extract the path field. It must match the example collection path; otherwise, extraction will fail.
    keys Sequence[str]
    List of field names. Log Service parses PathSample into multiple fields using regular expressions (Regex). Keys specify the name of each field. You can configure up to 100 field names. Field names cannot be empty or duplicated.
    path_sample str
    Sample collection path for actual scenarios. The sample path must be an absolute path. Wildcards *, ?, ** are not allowed in the sample path.
    regex str
    Regular expression used to extract the path field. It must match the example collection path; otherwise, extraction will fail.
    keys List<String>
    List of field names. Log Service parses PathSample into multiple fields using regular expressions (Regex). Keys specify the name of each field. You can configure up to 100 field names. Field names cannot be empty or duplicated.
    pathSample String
    Sample collection path for actual scenarios. The sample path must be an absolute path. Wildcards *, ?, ** are not allowed in the sample path.
    regex String
    Regular expression used to extract the path field. It must match the example collection path; otherwise, extraction will fail.

    HostGroupRuleUserDefineRulePlugin, HostGroupRuleUserDefineRulePluginArgs

    Processors string
    LogCollector plugins. For supported plugin lists and parameter descriptions, see LogCollector plugin overview.
    Processors string
    LogCollector plugins. For supported plugin lists and parameter descriptions, see LogCollector plugin overview.
    processors string
    LogCollector plugins. For supported plugin lists and parameter descriptions, see LogCollector plugin overview.
    processors String
    LogCollector plugins. For supported plugin lists and parameter descriptions, see LogCollector plugin overview.
    processors string
    LogCollector plugins. For supported plugin lists and parameter descriptions, see LogCollector plugin overview.
    processors str
    LogCollector plugins. For supported plugin lists and parameter descriptions, see LogCollector plugin overview.
    processors String
    LogCollector plugins. For supported plugin lists and parameter descriptions, see LogCollector plugin overview.

    HostGroupRuleUserDefineRuleShardHashKey, HostGroupRuleUserDefineRuleShardHashKeyArgs

    HashKey string
    The HashKey of the log group specifies the shard where the current log group will be written. The valid range for this parameter is [00000000000000000000000000000000-ffffffffffffffffffffffffffffffff).
    HashKey string
    The HashKey of the log group specifies the shard where the current log group will be written. The valid range for this parameter is [00000000000000000000000000000000-ffffffffffffffffffffffffffffffff).
    hash_key string
    The HashKey of the log group specifies the shard where the current log group will be written. The valid range for this parameter is [00000000000000000000000000000000-ffffffffffffffffffffffffffffffff).
    hashKey String
    The HashKey of the log group specifies the shard where the current log group will be written. The valid range for this parameter is [00000000000000000000000000000000-ffffffffffffffffffffffffffffffff).
    hashKey string
    The HashKey of the log group specifies the shard where the current log group will be written. The valid range for this parameter is [00000000000000000000000000000000-ffffffffffffffffffffffffffffffff).
    hash_key str
    The HashKey of the log group specifies the shard where the current log group will be written. The valid range for this parameter is [00000000000000000000000000000000-ffffffffffffffffffffffffffffffff).
    hashKey String
    The HashKey of the log group specifies the shard where the current log group will be written. The valid range for this parameter is [00000000000000000000000000000000-ffffffffffffffffffffffffffffffff).

    Import

    $ pulumi import bytepluscc:tls/hostGroup:HostGroup example "host_group_id"

    To learn more about importing existing cloud resources, see Importing resources.

    Package Details

    Repository
    bytepluscc byteplus-sdk/pulumi-bytepluscc
    License
    MPL-2.0
    Notes
    This Pulumi package is based on the bytepluscc Terraform Provider.
    bytepluscc logo
    Viewing docs for bytepluscc v0.0.42
    published on Monday, Jul 20, 2026 by Byteplus
    Schema (JSON)
    byteplus-sdk/pulumi-bytepluscc

      Try Pulumi Cloud free.
      Your team will thank you.

      Start free trial