@byteplus/pulumi-bytepluscc 0.0.23 → 0.0.24

package/types/output.d.ts

@@ -7849,6 +7849,34 @@ export declare namespace cen {
          */
         value: string;
     }
+    interface GetServiceRouteEntryPublishToInstance {
+        /**
+         * Network instance ID for published cloud service access route.
+         */
+        instanceId: string;
+        /**
+         * Region for published cloud service access route.
+         */
+        instanceRegionId: string;
+        /**
+         * Network instance type for published cloud service access route.
+         */
+        instanceType: string;
+    }
+    interface ServiceRouteEntryPublishToInstance {
+        /**
+         * Network instance ID for published cloud service access route.
+         */
+        instanceId: string;
+        /**
+         * Region for published cloud service access route.
+         */
+        instanceRegionId: string;
+        /**
+         * Network instance type for published cloud service access route.
+         */
+        instanceType: string;
+    }
 }
 export declare namespace clb {
     interface AclAclEntry {
@@ -8195,6 +8223,24 @@ export declare namespace clb {
          */
         value: string;
     }
+    interface GetListenerDomainExtension {
+        /**
+         * Certificate ID of the extended domain name.
+         */
+        certCenterCertificateId: string;
+        /**
+         * Certificate source for the extended domain name to be added. Value: cert_center: SSL certificate from Volcano Engine Certificate Center. This parameter is required when adding an extended domain name.
+         */
+        certificateSource: string;
+        /**
+         * Domain name. Supports both wildcard and exact domain names. Specifications: 1. Must contain at least one '.', and cannot start or end with '.'. 2. Only letters, numbers, '.', '-', and '*' are allowed. 3. Length must be between 1 and 128 characters. 4. Wildcard domain: Use '*' to replace one or more characters. 5. Exact domain: A domain name that strictly follows domain name specifications.
+         */
+        domain: string;
+        /**
+         * Extended domain name ID.
+         */
+        domainExtensionId: string;
+    }
     interface GetListenerHealthCheck {
         /**
          * Domain name for health check. Must be set to the actual address provided by the backend server. This parameter takes effect when Protocol is set to HTTP or HTTPS and HealthCheck.Enabled is on. Must contain at least one period (.), and cannot start or end with a period (.). Each string can include letters, numbers, hyphens (-), and periods (.), with hyphens (-) not allowed at the beginning or end of the string. Length limit: 1 to 128 characters. If this parameter is not provided or no value is specified, the default is empty, meaning CLB uses the private IP address of each backend server for health checks.
@@ -8563,6 +8609,20 @@ export declare namespace clb {
          */
         value: string;
     }
+    interface ListenerDomainExtension {
+        /**
+         * Certificate ID of the extended domain name.
+         */
+        certCenterCertificateId: string;
+        /**
+         * Certificate source for the extended domain name to be added. Value: cert_center: SSL certificate from Volcano Engine Certificate Center. This parameter is required when adding an extended domain name.
+         */
+        certificateSource: string;
+        /**
+         * Domain name. Supports both wildcard and exact domain names. Specifications: 1. Must contain at least one '.', and cannot start or end with '.'. 2. Only letters, numbers, '.', '-', and '*' are allowed. 3. Length must be between 1 and 128 characters. 4. Wildcard domain: Use '*' to replace one or more characters. 5. Exact domain: A domain name that strictly follows domain name specifications.
+         */
+        domain: string;
+    }
     interface ListenerHealthCheck {
         /**
          * Domain name for health check. Must be set to the actual address provided by the backend server. This parameter takes effect when Protocol is set to HTTP or HTTPS and HealthCheck.Enabled is on. Must contain at least one period (.), and cannot start or end with a period (.). Each string can include letters, numbers, hyphens (-), and periods (.), with hyphens (-) not allowed at the beginning or end of the string. Length limit: 1 to 128 characters. If this parameter is not provided or no value is specified, the default is empty, meaning CLB uses the private IP address of each backend server for health checks.
@@ -15232,10 +15292,6 @@ export declare namespace privatelink {
         value: string;
     }
     interface EndpointServiceResource {
-        /**
-         * Endpoint service ID.
-         */
-        instanceId: string;
         /**
          * Service resource ID to be added to the endpoint service.
          */
@@ -15274,14 +15330,14 @@ export declare namespace privatelink {
         value: string;
     }
     interface GetEndpointServiceResource {
-        /**
-         * Endpoint service ID.
-         */
-        instanceId: string;
         /**
          * Service resource ID to be added to the endpoint service.
          */
         resourceId: string;
+        /**
+         * Type of service resource.
+         */
+        resourceType: string;
         /**
          * Availability zone where the load balancer provides service.
          */
@@ -15297,6 +15353,54 @@ export declare namespace privatelink {
          */
         value: string;
     }
+    interface GetVpcEndpointConnectionResourcesAllocate {
+        /**
+         * Specify the service resource for the endpoint connection
+         */
+        resourceId: string;
+        /**
+         * Availability zone ID of the service resource to be specified
+         */
+        zoneId: string;
+    }
+    interface GetVpcEndpointConnectionZone {
+        /**
+         * Endpoint network interface ID. If a seamless service resource replacement is in progress, this indicates the endpoint network interface ID connected to the replaced service resource
+         */
+        networkInterfaceId: string;
+        /**
+         * The private IPv4 address of the terminal node NIC. If a smooth service resource replacement is in progress, this refers to the IPv4 address of the terminal node NIC connected to the service resource being replaced.
+         */
+        networkInterfaceIp: string;
+        /**
+         * Private IPv6 address of the endpoint network interface. If a seamless service resource replacement is in progress, this indicates the IPv6 address of the endpoint network interface connected to the replaced service resource. If the endpoint only supports IPv4, this parameter is not returned
+         */
+        networkInterfaceIpv6: string;
+        /**
+         * Service resource ID
+         */
+        resourceId: string;
+        /**
+         * Status of the service resource
+         */
+        serviceStatus: string;
+        /**
+         * ID of the subnet to which the endpoint network interface belongs
+         */
+        subnetId: string;
+        /**
+         * The domain name of the terminal node availability zone.
+         */
+        zoneDomain: string;
+        /**
+         * Endpoint zone ID
+         */
+        zoneId: string;
+        /**
+         * Status of the endpoint zone. PendingAcceptance: waiting for connection. Connecting: connecting. Connected: connected. Disconnecting: disconnecting. Rejected: connection rejected. Failed: connection failed
+         */
+        zoneStatus: string;
+    }
     interface GetVpcEndpointTag {
         /**
          * Tag key of the endpoint user tag. Length limit: 1–128 characters. Case sensitive. Cannot start with 'or' or 'sys:' in any case combination. Cannot start or end with a space. Allowed characters: letters, numbers, spaces ( ), underscores (_), periods (.), colons (:), slashes (/), equal signs (=), plus signs (+), hyphens (-), and @.
@@ -15345,6 +15449,54 @@ export declare namespace privatelink {
          */
         zoneStatus: string;
     }
+    interface VpcEndpointConnectionResourcesAllocate {
+        /**
+         * Specify the service resource for the endpoint connection
+         */
+        resourceId: string;
+        /**
+         * Availability zone ID of the service resource to be specified
+         */
+        zoneId: string;
+    }
+    interface VpcEndpointConnectionZone {
+        /**
+         * Endpoint network interface ID. If a seamless service resource replacement is in progress, this indicates the endpoint network interface ID connected to the replaced service resource
+         */
+        networkInterfaceId: string;
+        /**
+         * The private IPv4 address of the terminal node NIC. If a smooth service resource replacement is in progress, this refers to the IPv4 address of the terminal node NIC connected to the service resource being replaced.
+         */
+        networkInterfaceIp: string;
+        /**
+         * Private IPv6 address of the endpoint network interface. If a seamless service resource replacement is in progress, this indicates the IPv6 address of the endpoint network interface connected to the replaced service resource. If the endpoint only supports IPv4, this parameter is not returned
+         */
+        networkInterfaceIpv6: string;
+        /**
+         * Service resource ID
+         */
+        resourceId: string;
+        /**
+         * Status of the service resource
+         */
+        serviceStatus: string;
+        /**
+         * ID of the subnet to which the endpoint network interface belongs
+         */
+        subnetId: string;
+        /**
+         * The domain name of the terminal node availability zone.
+         */
+        zoneDomain: string;
+        /**
+         * Endpoint zone ID
+         */
+        zoneId: string;
+        /**
+         * Status of the endpoint zone. PendingAcceptance: waiting for connection. Connecting: connecting. Connected: connected. Disconnecting: disconnecting. Rejected: connection rejected. Failed: connection failed
+         */
+        zoneStatus: string;
+    }
     interface VpcEndpointTag {
         /**
          * Tag key of the endpoint user tag. Length limit: 1–128 characters. Case sensitive. Cannot start with 'or' or 'sys:' in any case combination. Cannot start or end with a space. Allowed characters: letters, numbers, spaces ( ), underscores (_), periods (.), colons (:), slashes (/), equal signs (=), plus signs (+), hyphens (-), and @.
@@ -15501,6 +15653,26 @@ export declare namespace privatezone {
     }
 }
 export declare namespace rabbitmq {
+    interface AllowListAssociatedInstance {
+        /**
+         * Instance ID
+         */
+        instanceId: string;
+    }
+    interface GetAllowListAssociatedInstance {
+        /**
+         * Instance ID
+         */
+        instanceId: string;
+        /**
+         * Instance Name
+         */
+        instanceName: string;
+        /**
+         * VPC ID of the instance
+         */
+        vpc: string;
+    }
     interface GetInstanceChargeDetail {
         /**
          * Whether to automatically renew the subscription instance after expiration.
@@ -17723,6 +17895,70 @@ export declare namespace rdspostgresql {
     }
 }
 export declare namespace redis {
+    interface AllowListAssociatedInstance {
+        /**
+         * Instance ID bound to the current allowlist
+         */
+        instanceId: string;
+        /**
+         * Instance names bound to the current allowlist
+         */
+        instanceName: string;
+        /**
+         * Project name associated with the instance
+         */
+        projectName: string;
+        /**
+         * Private network ID associated with the instance
+         */
+        vpc: string;
+    }
+    interface AllowListSecurityGroupBindInfo {
+        /**
+         * Security group association mode. The value range is as follows: IngressDirectionIp: ingress IP, which allows IPs involved in TCP and ALL protocols in the source address of the security group ingress direction to access the database. If the source address is configured as a security group, it will be ignored. AssociateEcsIp: associate ECS IP, which allows cloud servers within the security group to access the database. Currently, only importing IP information of the primary network interface is supported
+         */
+        bindMode: string;
+        /**
+         * Associated security group ID
+         */
+        securityGroupId: string;
+    }
+    interface GetAllowListAssociatedInstance {
+        /**
+         * Instance ID bound to the current allowlist
+         */
+        instanceId: string;
+        /**
+         * Instance names bound to the current allowlist
+         */
+        instanceName: string;
+        /**
+         * Project name associated with the instance
+         */
+        projectName: string;
+        /**
+         * Private network ID associated with the instance
+         */
+        vpc: string;
+    }
+    interface GetAllowListSecurityGroupBindInfo {
+        /**
+         * Security group association mode. The value range is as follows: IngressDirectionIp: ingress IP, which allows IPs involved in TCP and ALL protocols in the source address of the security group ingress direction to access the database. If the source address is configured as a security group, it will be ignored. AssociateEcsIp: associate ECS IP, which allows cloud servers within the security group to access the database. Currently, only importing IP information of the primary network interface is supported
+         */
+        bindMode: string;
+        /**
+         * IP list of security groups associated with the allowlist
+         */
+        ipLists: string[];
+        /**
+         * Associated security group ID
+         */
+        securityGroupId: string;
+        /**
+         * Name of the associated security group
+         */
+        securityGroupName: string;
+    }
     interface GetInstanceCapacity {
         /**
          * Total memory capacity of the current instance. Unit: MiB.
@@ -17890,127 +18126,1679 @@ export declare namespace redis {
     }
 }
 export declare namespace storageebs {
-    interface GetSnapshotTag {
+    interface GetSnapshotGroupSnapshot {
         /**
-         * User tag key added to the resource. Naming rules: Cannot start with volc: or sys: in any case. Keys starting with volc: or sys: are reserved system tag keys and cannot be created. Only language characters, numbers, spaces, and the following English symbols are allowed: '_', '.', ':', '/', '=', '+', '-', '@'. Length must be between 1 and 128 characters.
+         * Snapshot creation time
          */
-        key: string;
+        creationTime: string;
         /**
-         * User tag value added to the resource. Naming rules: Only language characters, numbers, spaces, and the following English symbols are allowed: '_', '.', ':', '/', '=', '+', '-', '@'. Can be empty. Length must be between 0 and 256 characters.
+         * Snapshot description
          */
-        value: string;
-    }
-    interface GetVolumeBaselinePerformance {
+        description: string;
         /**
-         * Total IOPS of the disk, which is the sum of the baseline IOPS and extra IOPS.
+         * Image ID
          */
-        iops: number;
+        imageId: string;
         /**
-         * The total throughput of the cloud disk is the sum of its baseline throughput and additional throughput.
+         * Whether the snapshot has enabled ultra-fast availability. Values are as follows:   - true: Ultra-fast availability enabled   - false: Ultra-fast availability not enabled
          */
-        throughput: number;
-    }
-    interface GetVolumeExtraPerformance {
+        instantAccess: boolean;
         /**
-         * Type of extra performance. Value description: Balance: Balanced extra performance; IOPS: IOPS extra performance; Throughput: Throughput extra performance.
+         * Dump progress
          */
-        extraPerformanceTypeId: string;
+        progress: number;
         /**
-         * Extra IOPS of the disk.
+         * Project of the snapshot
          */
-        iops: number;
+        projectName: string;
         /**
-         * Extra throughput of the disk.
+         * Retention days for automatic snapshots
          */
-        throughput: number;
-    }
-    interface GetVolumeTag {
+        retentionDays: number;
         /**
-         * Tag key.
+         * Whether the snapshot is shared with others. Values are as follows:   - true: Snapshot is shared with others   - false: Snapshot is not shared with others
          */
-        key: string;
+        shared: boolean;
         /**
-         * Tag value.
+         * Snapshot consistency group ID
          */
-        value: string;
-    }
-    interface GetVolumeTotalPerformance {
+        snapshotGroupId: string;
         /**
-         * Total IOPS of the disk, which is the sum of the baseline IOPS and extra IOPS.
+         * Snapshot ID
          */
-        iops: number;
+        snapshotId: string;
         /**
-         * The total throughput of the cloud disk is the sum of its baseline throughput and additional throughput.
+         * Snapshot name
          */
-        throughput: number;
-    }
-    interface SnapshotTag {
+        snapshotName: string;
         /**
-         * User tag key added to the resource. Naming rules: Cannot start with volc: or sys: in any case. Keys starting with volc: or sys: are reserved system tag keys and cannot be created. Only language characters, numbers, spaces, and the following English symbols are allowed: '_', '.', ':', '/', '=', '+', '-', '@'. Length must be between 1 and 128 characters.
+         * Snapshot type. Values are as follows:   - user: Manual snapshot   - auto: Automatic snapshot
          */
-        key: string;
+        snapshotType: string;
         /**
-         * User tag value added to the resource. Naming rules: Only language characters, numbers, spaces, and the following English symbols are allowed: '_', '.', ':', '/', '=', '+', '-', '@'. Can be empty. Length must be between 0 and 256 characters.
+         * Snapshot status. Values are as follows:   - available: Available   - creating: Creating   - rollbacking: Rolling back   - deleted: Deleted   - failed: Error
          */
-        value: string;
-    }
-    interface VolumeBaselinePerformance {
+        status: string;
         /**
-         * Total IOPS of the disk, which is the sum of the baseline IOPS and extra IOPS.
+         * Tag information
          */
-        iops: number;
+        tags: outputs.storageebs.GetSnapshotGroupSnapshotTag[];
         /**
-         * The total throughput of the cloud disk is the sum of its baseline throughput and additional throughput.
+         * Cloud disk ID
          */
-        throughput: number;
-    }
-    interface VolumeExtraPerformance {
+        volumeId: string;
         /**
-         * Type of extra performance. Value description: Balance: Balanced extra performance; IOPS: IOPS extra performance; Throughput: Throughput extra performance.
+         * Cloud disk category. Values are as follows:   - system: System disk   - data: Data disk
          */
-        extraPerformanceTypeId: string;
+        volumeKind: string;
         /**
-         * Extra IOPS of the disk.
+         * Cloud disk name
          */
-        iops: number;
+        volumeName: string;
         /**
-         * Extra throughput of the disk.
+         * Cloud disk size (GiB)
          */
-        throughput: number;
-    }
-    interface VolumeTag {
+        volumeSize: number;
         /**
-         * Tag key.
+         * Cloud disk status. Values are as follows:   - available: Available   - attaching: Attaching   - attached: Attached   - detaching: Detaching   - creating: Creating   - deleting: Deleting   - error: Error   - extending: Expanding
          */
-        key: string;
+        volumeStatus: string;
         /**
-         * Tag value.
+         * Cloud disk type. Values are as follows:   - ESSD*PL0: Ultra-fast SSD cloud disk, PL0 specification   - ESSD*FlexPL: Ultra-fast SSD cloud disk, FlexPL specification   - TSSD_TL0: Throughput SSD cloud disk
+         */
+        volumeType: string;
+        /**
+         * Zone ID. If ultra-fast availability is enabled for the snapshot, you can create a cloud disk in this zone using the ultra-fast available snapshot
+         */
+        zoneId: string;
+    }
+    interface GetSnapshotGroupSnapshotTag {
+        /**
+         * Tag key
+         */
+        key: string;
+        /**
+         * Tag value
+         */
+        value: string;
+    }
+    interface GetSnapshotGroupTag {
+        /**
+         * Tag key
+         */
+        key: string;
+        /**
+         * Tag value
+         */
+        value: string;
+    }
+    interface GetSnapshotTag {
+        /**
+         * User tag key added to the resource. Naming rules: Cannot start with volc: or sys: in any case. Keys starting with volc: or sys: are reserved system tag keys and cannot be created. Only language characters, numbers, spaces, and the following English symbols are allowed: '_', '.', ':', '/', '=', '+', '-', '@'. Length must be between 1 and 128 characters.
+         */
+        key: string;
+        /**
+         * User tag value added to the resource. Naming rules: Only language characters, numbers, spaces, and the following English symbols are allowed: '_', '.', ':', '/', '=', '+', '-', '@'. Can be empty. Length must be between 0 and 256 characters.
+         */
+        value: string;
+    }
+    interface GetVolumeBaselinePerformance {
+        /**
+         * Total IOPS of the disk, which is the sum of the baseline IOPS and extra IOPS.
+         */
+        iops: number;
+        /**
+         * The total throughput of the cloud disk is the sum of its baseline throughput and additional throughput.
+         */
+        throughput: number;
+    }
+    interface GetVolumeExtraPerformance {
+        /**
+         * Type of extra performance. Value description: Balance: Balanced extra performance; IOPS: IOPS extra performance; Throughput: Throughput extra performance.
+         */
+        extraPerformanceTypeId: string;
+        /**
+         * Extra IOPS of the disk.
+         */
+        iops: number;
+        /**
+         * Extra throughput of the disk.
+         */
+        throughput: number;
+    }
+    interface GetVolumeTag {
+        /**
+         * Tag key.
+         */
+        key: string;
+        /**
+         * Tag value.
+         */
+        value: string;
+    }
+    interface GetVolumeTotalPerformance {
+        /**
+         * Total IOPS of the disk, which is the sum of the baseline IOPS and extra IOPS.
+         */
+        iops: number;
+        /**
+         * The total throughput of the cloud disk is the sum of its baseline throughput and additional throughput.
+         */
+        throughput: number;
+    }
+    interface SnapshotGroupSnapshot {
+        /**
+         * Snapshot creation time
+         */
+        creationTime: string;
+        /**
+         * Snapshot description
+         */
+        description: string;
+        /**
+         * Image ID
+         */
+        imageId: string;
+        /**
+         * Whether the snapshot has enabled ultra-fast availability. Values are as follows:   - true: Ultra-fast availability enabled   - false: Ultra-fast availability not enabled
+         */
+        instantAccess: boolean;
+        /**
+         * Dump progress
+         */
+        progress: number;
+        /**
+         * Project of the snapshot
+         */
+        projectName: string;
+        /**
+         * Retention days for automatic snapshots
+         */
+        retentionDays: number;
+        /**
+         * Whether the snapshot is shared with others. Values are as follows:   - true: Snapshot is shared with others   - false: Snapshot is not shared with others
+         */
+        shared: boolean;
+        /**
+         * Snapshot consistency group ID
+         */
+        snapshotGroupId: string;
+        /**
+         * Snapshot ID
+         */
+        snapshotId: string;
+        /**
+         * Snapshot name
+         */
+        snapshotName: string;
+        /**
+         * Snapshot type. Values are as follows:   - user: Manual snapshot   - auto: Automatic snapshot
+         */
+        snapshotType: string;
+        /**
+         * Snapshot status. Values are as follows:   - available: Available   - creating: Creating   - rollbacking: Rolling back   - deleted: Deleted   - failed: Error
+         */
+        status: string;
+        tags: outputs.storageebs.SnapshotGroupSnapshotTag[];
+        /**
+         * Cloud disk ID
+         */
+        volumeId: string;
+        /**
+         * Cloud disk category. Values are as follows:   - system: System disk   - data: Data disk
+         */
+        volumeKind: string;
+        /**
+         * Cloud disk name
+         */
+        volumeName: string;
+        /**
+         * Cloud disk size (GiB)
+         */
+        volumeSize: number;
+        /**
+         * Cloud disk status. Values are as follows:   - available: Available   - attaching: Attaching   - attached: Attached   - detaching: Detaching   - creating: Creating   - deleting: Deleting   - error: Error   - extending: Expanding
+         */
+        volumeStatus: string;
+        /**
+         * Cloud disk type. Values are as follows:   - ESSD*PL0: Ultra-fast SSD cloud disk, PL0 specification   - ESSD*FlexPL: Ultra-fast SSD cloud disk, FlexPL specification   - TSSD_TL0: Throughput SSD cloud disk
+         */
+        volumeType: string;
+        /**
+         * Zone ID. If ultra-fast availability is enabled for the snapshot, you can create a cloud disk in this zone using the ultra-fast available snapshot
+         */
+        zoneId: string;
+    }
+    interface SnapshotGroupSnapshotTag {
+        /**
+         * Tag key
+         */
+        key: string;
+        /**
+         * Tag value
+         */
+        value: string;
+    }
+    interface SnapshotGroupTag {
+        /**
+         * Tag key
+         */
+        key: string;
+        /**
+         * Tag value
+         */
+        value: string;
+    }
+    interface SnapshotTag {
+        /**
+         * User tag key added to the resource. Naming rules: Cannot start with volc: or sys: in any case. Keys starting with volc: or sys: are reserved system tag keys and cannot be created. Only language characters, numbers, spaces, and the following English symbols are allowed: '_', '.', ':', '/', '=', '+', '-', '@'. Length must be between 1 and 128 characters.
+         */
+        key: string;
+        /**
+         * User tag value added to the resource. Naming rules: Only language characters, numbers, spaces, and the following English symbols are allowed: '_', '.', ':', '/', '=', '+', '-', '@'. Can be empty. Length must be between 0 and 256 characters.
+         */
+        value: string;
+    }
+    interface VolumeBaselinePerformance {
+        /**
+         * Total IOPS of the disk, which is the sum of the baseline IOPS and extra IOPS.
+         */
+        iops: number;
+        /**
+         * The total throughput of the cloud disk is the sum of its baseline throughput and additional throughput.
+         */
+        throughput: number;
+    }
+    interface VolumeExtraPerformance {
+        /**
+         * Type of extra performance. Value description: Balance: Balanced extra performance; IOPS: IOPS extra performance; Throughput: Throughput extra performance.
+         */
+        extraPerformanceTypeId: string;
+        /**
+         * Extra IOPS of the disk.
+         */
+        iops: number;
+        /**
+         * Extra throughput of the disk.
+         */
+        throughput: number;
+    }
+    interface VolumeTag {
+        /**
+         * Tag key.
+         */
+        key: string;
+        /**
+         * Tag value.
+         */
+        value: string;
+    }
+    interface VolumeTotalPerformance {
+        /**
+         * Total IOPS of the disk, which is the sum of the baseline IOPS and extra IOPS.
+         */
+        iops: number;
+        /**
+         * The total throughput of the cloud disk is the sum of its baseline throughput and additional throughput.
+         */
+        throughput: number;
+    }
+}
+export declare namespace tls {
+    interface AlarmNotifyGroupNoticeRule {
+        /**
+         * Whether there is an end node afterwards.
+         */
+        hasEndNode: boolean;
+        /**
+         * Condition for whether to proceed to the next level.
+         */
+        hasNext: boolean;
+        receiverInfos: outputs.tls.AlarmNotifyGroupNoticeRuleReceiverInfo[];
+        /**
+         * Rule node. JSON format.
+         */
+        ruleNode: string;
+    }
+    interface AlarmNotifyGroupNoticeRuleReceiverInfo {
+        /**
+         * Alarm content template ID.
+         */
+        alarmContentTemplateId: string;
+        /**
+         * User group name to notify when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookAtGroups: string[];
+        /**
+         * Username to notify when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookAtUsers: string[];
+        /**
+         * Alarm webhook integration configuration ID.
+         */
+        alarmWebhookIntegrationId: string;
+        /**
+         * Name of the alarm Webhook integration configuration.
+         */
+        alarmWebhookIntegrationName: string;
+        /**
+         * Whether to notify everyone when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookIsAtAll: boolean;
+        /**
+         * End time for receiving alarm notifications. Uses 24-hour format: HH:mm:ss, with a valid range of 00:00:00–23:59:59. StartTime cannot be greater than EndTime.
+         */
+        endTime: string;
+        /**
+         * Custom WebHook request body. It is recommended to set the request body according to the callback interface requirements of the corresponding service.
+         */
+        generalWebhookBody: string;
+        generalWebhookHeaders: outputs.tls.AlarmNotifyGroupNoticeRuleReceiverInfoGeneralWebhookHeader[];
+        /**
+         * Custom callback method for the interface. Only POST or PUT is supported.
+         */
+        generalWebhookMethod: string;
+        /**
+         * Custom callback URL for the interface.
+         */
+        generalWebhookUrl: string;
+        /**
+         * Notification channels. Supports one or more channels. Options: Email, Sms, Phone, GeneralWebhook, Lark, DingTalk, WeChat.
+         */
+        receiverChannels: string[];
+        /**
+         * IAM user or user group name.
+         */
+        receiverNames: string[];
+        /**
+         * Recipient type. Options: User: IAM user; UserGroup: IAM user group.
+         */
+        receiverType: string;
+        /**
+         * Alarm notification start time. Uses 24-hour format (HH:mm:ss), valid range is 00:00:00–23:59:59. StartTime cannot be later than EndTime.
+         */
+        startTime: string;
+    }
+    interface AlarmNotifyGroupNoticeRuleReceiverInfoGeneralWebhookHeader {
+        /**
+         * Custom request header key.
+         */
+        key: string;
+        /**
+         * Custom request header value.
+         */
+        value: string;
+    }
+    interface AlarmNotifyGroupReceiver {
+        /**
+         * Alarm content template ID.
+         */
+        alarmContentTemplateId: string;
+        /**
+         * User group name to notify when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookAtGroups: string[];
+        /**
+         * Username to notify when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookAtUsers: string[];
+        /**
+         * Alarm webhook integration configuration ID.
+         */
+        alarmWebhookIntegrationId: string;
+        /**
+         * Name of the alarm Webhook integration configuration.
+         */
+        alarmWebhookIntegrationName: string;
+        /**
+         * Whether to notify everyone when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookIsAtAll: boolean;
+        /**
+         * End time for receiving alarm notifications. Uses 24-hour format: HH:mm:ss, with a valid range of 00:00:00–23:59:59. StartTime cannot be greater than EndTime.
+         */
+        endTime: string;
+        /**
+         * Custom WebHook request body. It is recommended to set the request body according to the callback interface requirements of the corresponding service.
+         */
+        generalWebhookBody: string;
+        generalWebhookHeaders: outputs.tls.AlarmNotifyGroupReceiverGeneralWebhookHeader[];
+        /**
+         * Custom callback method for the interface. Only POST or PUT is supported.
+         */
+        generalWebhookMethod: string;
+        /**
+         * Custom callback URL for the interface.
+         */
+        generalWebhookUrl: string;
+        /**
+         * Notification channels. Supports one or more channels. Options: Email, Sms, Phone, GeneralWebhook, Lark, DingTalk, WeChat.
+         */
+        receiverChannels: string[];
+        /**
+         * IAM user or user group name.
+         */
+        receiverNames: string[];
+        /**
+         * Recipient type. Options: User: IAM user; UserGroup: IAM user group.
+         */
+        receiverType: string;
+        /**
+         * Alarm notification start time. Uses 24-hour format (HH:mm:ss), valid range is 00:00:00–23:59:59. StartTime cannot be later than EndTime.
+         */
+        startTime: string;
+    }
+    interface AlarmNotifyGroupReceiverGeneralWebhookHeader {
+        /**
+         * Custom request header key.
+         */
+        key: string;
+        /**
+         * Custom request header value.
+         */
+        value: string;
+    }
+    interface GetAlarmNotifyGroupNoticeRule {
+        /**
+         * Whether there is an end node afterwards.
+         */
+        hasEndNode: boolean;
+        /**
+         * Condition for whether to proceed to the next level.
+         */
+        hasNext: boolean;
+        /**
+         * Notification channel information.
+         */
+        receiverInfos: outputs.tls.GetAlarmNotifyGroupNoticeRuleReceiverInfo[];
+        /**
+         * Rule node. JSON format.
+         */
+        ruleNode: string;
+    }
+    interface GetAlarmNotifyGroupNoticeRuleReceiverInfo {
+        /**
+         * Alarm content template ID.
+         */
+        alarmContentTemplateId: string;
+        /**
+         * User group name to notify when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookAtGroups: string[];
+        /**
+         * Username to notify when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookAtUsers: string[];
+        /**
+         * Alarm webhook integration configuration ID.
+         */
+        alarmWebhookIntegrationId: string;
+        /**
+         * Name of the alarm Webhook integration configuration.
+         */
+        alarmWebhookIntegrationName: string;
+        /**
+         * Whether to notify everyone when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookIsAtAll: boolean;
+        /**
+         * End time for receiving alarm notifications. Uses 24-hour format: HH:mm:ss, with a valid range of 00:00:00–23:59:59. StartTime cannot be greater than EndTime.
+         */
+        endTime: string;
+        /**
+         * Custom WebHook request body. It is recommended to set the request body according to the callback interface requirements of the corresponding service.
+         */
+        generalWebhookBody: string;
+        /**
+         * Custom callback request headers for the interface.
+         */
+        generalWebhookHeaders: outputs.tls.GetAlarmNotifyGroupNoticeRuleReceiverInfoGeneralWebhookHeader[];
+        /**
+         * Custom callback method for the interface. Only POST or PUT is supported.
+         */
+        generalWebhookMethod: string;
+        /**
+         * Custom callback URL for the interface.
+         */
+        generalWebhookUrl: string;
+        /**
+         * Notification channels. Supports one or more channels. Options: Email, Sms, Phone, GeneralWebhook, Lark, DingTalk, WeChat.
+         */
+        receiverChannels: string[];
+        /**
+         * IAM user or user group name.
+         */
+        receiverNames: string[];
+        /**
+         * Recipient type. Options: User: IAM user; UserGroup: IAM user group.
+         */
+        receiverType: string;
+        /**
+         * Alarm notification start time. Uses 24-hour format (HH:mm:ss), valid range is 00:00:00–23:59:59. StartTime cannot be later than EndTime.
+         */
+        startTime: string;
+    }
+    interface GetAlarmNotifyGroupNoticeRuleReceiverInfoGeneralWebhookHeader {
+        /**
+         * Custom request header key.
+         */
+        key: string;
+        /**
+         * Custom request header value.
+         */
+        value: string;
+    }
+    interface GetAlarmNotifyGroupReceiver {
+        /**
+         * Alarm content template ID.
+         */
+        alarmContentTemplateId: string;
+        /**
+         * User group name to notify when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookAtGroups: string[];
+        /**
+         * Username to notify when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookAtUsers: string[];
+        /**
+         * Alarm webhook integration configuration ID.
+         */
+        alarmWebhookIntegrationId: string;
+        /**
+         * Name of the alarm Webhook integration configuration.
+         */
+        alarmWebhookIntegrationName: string;
+        /**
+         * Whether to notify everyone when sending notifications to Feishu, DingTalk, or WeCom via Webhook integration.
+         */
+        alarmWebhookIsAtAll: boolean;
+        /**
+         * End time for receiving alarm notifications. Uses 24-hour format: HH:mm:ss, with a valid range of 00:00:00–23:59:59. StartTime cannot be greater than EndTime.
+         */
+        endTime: string;
+        /**
+         * Custom WebHook request body. It is recommended to set the request body according to the callback interface requirements of the corresponding service.
+         */
+        generalWebhookBody: string;
+        /**
+         * Custom callback request headers for the interface.
+         */
+        generalWebhookHeaders: outputs.tls.GetAlarmNotifyGroupReceiverGeneralWebhookHeader[];
+        /**
+         * Custom callback method for the interface. Only POST or PUT is supported.
+         */
+        generalWebhookMethod: string;
+        /**
+         * Custom callback URL for the interface.
+         */
+        generalWebhookUrl: string;
+        /**
+         * Notification channels. Supports one or more channels. Options: Email, Sms, Phone, GeneralWebhook, Lark, DingTalk, WeChat.
+         */
+        receiverChannels: string[];
+        /**
+         * IAM user or user group name.
+         */
+        receiverNames: string[];
+        /**
+         * Recipient type. Options: User: IAM user; UserGroup: IAM user group.
+         */
+        receiverType: string;
+        /**
+         * Alarm notification start time. Uses 24-hour format (HH:mm:ss), valid range is 00:00:00–23:59:59. StartTime cannot be later than EndTime.
+         */
+        startTime: string;
+    }
+    interface GetAlarmNotifyGroupReceiverGeneralWebhookHeader {
+        /**
+         * Custom request header key.
+         */
+        key: string;
+        /**
+         * Custom request header value.
+         */
+        value: string;
+    }
+    interface GetImportTaskImportSourceInfo {
+        /**
+         * Kafka data source information. When sourceType is kafka, the KafkaSourceInfo field is required
+         */
+        kafkaSourceInfo: outputs.tls.GetImportTaskImportSourceInfoKafkaSourceInfo;
+        /**
+         * TOS data source information. When sourceType is tos, the TosSourceInfo field is required.
+         */
+        tosSourceInfo: outputs.tls.GetImportTaskImportSourceInfoTosSourceInfo;
+    }
+    interface GetImportTaskImportSourceInfoKafkaSourceInfo {
+        /**
+         * Data encoding format. Available options: UTF-8, GBK.
+         */
+        encode: string;
+        /**
+         * Kafka consumer group. If not specified, the system will automatically create a Kafka consumer group.
+         */
+        group: string;
+        /**
+         * The service addresses for different types of Kafka clusters vary. Details are as follows: Message Queue Kafka Edition: Use the access point of the Kafka instance. For more information, see Access Point. If the Kafka instance and the Log Service Project are in the same region, you can use private network access; otherwise, use public network access. Self-hosted Kafka clusters: Use the IP address and port number or the domain name and port number of the Kafka Broker. Only public network access is supported. Separate multiple service addresses with a comma (,).
+         */
+        host: string;
+        /**
+         * Starting position for data import. Options: 0: Earliest time, start importing from the first record in the specified Kafka Topic. 1: Latest time, start importing from the most recently generated record in the specified Kafka Topic.
+         */
+        initialOffset: number;
+        /**
+         * If you are using Message Queue Kafka Edition, set this to the Kafka instance ID.
+         */
+        instanceId: string;
+        /**
+         * Whether to enable authentication. If you use a public service address, it is recommended to enable authentication.
+         */
+        isNeedAuth: boolean;
+        /**
+         * Password authentication mechanism. Available options: PLAIN, SCRAM-SHA-256, and SCRAM-SHA-512.
+         */
+        mechanism: string;
+        /**
+         * Kafka SASL user password for authentication.
+         */
+        password: string;
+        /**
+         * Secure transmission protocol. Options include plaintext, sasl*ssl, ssl, and sasl*plaintext
+         */
+        protocol: string;
+        /**
+         * Specify log time. Options: 0: Use Kafka message timestamp. 1: Use current system time.
+         */
+        timeSourceDefault: number;
+        /**
+         * Kafka Topic name. Separate multiple Kafka Topics with commas (,).
+         */
+        topic: string;
+        /**
+         * Kafka SASL username for authentication.
+         */
+        username: string;
+    }
+    interface GetImportTaskImportSourceInfoTosSourceInfo {
+        /**
+         * TOS bucket name
+         */
+        bucket: string;
+        /**
+         * Compression mode for data in the TOS bucket. none: No compression. snappy: Compress using snappy. gzip: Compress using gzip. lz4: Compress using lz4.
+         */
+        compressType: string;
+        /**
+         * Path of the file to be imported in the TOS bucket.
+         */
+        prefix: string;
+        /**
+         * Region where the TOS bucket is located. Cross-region data import is supported
+         */
+        region: string;
+    }
+    interface GetImportTaskTargetInfo {
+        /**
+         * Log extraction rule.
+         */
+        extractRule: outputs.tls.GetImportTaskTargetInfoExtractRule;
+        /**
+         * Log sample. When LogType is set to multiline_log, you must configure log samples. It is recommended to provide more than two log entries as examples to ensure the regular expression matches the first line of each log. Use real samples from the production environment.
+         */
+        logSample: string;
+        /**
+         * Specify log parsing type during import. delimiter*log: CSV type. multiline*log: multiline full text type. minimalist*log: single line full text type. json*log: JSON type.
+         */
+        logType: string;
+        /**
+         * Region.
+         */
+        region: string;
+    }
+    interface GetImportTaskTargetInfoExtractRule {
+        /**
+         * Basic content of log extraction rules.
+         */
+        extractRule: outputs.tls.GetImportTaskTargetInfoExtractRuleExtractRule;
+        /**
+         * Number of skipped rows. Only valid when the log type is delimiterLog and the import type is tos.
+         */
+        skipLineCount: number;
+        /**
+         * Time extraction regular expression, used to extract the time value from the TimeKey field and parse it as the collection time
+         */
+        timeExtractRegex: string;
+        /**
+         * Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC. GMT format: GMT+08:00. UTC format: Asia/Shanghai.
+         */
+        timeZone: string;
+    }
+    interface GetImportTaskTargetInfoExtractRuleExtractRule {
+        /**
+         * Regular expression for identifying the first line of each log. The matched part is treated as the start of the log. When LogType is set to multiline_log, you must configure a log sample
+         */
+        beginRegex: string;
+        /**
+         * Delimiter. Only valid when LogType is delimiter_log.
+         */
+        delimiter: string;
+        /**
+         * Enable nanoseconds.
+         */
+        enableNanosecond: boolean;
+        /**
+         * Filter key regular expression.
+         */
+        filterKeyRegexes: outputs.tls.GetImportTaskTargetInfoExtractRuleExtractRuleFilterKeyRegex[];
+        /**
+         * List of log field names (Key). Valid only when LogType is delimiter_log. Supports up to 100 field names. Duplicate field names are not allowed, and all field names cannot be left blank
+         */
+        keys: string[];
+        /**
+         * Log regular expression
+         */
+        logRegex: string;
+        /**
+         * Log template.
+         */
+        logTemplate: outputs.tls.GetImportTaskTargetInfoExtractRuleExtractRuleLogTemplate;
+        /**
+         * Quotation mark. Content enclosed by the quotation mark will not be separated and will be parsed as a complete field. Only valid when LogType is delimiter_log.
+         */
+        quote: string;
+        /**
+         * Parsing format for the time field. If you use a specified time field in the log as the log timestamp, you must fill in TimeKey and TimeFormat. TimeKey and TimeFormat must be paired. For configuration details, see time format.
+         */
+        timeFormat: string;
+        /**
+         * Name of the log time field. If you use a specific time field in the log as the log timestamp, you must provide both TimeKey and TimeFormat. TimeKey and TimeFormat must appear in pairs
+         */
+        timeKey: string;
+        /**
+         * Time sample. Used to verify whether the entered time parsing format is correct
+         */
+        timeSample: string;
+        /**
+         * When uploading logs that failed to parse, specify the key name for the failed logs. UnMatchUpLoadSwitch=true and UnMatchLogKey must be used together.
+         */
+        unMatchLogKey: string;
+        /**
+         * Whether to upload logs that failed to parse. UnMatchUpLoadSwitch=true and UnMatchLogKey must be paired. true: Upload logs that failed to parse. false: Do not upload logs that failed to parse.
+         */
+        unMatchUpLoadSwitch: boolean;
+    }
+    interface GetImportTaskTargetInfoExtractRuleExtractRuleFilterKeyRegex {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Regular expression.
+         */
+        regex: string;
+    }
+    interface GetImportTaskTargetInfoExtractRuleExtractRuleLogTemplate {
+        /**
+         * Format.
+         */
+        format: string;
+        /**
+         * Type
+         */
+        type: string;
+    }
+    interface GetImportTaskTaskStatistics {
+        /**
+         * Total resource bytes enumerated
+         */
+        bytesTotal: number;
+        /**
+         * Bytes transferred.
+         */
+        bytesTransferred: number;
+        /**
+         * Number of resources failed to import.
+         */
+        failed: number;
+        /**
+         * Number of resources not found.
+         */
+        notExist: number;
+        /**
+         * Number of resources skipped during import
+         */
+        skipped: number;
+        /**
+         * Task status. Status of the import task. Preparing: Preparing for import. Importing: Importing data. Success: Import completed successfully. Failed: Import failed. Stopped: Import paused.
+         */
+        taskStatus: string;
+        /**
+         * Total number of resources enumerated.
+         */
+        total: number;
+        /**
+         * Number of records transferred.
+         */
+        transferred: number;
+    }
+    interface GetIndexFullText {
+        /**
+         * Case sensitivity. true: Case sensitive. false: Not case sensitive.
+         */
+        caseSensitive: boolean;
+        /**
+         * Token separators for the full-text index. Each character in the string represents a token separator. Length: 1–256 bytes. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
+         */
+        delimiter: string;
+        /**
+         * When searching, specify whether to segment Chinese content in logs according to Chinese grammar. The default is false. true: For Chinese characters in logs, segment the log according to common Chinese grammar rules. Custom segmentation symbols for Chinese content are not supported. For non-Chinese characters in logs, segment the log using the segmentation symbols specified in the parameter. false: Segment the log using the segmentation symbols specified in the parameter.
+         */
+        includeChinese: boolean;
+    }
+    interface GetIndexKeyValue {
+        /**
+         * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
+         */
+        key: string;
+        /**
+         * Field description information required for configuring key-value indexes.
+         */
+        value: outputs.tls.GetIndexKeyValueValue;
+    }
+    interface GetIndexKeyValueValue {
+        /**
+         * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
+         */
+        autoIndexFlag: boolean;
+        /**
+         * Whether to distinguish case. Default is false.
+         */
+        caseSensitive: boolean;
+        /**
+         * Token separators for the field. Default is empty (""). Each character in the string represents a token separator. Length: 0–256 bytes. If the length is 0, segmentation is disabled. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
+         */
+        delimiter: string;
+        /**
+         * When searching, determines whether to segment Chinese log content according to Chinese syntax. Enabled: Chinese characters in logs are segmented based on common Chinese syntax; custom segmentation for Chinese content is not supported. Non-Chinese characters in logs are segmented using the token separators specified in the parameter. Disabled: Logs are segmented using the token separators specified in the parameter.
+         */
+        includeChinese: boolean;
+        /**
+         * Create indexes for all fields with text values in the JSON field.
+         */
+        indexAll: boolean;
+        /**
+         * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
+         */
+        indexSqlAll: boolean;
+        /**
+         * When ValueType is json, you can configure key-value indexes for JSON subfields using the JsonKeys field, which is an array of KeyValueInfo. Each element in the JsonKeys list is a KeyValueInfo, and you can further nest text, long, and double type subfields. For subfields in JSON key-value indexes, use . to indicate the hierarchy between JSON fields. For example, the JSON field namelist contains a text-type subfield totalcount and a JSON-type info, which itself contains the field name. Each field name should be configured as totalcount and info.name, respectively. The SqlFlag setting for subfield key-value indexes defined in JsonKeys must match their parent field, meaning they must be enabled or disabled together. The default is disabled. Subfields do not support separate settings for Delimiter, CaseSensitive, or IncludeChinese. For text-type fields, CaseSensitive, Delimiter, and IncludeChinese always inherit the parent field settings. This is only set when ValueType is json.
+         */
+        jsonKeys: outputs.tls.GetIndexKeyValueValueJsonKey[];
+        /**
+         * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
+         */
+        sqlFlag: boolean;
+        /**
+         * Field type. Currently supports long, double, text, and json. The long and double types do not support configuring delimiters, including Chinese, or case sensitivity. Only the json type supports further configuration of JsonKeys subfields.
+         */
+        valueType: string;
+    }
+    interface GetIndexKeyValueValueJsonKey {
+        /**
+         * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
+         */
+        key: string;
+        /**
+         * Field description information required for configuring key-value indexes.
+         */
+        value: outputs.tls.GetIndexKeyValueValueJsonKeyValue;
+    }
+    interface GetIndexKeyValueValueJsonKeyValue {
+        /**
+         * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
+         */
+        autoIndexFlag: boolean;
+        /**
+         * Whether to distinguish case. Default is false.
+         */
+        caseSensitive: boolean;
+        /**
+         * Token separators for the field. Default is empty (""). Each character in the string represents a token separator. Length: 0–256 bytes. If the length is 0, segmentation is disabled. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
+         */
+        delimiter: string;
+        /**
+         * When searching, determines whether to segment Chinese log content according to Chinese syntax. Enabled: Chinese characters in logs are segmented based on common Chinese syntax; custom segmentation for Chinese content is not supported. Non-Chinese characters in logs are segmented using the token separators specified in the parameter. Disabled: Logs are segmented using the token separators specified in the parameter.
+         */
+        includeChinese: boolean;
+        /**
+         * Create indexes for all fields with text values in the JSON field.
+         */
+        indexAll: boolean;
+        /**
+         * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
+         */
+        indexSqlAll: boolean;
+        /**
+         * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
+         */
+        sqlFlag: boolean;
+        /**
+         * Field type. Currently supports long, double, text, and json. The long and double types do not support configuring delimiters, including Chinese, or case sensitivity. Only the json type supports further configuration of JsonKeys subfields.
+         */
+        valueType: string;
+    }
+    interface GetIndexUserInnerKeyValue {
+        /**
+         * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
+         */
+        key: string;
+        /**
+         * Field description information required for configuring key-value indexes.
+         */
+        value: outputs.tls.GetIndexUserInnerKeyValueValue;
+    }
+    interface GetIndexUserInnerKeyValueValue {
+        /**
+         * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
+         */
+        autoIndexFlag: boolean;
+        /**
+         * Whether to distinguish case. Default is false.
+         */
+        caseSensitive: boolean;
+        /**
+         * Token separators for the field. Default is empty (""). Each character in the string represents a token separator. Length: 0–256 bytes. If the length is 0, segmentation is disabled. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
+         */
+        delimiter: string;
+        /**
+         * When searching, determines whether to segment Chinese log content according to Chinese syntax. Enabled: Chinese characters in logs are segmented based on common Chinese syntax; custom segmentation for Chinese content is not supported. Non-Chinese characters in logs are segmented using the token separators specified in the parameter. Disabled: Logs are segmented using the token separators specified in the parameter.
+         */
+        includeChinese: boolean;
+        /**
+         * Create indexes for all fields with text values in the JSON field.
+         */
+        indexAll: boolean;
+        /**
+         * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
+         */
+        indexSqlAll: boolean;
+        /**
+         * When ValueType is json, you can configure key-value indexes for JSON subfields using the JsonKeys field, which is an array of KeyValueInfo. Each element in the JsonKeys list is a KeyValueInfo, and you can further nest text, long, and double type subfields. For subfields in JSON key-value indexes, use . to indicate the hierarchy between JSON fields. For example, the JSON field namelist contains a text-type subfield totalcount and a JSON-type info, which itself contains the field name. Each field name should be configured as totalcount and info.name, respectively. The SqlFlag setting for subfield key-value indexes defined in JsonKeys must match their parent field, meaning they must be enabled or disabled together. The default is disabled. Subfields do not support separate settings for Delimiter, CaseSensitive, or IncludeChinese. For text-type fields, CaseSensitive, Delimiter, and IncludeChinese always inherit the parent field settings. This is only set when ValueType is json.
+         */
+        jsonKeys: outputs.tls.GetIndexUserInnerKeyValueValueJsonKey[];
+        /**
+         * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
+         */
+        sqlFlag: boolean;
+        /**
+         * Field type. Currently supports long, double, text, and json. The long and double types do not support configuring delimiters, including Chinese, or case sensitivity. Only the json type supports further configuration of JsonKeys subfields.
+         */
+        valueType: string;
+    }
+    interface GetIndexUserInnerKeyValueValueJsonKey {
+        /**
+         * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
+         */
+        key: string;
+        /**
+         * Field description information required for configuring key-value indexes.
+         */
+        value: outputs.tls.GetIndexUserInnerKeyValueValueJsonKeyValue;
+    }
+    interface GetIndexUserInnerKeyValueValueJsonKeyValue {
+        /**
+         * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
+         */
+        autoIndexFlag: boolean;
+        /**
+         * Whether to distinguish case. Default is false.
+         */
+        caseSensitive: boolean;
+        /**
+         * Token separators for the field. Default is empty (""). Each character in the string represents a token separator. Length: 0–256 bytes. If the length is 0, segmentation is disabled. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
+         */
+        delimiter: string;
+        /**
+         * When searching, determines whether to segment Chinese log content according to Chinese syntax. Enabled: Chinese characters in logs are segmented based on common Chinese syntax; custom segmentation for Chinese content is not supported. Non-Chinese characters in logs are segmented using the token separators specified in the parameter. Disabled: Logs are segmented using the token separators specified in the parameter.
+         */
+        includeChinese: boolean;
+        /**
+         * Create indexes for all fields with text values in the JSON field.
+         */
+        indexAll: boolean;
+        /**
+         * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
+         */
+        indexSqlAll: boolean;
+        /**
+         * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
+         */
+        sqlFlag: boolean;
+        /**
+         * Field type. Currently supports long, double, text, and json. The long and double types do not support configuring delimiters, including Chinese, or case sensitivity. Only the json type supports further configuration of JsonKeys subfields.
+         */
+        valueType: string;
+    }
+    interface GetProjectTag {
+        /**
+         * Tag key
+         */
+        key: string;
+        /**
+         * Tag value
+         */
+        value: string;
+    }
+    interface GetRuleContainerRule {
+        /**
+         * Container name to collect. If no container name is specified, all containers in the machine group will be collected. Supports regex matching; for example, setting the container name to ^(container-test)$ will collect all containers named container-test.
+         */
+        containerNameRegex: string;
+        /**
+         * Whether to add environment variables as log tags to the raw log data. When enabled, the log service adds container environment variable 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 container has the environment variable source=DC, the log will include the field **tag**data_source_*: DC
+         */
+        envTags: outputs.tls.GetRuleContainerRuleEnvTag[];
+        /**
+         * The container environment variable denylist specifies which containers are excluded from collection. If the denylist is not enabled, all containers are collected. When the container environment variable denylist is enabled, Key is required and Value is optional. If Value is empty, all containers whose environment variables contain the Key are excluded from collection. If Value is not empty, only containers with a matching key-value pair are excluded, meaning only containers whose environment variables contain the Key and whose value matches the Value are excluded. Value supports regular expressions. For example, if Key is set to module and Value is set to ^(tcp|udp)$, containers with environment variables module:tcp or module:udp are excluded from collection. Multiple key-value pairs are evaluated with a logical OR, so any container environment variable matching any key-value pair will be excluded from collection. When the container environment variable denylist is enabled, Keys must be unique.
+         */
+        excludeContainerEnvRegexes: outputs.tls.GetRuleContainerRuleExcludeContainerEnvRegex[];
+        /**
+         * Container label denylist specifies containers to exclude from collection. If the denylist is not enabled, all containers will be collected. If the container label denylist is enabled, Key is required and Value is optional. If Value is empty, all containers with the Key in their label will be excluded. If Value is not empty, only containers matching the key-value pair will be excluded—that is, containers with the Key in their label and a Value matching the specified pattern. Value supports regex matching; for example, set Key to app and Value to ^(test1|test2)$ to exclude containers with labels app:test1 and app:test2. Multiple key-value pairs use logical OR; any container label matching any pair will be excluded from collection. When the container label denylist is enabled, Keys must not be duplicated.
+         */
+        excludeContainerLabelRegexes: outputs.tls.GetRuleContainerRuleExcludeContainerLabelRegex[];
+        /**
+         * The container environment variable allowlist specifies which containers to collect using container environment variables. 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, all containers containing the Key in their environment variables are collected. If Value is not empty, only containers with the Key in their environment variables and a Value matching the specified value are collected. Value supports regular expression matching. For example, if Key is set to module and Value is set to ^(tcp|udp)$, only containers with module:tcp or module:udp in their environment variables are collected. The logical relationship between multiple key-value pairs is OR, meaning 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.
+         */
+        includeContainerEnvRegexes: outputs.tls.GetRuleContainerRuleIncludeContainerEnvRegex[];
+        /**
+         * 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 specify key-value pairs. Key is required and Value is optional. If Value is empty, all containers whose labels contain the Key are collected. If Value is not empty, only containers whose labels contain the Key and whose value matches the Value are collected. Value supports regular expressions. For example, if Key is set to app and Value is set to ^(test1|test2)$, only containers with labels app:test1 or app:test2 are collected. Multiple key-value pairs are evaluated with a logical OR, so any container label matching any key-value pair will be included in the collection scope. When the container label allowlist is enabled, Keys must be unique.
+         */
+        includeContainerLabelRegexes: outputs.tls.GetRuleContainerRuleIncludeContainerLabelRegex[];
+        /**
+         * Kubernetes container collection rules.
+         */
+        kubernetesRule: outputs.tls.GetRuleContainerRuleKubernetesRule;
+        /**
+         * Collection information. stdout: Collects container standard output (stdout). stderr: Collects container standard error (stderr). all: Collects both container standard output (stdout) and standard error (stderr).
+         */
+        stream: string;
+    }
+    interface GetRuleContainerRuleEnvTag {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleExcludeContainerEnvRegex {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleExcludeContainerLabelRegex {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleIncludeContainerEnvRegex {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleIncludeContainerLabelRegex {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleKubernetesRule {
+        /**
+         * Whether to add Kubernetes Annotations as log tags to the original log data. When enabled, the log service will add fields related to Kubernetes Pod Annotations to the logs. Setting multiple key-value pairs means adding multiple fields. For example, if you set Key to sink and Value to data_sink, and the Pod contains the annotation sink=ck, a new field **tag**data_sink_*: ck will be added to the log.
+         */
+        annotationTags: outputs.tls.GetRuleContainerRuleKubernetesRuleAnnotationTag[];
+        /**
+         * Whether to add all Kubernetes Labels as log tags to the original log data. When enabled, the log service adds fields for all Labels in the Kubernetes Pod to the logs. For example, if the Pod contains Label source=DC and destination=CS, the logs will include fields **tag**source__: DC and **tag**destination__: CS.
+         */
+        enableAllLabelTag: boolean;
+        /**
+         * 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 specified Key are excluded. If Value is not empty, only containers under Pods whose Pod Annotation contains the Key and whose value matches the specified Value are excluded. By default, Value uses string matching, meaning it only matches when Value and the Pod Annotation value are exactly the same. If the value starts with ^ and ends with $, it is treated as a regular expression. For example, if Key is set to app and Value is set to ^(test1|test2)$, it matches containers under Pods with Pod Annotation app:test1 or app:test2. Note: The logical relationship between multiple Key-Value pairs is OR, meaning a Pod Annotation that matches any pair will be excluded from the collection scope. When enabling the Pod Annotation Denylist, Keys must not be duplicated. For regex fuzzy matching, you must add .*. For example, ^(http.*)$ matches strings starting with http
+         */
+        excludePodAnnotationRegexes: outputs.tls.GetRuleContainerRuleKubernetesRuleExcludePodAnnotationRegex[];
+        /**
+         * 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 their Pod Label are excluded from collection. If Value is not empty, only containers with the specified Key and a Value matching the Value in their Pod Label are excluded. Value supports regular expressions. For example, set Key to module and Value to ^(tcp|udp)$ to exclude containers with module:tcp or module:udp in their Pod Label. Note: The logical relationship between multiple Key-Value pairs is OR. Any Pod Label matching any Key-Value pair will be excluded from collection. When enabling the Pod Label denylist, Keys must not be duplicated. For fuzzy regular expression matching, you must add .*. For example, ^(http.*)$ matches any string starting with http
+         */
+        excludePodLabelRegexes: outputs.tls.GetRuleContainerRuleKubernetesRuleExcludePodLabelRegex[];
+        /**
+         * Pod Annotation Allowlist is used to specify containers to be collected. If you need to set a Pod Annotation Allowlist, Key is required and Value is optional. If Value is empty, all containers under Pods that contain the Key in Pod Annotation will match. If Value is not empty, only containers under Pods that contain the Key and whose value matches Value in Pod Annotation will match. Value defaults to string matching, meaning only when Value and the Pod Annotation value are exactly the same will they match. If the value starts with ^ and ends with $, it is a regex match. For example, set Key to app and Value to ^(test1|test2)$ to match containers under Pods with Pod Annotation app:test1 or app:test2. Note: The logical relationship between multiple Key-Value pairs is OR, meaning as long as Pod Annotation matches any pair, it will be included in the collection scope. When enabling Pod Annotation Allowlist, Keys must not be duplicated. For regex fuzzy matching, you must add .*. For example, ^(http.*)$ matches strings starting with http.
+         */
+        includePodAnnotationRegexes: outputs.tls.GetRuleContainerRuleKubernetesRuleIncludePodAnnotationRegex[];
+        /**
+         * Pod Label Allowlist is used to specify which containers to collect. If Pod Label Allowlist is not enabled, all containers will be collected. If you need to set a Pod Label Allowlist, Key is required: if Value is empty, all containers with the Key in their Pod Label will be collected. If Value is not empty, only containers with the Key in their Pod Label and a Value matching the specified pattern will be collected; regular expression matching is supported. For example, if you set Key to module and Value to ^(tcp|udp)$, only containers with module:tcp or module:udp in their Pod Label will be collected. Note: The logical relationship between multiple key-value pairs is OR, meaning any Pod Label matching any key-value pair will be included in the collection scope. When enabling Pod Label Allowlist, Keys cannot be duplicated. For fuzzy regular expression matching, you must add .*, for example, ^(http.*)$ matches strings starting with http.
+         */
+        includePodLabelRegexes: outputs.tls.GetRuleContainerRuleKubernetesRuleIncludePodLabelRegex[];
+        /**
+         * Whether to add Kubernetes labels as log tags to the raw 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, if you set Key to source and Value to data_source, and the Pod contains the label source=DC, the log will include the field **tag**data_source_*: DC.
+         */
+        labelTags: outputs.tls.GetRuleContainerRuleKubernetesRuleLabelTag[];
+        /**
+         * Name of the Kubernetes Namespace to collect. If no Namespace name is specified, all containers will be collected. Namespace names support regular expression matching. For example, if you set the Namespace name to ^(tcp|udp)$, it will collect all containers under the tcp and udp namespaces.
+         */
+        namespaceNameRegex: string;
+        /**
+         * Pod name is used to specify the Pod whose containers will be collected. If no Pod name is specified, all containers will be collected. Pod name supports regular expression matching. For example, setting the Pod name to ^(http.*)$ collects all containers under Pods whose names start with http.
+         */
+        podNameRegex: 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.
+         */
+        workloadNameRegex: string;
+        /**
+         * Specify the container 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: Deployment: stateless workload StatefulSet: stateful workload DaemonSet: daemon process Job: task CronJob: scheduled task
+         */
+        workloadType: string;
+    }
+    interface GetRuleContainerRuleKubernetesRuleAnnotationTag {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleKubernetesRuleExcludePodAnnotationRegex {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleKubernetesRuleExcludePodLabelRegex {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleKubernetesRuleIncludePodAnnotationRegex {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleKubernetesRuleIncludePodLabelRegex {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleContainerRuleKubernetesRuleLabelTag {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleExcludePath {
+        /**
+         * Collection path type. File: File name. Path: Directory.
+         */
+        type: 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.
          */
         value: string;
     }
-    interface VolumeTotalPerformance {
+    interface GetRuleExtractRule {
+        /**
+         * Regular expression that the first line of the log must match. Valid only when LogType is multiline*log or fullregex*log. Must be a valid regular expression.
+         */
+        beginRegex: string;
+        /**
+         * Log delimiter. Valid only when LogType is delimiter_log.
+         */
+        delimiter: string;
+        /**
+         * Enable nanosecond precision time. When enabled, log time parsing will include and report nanosecond precision. true: Enable nanosecond precision time. false: Disable nanosecond precision time.
+         */
+        enableNanosecond: boolean;
+        /**
+         * Filter rule list. When LogType is minimalist*log or multiline*log, you can configure up to 1 filter rule, and the filter field name key must be content. When LogType is delimiter*log, json*log, or fullregex*log, you can configure up to 5 filter rules, and the filter field name key cannot be duplicated or empty. The regular expression for the filter field's log content must be a valid regular expression and is limited to 256 characters.
+         */
+        filterKeyRegexes: outputs.tls.GetRuleExtractRuleFilterKeyRegex[];
+        /**
+         * List of log field names (Key). This is only valid when LogType is delimiter*log or fullregex*log. You can configure up to 100 field names. When LogType is delimiter*log, field names must be unique and cannot all be empty. When LogType is fullregex*log, field names must be unique and cannot be empty.
+         */
+        keys: string[];
+        /**
+         * The entire log must match the specified regular expression. This is only valid when the collected log type is fullregex_log. Must be a valid regular expression.
+         */
+        logRegex: string;
+        /**
+         * Automatically extract log fields based on the specified log template
+         */
+        logTemplate: outputs.tls.GetRuleExtractRuleLogTemplate;
+        /**
+         * Quoting character. Content wrapped by a quoting character will not be split but parsed as a complete field. Only valid when LogType is delimiter_log.
+         */
+        quote: string;
+        /**
+         * Regular expression for extracting time, used to extract the time value from the TimeKey field and parse it as the collection time
+         */
+        timeExtractRegex: string;
+        /**
+         * Parsing format for the time field. If you use a specific time field in the log as the log timestamp, you must provide both TimeKey and TimeFormat. TimeKey and TimeFormat must be used together.
+         */
+        timeFormat: string;
+        /**
+         * Name of the log time field. If you want to use a specific time field in the log as the log timestamp, you need to specify both TimeKey and TimeFormat. TimeKey and TimeFormat must be provided together.
+         */
+        timeKey: string;
+        /**
+         * Time sample. Used to check whether the entered time parsing format is correct.
+         */
+        timeSample: string;
+        /**
+         * Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC. GMT format: GMT+08:00. UTC format: Asia/Shanghai.
+         */
+        timeZone: string;
+        /**
+         * Key name for unmatched logs.
+         */
+        unMatchLogKey: string;
+        /**
+         * Switch for uploading unmatched logs.
+         */
+        unMatchUpLoadSwitch: boolean;
+    }
+    interface GetRuleExtractRuleFilterKeyRegex {
+        /**
+         * Name of the filter field.
+         */
+        key: string;
+        /**
+         * The log content of the filter field must match the specified regular expression.
+         */
+        regex: string;
+    }
+    interface GetRuleExtractRuleLogTemplate {
+        /**
+         * Log template format.
+         */
+        format: string;
+        /**
+         * Log template types. Supported types: Nginx: Nginx log template.
+         */
+        type: string;
+    }
+    interface GetRuleHostGroupInfo {
+        /**
+         * Number of hosts with heartbeat exceptions.
+         */
+        abnormalHeartbeatStatusCount: number;
+        /**
+         * Latest agent version.
+         */
+        agentLatestVersion: string;
+        /**
+         * Whether LogCollector installed on the machine group server has automatic upgrade enabled. true: The log service will check for upgrades during a specified time period each day. If upgrade conditions are met, LogCollector will be upgraded automatically without manual intervention. false (default): LogCollector does not upgrade automatically. To use a newer version of LogCollector, refer to the LogCollector upgrade procedure.
+         */
+        autoUpdate: boolean;
+        /**
+         * Machine group creation time.
+         */
+        createTime: string;
+        /**
+         * Number of hosts.
+         */
+        hostCount: number;
+        /**
+         * Machine group ID
+         */
+        hostGroupId: string;
+        /**
+         * Name of the machine group.
+         */
+        hostGroupName: string;
+        /**
+         * Machine group type. IP: Machine IP. Label: Machine label.
+         */
+        hostGroupType: string;
+        /**
+         * Machine identifier.
+         */
+        hostIdentifier: string;
+        /**
+         * The IAM project to which the host group belongs.
+         */
+        iamProjectName: string;
+        /**
+         * Time when the machine group was modified.
+         */
+        modifyTime: string;
+        /**
+         * Number of hosts with normal heartbeat.
+         */
+        normalHeartbeatStatusCount: number;
+        /**
+         * The number of bound collection configurations.
+         */
+        ruleCount: number;
+        /**
+         * Whether to enable the Logcollector service log feature. true: enabled. false (default): disabled.
+         */
+        serviceLogging: boolean;
+        /**
+         * End time for LogCollector automatic upgrade.
+         */
+        updateEndTime: string;
+        /**
+         * LogCollector auto-update start time. Note: Only required when AutoUpdate is set to true. It is recommended to schedule auto-updates during off-peak hours. LogCollector may restart during the update process, but logs will not be lost.
+         */
+        updateStartTime: string;
+    }
+    interface GetRuleUserDefineRule {
+        /**
+         * The Advanced parameter is 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 release conditions are specified, the handle is released and log file monitoring ends as soon as any condition is met.
+         */
+        advanced: outputs.tls.GetRuleUserDefineRuleAdvanced;
+        /**
+         * Whether to upload the label information of the host group to the log service. The default is off. 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): Host group label information is not uploaded.
+         */
+        enableHostGroupLabel: boolean;
+        /**
+         * Upload the hostname field. Default is disabled. true: Add a field to the original log to record the source hostname. Specify the hostname field name using HostnameKey. false: (default) Do not add the hostname field.
+         */
+        enableHostname: boolean;
+        /**
+         * Upload raw logs. true: Upload raw logs. false (default): Do not upload raw logs.
+         */
+        enableRawLog: boolean;
+        /**
+         * Add constant fields to logs. Constant fields must follow these restrictions: You can upload up to 5 constant fields. Field names (Key) must be unique and not empty. Length limit: 1–128 characters, including letters, numbers, and special characters (-*./), and cannot start with an underscore. Field values (Value) must not be empty, with a maximum length of 512 KiB.
+         */
+        fields: outputs.tls.GetRuleUserDefineRuleField[];
+        /**
+         * Field name used to store machine group label information
+         */
+        hostGroupLabelKey: string;
+        /**
+         * Hostname field name. Required only when EnableHostname is true.
+         */
+        hostnameKey: string;
+        /**
+         * Ignore log files that have not been updated for a specified period (in hours).
+         */
+        ignoreOlder: number;
+        /**
+         * Allow multiple log file collections. Empty: Use log file ID (including file inode, device, and checksum of the first N bytes) to uniquely identify the log file. RuleID: Use collection rule ID and log file ID to uniquely identify the log file. TopicIDRuleName: Use log topic ID, collection rule name, and log file ID to uniquely identify the log file.
+         */
+        multiCollectsType: string;
+        /**
+         * Rule for parsing the collection path. After setting the rule, fields in the collection path are extracted using the specified regular expression and added as metadata to the log data. Note: This parameter is not supported when collecting container standard output.
+         */
+        parsePathRule: outputs.tls.GetRuleUserDefineRuleParsePathRule;
+        /**
+         * LogCollector plugin configuration. After enabling plugin configuration, you can add one or more LogCollector processor plugins to parse logs with complex or variable structures.
+         */
+        plugin: outputs.tls.GetRuleUserDefineRulePlugin;
+        /**
+         * Name of the raw log field. 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 along with the parsed log data.
+         */
+        rawLogKey: string;
+        /**
+         * 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 this parameter is set, logs are collected using the HashKey routing Shard mode, and the log service writes data to the Shard containing the specified Key value
+         */
+        shardHashKey: outputs.tls.GetRuleUserDefineRuleShardHashKey;
+        /**
+         * LogCollector collection policy, which specifies whether LogCollector collects incremental logs or full logs. Default is false, meaning full log collection. true: incremental collection. LogCollector only collects newly added content in the file. When new logs are written to monitored log files, LogCollector triggers log collection. For first-time collection, 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 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, collecting only incremental logs. For subsequent collections, LogCollector determines the collection position based on Checkpoint and continues collecting. false: (default) full collection. LogCollector collects logs from the beginning of each file, including historical log data.
+         */
+        tailFiles: boolean;
+        /**
+         * Backtracking threshold for incremental collection, 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 that is TailSizeKb from the end of the file.
+         */
+        tailSizeKb: number;
+    }
+    interface GetRuleUserDefineRuleAdvanced {
+        /**
+         * After reading to the end of the log file, choose whether to release the file handle. Default is false.
+         */
+        closeEof: boolean;
+        /**
+         * Wait time to release log file handle. If no new logs are written to the log file within the specified time, the handle for that log file is released. Unit: seconds. Range: 1–300 seconds. Default: 60 seconds.
+         */
+        closeInactive: number;
+        /**
+         * Release the file handle after the log file is removed. Default is false.
+         */
+        closeRemoved: boolean;
+        /**
+         * Release the file handle after the log file is renamed. Default is false.
+         */
+        closeRenamed: boolean;
+        /**
+         * Maximum monitoring duration for LogCollector log files, in seconds. The default is 0 seconds, meaning LogCollector does not limit the monitoring duration for log files. Timing starts when LogCollector begins monitoring the log file. Once the specified duration is exceeded, LogCollector immediately releases the file handle and stops monitoring, regardless of whether the log file has been fully read.
+         */
+        closeTimeout: number;
+        /**
+         * Maximum wait time when LogCollector does not detect a line break, in seconds. The default is 5s. Timing starts when LogCollector begins reading the log file. If no line break is detected within the specified time, LogCollector sends the logs in the buffer. If the file write interval is long, a complete log entry may be split into two parts and written separately. Adjust this parameter based on your log write interval.
+         */
+        noLineTerminatorEofMaxTime: number;
+    }
+    interface GetRuleUserDefineRuleField {
+        /**
+         * Key.
+         */
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
+    }
+    interface GetRuleUserDefineRuleParsePathRule {
+        /**
+         * Field name list. The log service uses a regular expression (Regex) to parse the path sample (PathSample) into multiple fields. Keys specify the name of each field. You can configure up to 100 field names. Field names cannot be empty or duplicated.
+         */
+        keys: string[];
+        /**
+         * Sample collection path for actual scenarios. The sample collection path must be an absolute path. Wildcards *, ?, ** are not allowed in the path sample.
+         */
+        pathSample: string;
+        /**
+         * Regular expression used to extract the path field. Must match the sample collection path, otherwise extraction will fail
+         */
+        regex: string;
+    }
+    interface GetRuleUserDefineRulePlugin {
+        /**
+         * LogCollector plugin. For the list of supported plugins and parameter descriptions, see LogCollector plugin overview.
+         */
+        processors: string;
+    }
+    interface GetRuleUserDefineRuleShardHashKey {
+        /**
+         * HashKey of the log group, used to specify the shard to which the current log group will be written. The value range for this parameter is [00000000000000000000000000000000-ffffffffffffffffffffffffffffffff).
+         */
+        hashKey: string;
+    }
+    interface GetScheduleSqlTaskRequestCycle {
         /**
-         * Total IOPS of the disk, which is the sum of the baseline IOPS and extra IOPS.
+         * Cron expression, with a minimum granularity of minutes, using 24-hour format. For example, 0 18 * * * means execution at 18:00 every day.
          */
-        iops: number;
+        cronTab: string;
         /**
-         * The total throughput of the cloud disk is the sum of its baseline throughput and additional throughput.
+         * If Type is set to Cron, you must also set the time zone.
          */
-        throughput: number;
+        cronTimeZone: string;
+        /**
+         * Scheduling period or the time point for periodic execution (minutes from 00:00). Range: 1–1440 minutes.
+         */
+        time: number;
+        /**
+         * Scheduling period type. Options: Period, Fixed, Cron.
+         */
+        type: string;
     }
-}
-export declare namespace tls {
-    interface GetImportTaskImportSourceInfo {
+    interface GetShipperContentInfo {
+        /**
+         * CSV format log content configuration.
+         */
+        csvInfo: outputs.tls.GetShipperContentInfoCsvInfo;
+        /**
+         * Log content parsing format. Delivery to TOS supports json, jsonl, csv; delivery to Kafka supports original, json.
+         */
+        format: string;
+        /**
+         * JSON/JSONL format log content configuration.
+         */
+        jsonInfo: outputs.tls.GetShipperContentInfoJsonInfo;
+    }
+    interface GetShipperContentInfoCsvInfo {
+        /**
+         * Delimiter. Supports comma, tab, pipe, semicolon, space.
+         */
+        delimiter: string;
+        /**
+         * Escape character. When field content contains a delimiter, use an escape character to enclose it. Supports single quote, double quote, or empty character.
+         */
+        escapeChar: string;
+        /**
+         * Fields to be delivered. Supports letters, numbers, and _-./. Cannot start with an underscore. Length: 1–128.
+         */
+        keys: string[];
+        /**
+         * Content for invalid field padding. Length: 0–128.
+         */
+        nonFieldContent: string;
+        /**
+         * Whether to print the key in the first row.
+         */
+        printHeader: boolean;
+    }
+    interface GetShipperContentInfoJsonInfo {
+        /**
+         * Enable flag.
+         */
+        enable: boolean;
+        /**
+         * Whether to enable escaping. Must be set to true.
+         */
+        escape: boolean;
+        /**
+         * Delivery field list; if not configured, all fields will be delivered. When delivering in JSON/JSONL format, if this parameter is not set, all fields will be delivered, including **content** (required), **source**, **path**, **time**, **image_name**, **container_name**, **pod_name**, **pod_uid**, namespace, **tag****client_ip**, and **tag****receive_time**.
+         */
+        keys: string[];
+    }
+    interface GetShipperKafkaShipperInfo {
+        /**
+         * Compression format; supports snappy, gzip, lz4, none.
+         */
+        compress: string;
+        /**
+         * Delivery end time, in milliseconds. If not set, delivery continues indefinitely. Note: Milliseconds will be truncated. For example, if 1776761323455 is entered, it will become 1776761323000; if 1776761323 is entered, it will become 1776761323000.
+         */
+        endTime: number;
+        /**
+         * Kafka instance.
+         */
+        instance: string;
+        /**
+         * Kafka topic name. All log data delivered through this configuration will be sent to this topic.
+         */
+        kafkaTopic: string;
+        /**
+         * Start time. If not configured, defaults to the current time. Note: Millisecond data will be ignored. For example, if 1776761323455 is entered, the result will be 1776761323000; if 1776761323 is entered, the result will be 1776761323000.
+         */
+        startTime: number;
+    }
+    interface GetShipperTosShipperInfo {
+        /**
+         * Select a TOS bucket. Must be in the same region as the source log topic. Can only contain numbers, hyphens (-), and letters a–z. Must start and end with a number or letter. Length: 3–63 characters.
+         */
+        bucket: string;
+        /**
+         * Compression format; supports snappy, gzip, lz4, none.
+         */
+        compress: string;
+        /**
+         * Delivery interval in seconds, range: 300–900.
+         */
+        interval: number;
+        /**
+         * Maximum raw file size per partition for delivery, in MiB. Range: 5–256.
+         */
+        maxSize: number;
+        /**
+         * Partition rule for log delivery. Subdirectory naming format supports strftime syntax. Default: %Y/%m/%d/%H/%M.
+         */
+        partitionFormat: string;
+        /**
+         * Top-level directory name for the bucket. Cannot start with / or \, and cannot use consecutive /. Cannot use .. as a folder name. Duplicate names are not allowed within the same bucket.
+         */
+        prefix: string;
+    }
+    interface GetTopicTag {
+        /**
+         * User tag key.
+         */
+        key: string;
+        /**
+         * User tag value.
+         */
+        value: string;
+    }
+    interface ImportTaskImportSourceInfo {
         /**
          * Kafka data source information. When sourceType is kafka, the KafkaSourceInfo field is required
          */
-        kafkaSourceInfo: outputs.tls.GetImportTaskImportSourceInfoKafkaSourceInfo;
+        kafkaSourceInfo: outputs.tls.ImportTaskImportSourceInfoKafkaSourceInfo;
         /**
          * TOS data source information. When sourceType is tos, the TosSourceInfo field is required.
          */
-        tosSourceInfo: outputs.tls.GetImportTaskImportSourceInfoTosSourceInfo;
+        tosSourceInfo: outputs.tls.ImportTaskImportSourceInfoTosSourceInfo;
     }
-    interface GetImportTaskImportSourceInfoKafkaSourceInfo {
+    interface ImportTaskImportSourceInfoKafkaSourceInfo {
         /**
          * Data encoding format. Available options: UTF-8, GBK.
          */
@@ -18060,7 +19848,7 @@ export declare namespace tls {
          */
         username: string;
     }
-    interface GetImportTaskImportSourceInfoTosSourceInfo {
+    interface ImportTaskImportSourceInfoTosSourceInfo {
         /**
          * TOS bucket name
          */
@@ -18078,11 +19866,11 @@ export declare namespace tls {
          */
         region: string;
     }
-    interface GetImportTaskTargetInfo {
+    interface ImportTaskTargetInfo {
         /**
          * Log extraction rule.
          */
-        extractRule: outputs.tls.GetImportTaskTargetInfoExtractRule;
+        extractRule: outputs.tls.ImportTaskTargetInfoExtractRule;
         /**
          * Log sample. When LogType is set to multiline_log, you must configure log samples. It is recommended to provide more than two log entries as examples to ensure the regular expression matches the first line of each log. Use real samples from the production environment.
          */
@@ -18096,11 +19884,11 @@ export declare namespace tls {
          */
         region: string;
     }
-    interface GetImportTaskTargetInfoExtractRule {
+    interface ImportTaskTargetInfoExtractRule {
         /**
          * Basic content of log extraction rules.
          */
-        extractRule: outputs.tls.GetImportTaskTargetInfoExtractRuleExtractRule;
+        extractRule: outputs.tls.ImportTaskTargetInfoExtractRuleExtractRule;
         /**
          * Number of skipped rows. Only valid when the log type is delimiterLog and the import type is tos.
          */
@@ -18114,7 +19902,7 @@ export declare namespace tls {
          */
         timeZone: string;
     }
-    interface GetImportTaskTargetInfoExtractRuleExtractRule {
+    interface ImportTaskTargetInfoExtractRuleExtractRule {
         /**
          * Regular expression for identifying the first line of each log. The matched part is treated as the start of the log. When LogType is set to multiline_log, you must configure a log sample
          */
@@ -18127,10 +19915,7 @@ export declare namespace tls {
          * Enable nanoseconds.
          */
         enableNanosecond: boolean;
-        /**
-         * Filter key regular expression.
-         */
-        filterKeyRegexes: outputs.tls.GetImportTaskTargetInfoExtractRuleExtractRuleFilterKeyRegex[];
+        filterKeyRegexes: outputs.tls.ImportTaskTargetInfoExtractRuleExtractRuleFilterKeyRegex[];
         /**
          * List of log field names (Key). Valid only when LogType is delimiter_log. Supports up to 100 field names. Duplicate field names are not allowed, and all field names cannot be left blank
          */
@@ -18142,7 +19927,7 @@ export declare namespace tls {
         /**
          * Log template.
          */
-        logTemplate: outputs.tls.GetImportTaskTargetInfoExtractRuleExtractRuleLogTemplate;
+        logTemplate: outputs.tls.ImportTaskTargetInfoExtractRuleExtractRuleLogTemplate;
         /**
          * Quotation mark. Content enclosed by the quotation mark will not be separated and will be parsed as a complete field. Only valid when LogType is delimiter_log.
          */
@@ -18168,7 +19953,7 @@ export declare namespace tls {
          */
         unMatchUpLoadSwitch: boolean;
     }
-    interface GetImportTaskTargetInfoExtractRuleExtractRuleFilterKeyRegex {
+    interface ImportTaskTargetInfoExtractRuleExtractRuleFilterKeyRegex {
         /**
          * Key.
          */
@@ -18178,7 +19963,7 @@ export declare namespace tls {
          */
         regex: string;
     }
-    interface GetImportTaskTargetInfoExtractRuleExtractRuleLogTemplate {
+    interface ImportTaskTargetInfoExtractRuleExtractRuleLogTemplate {
         /**
          * Format.
          */
@@ -18188,7 +19973,7 @@ export declare namespace tls {
          */
         type: string;
     }
-    interface GetImportTaskTaskStatistics {
+    interface ImportTaskTaskStatistics {
         /**
          * Total resource bytes enumerated
          */
@@ -18222,7 +20007,7 @@ export declare namespace tls {
          */
         transferred: number;
     }
-    interface GetIndexFullText {
+    interface IndexFullText {
         /**
          * Case sensitivity. true: Case sensitive. false: Not case sensitive.
          */
@@ -18236,7 +20021,7 @@ export declare namespace tls {
          */
         includeChinese: boolean;
     }
-    interface GetIndexKeyValue {
+    interface IndexKeyValue {
         /**
          * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
          */
@@ -18244,9 +20029,9 @@ export declare namespace tls {
         /**
          * Field description information required for configuring key-value indexes.
          */
-        value: outputs.tls.GetIndexKeyValueValue;
+        value: outputs.tls.IndexKeyValueValue;
     }
-    interface GetIndexKeyValueValue {
+    interface IndexKeyValueValue {
         /**
          * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
          */
@@ -18271,10 +20056,7 @@ export declare namespace tls {
          * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
          */
         indexSqlAll: boolean;
-        /**
-         * When ValueType is json, you can configure key-value indexes for JSON subfields using the JsonKeys field, which is an array of KeyValueInfo. Each element in the JsonKeys list is a KeyValueInfo, and you can further nest text, long, and double type subfields. For subfields in JSON key-value indexes, use . to indicate the hierarchy between JSON fields. For example, the JSON field namelist contains a text-type subfield totalcount and a JSON-type info, which itself contains the field name. Each field name should be configured as totalcount and info.name, respectively. The SqlFlag setting for subfield key-value indexes defined in JsonKeys must match their parent field, meaning they must be enabled or disabled together. The default is disabled. Subfields do not support separate settings for Delimiter, CaseSensitive, or IncludeChinese. For text-type fields, CaseSensitive, Delimiter, and IncludeChinese always inherit the parent field settings. This is only set when ValueType is json.
-         */
-        jsonKeys: outputs.tls.GetIndexKeyValueValueJsonKey[];
+        jsonKeys: outputs.tls.IndexKeyValueValueJsonKey[];
         /**
          * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
          */
@@ -18284,7 +20066,7 @@ export declare namespace tls {
          */
         valueType: string;
     }
-    interface GetIndexKeyValueValueJsonKey {
+    interface IndexKeyValueValueJsonKey {
         /**
          * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
          */
@@ -18292,9 +20074,9 @@ export declare namespace tls {
         /**
          * Field description information required for configuring key-value indexes.
          */
-        value: outputs.tls.GetIndexKeyValueValueJsonKeyValue;
+        value: outputs.tls.IndexKeyValueValueJsonKeyValue;
     }
-    interface GetIndexKeyValueValueJsonKeyValue {
+    interface IndexKeyValueValueJsonKeyValue {
         /**
          * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
          */
@@ -18328,7 +20110,7 @@ export declare namespace tls {
          */
         valueType: string;
     }
-    interface GetIndexUserInnerKeyValue {
+    interface IndexUserInnerKeyValue {
         /**
          * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
          */
@@ -18336,9 +20118,9 @@ export declare namespace tls {
         /**
          * Field description information required for configuring key-value indexes.
          */
-        value: outputs.tls.GetIndexUserInnerKeyValueValue;
+        value: outputs.tls.IndexUserInnerKeyValueValue;
     }
-    interface GetIndexUserInnerKeyValueValue {
+    interface IndexUserInnerKeyValueValue {
         /**
          * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
          */
@@ -18363,10 +20145,7 @@ export declare namespace tls {
          * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
          */
         indexSqlAll: boolean;
-        /**
-         * When ValueType is json, you can configure key-value indexes for JSON subfields using the JsonKeys field, which is an array of KeyValueInfo. Each element in the JsonKeys list is a KeyValueInfo, and you can further nest text, long, and double type subfields. For subfields in JSON key-value indexes, use . to indicate the hierarchy between JSON fields. For example, the JSON field namelist contains a text-type subfield totalcount and a JSON-type info, which itself contains the field name. Each field name should be configured as totalcount and info.name, respectively. The SqlFlag setting for subfield key-value indexes defined in JsonKeys must match their parent field, meaning they must be enabled or disabled together. The default is disabled. Subfields do not support separate settings for Delimiter, CaseSensitive, or IncludeChinese. For text-type fields, CaseSensitive, Delimiter, and IncludeChinese always inherit the parent field settings. This is only set when ValueType is json.
-         */
-        jsonKeys: outputs.tls.GetIndexUserInnerKeyValueValueJsonKey[];
+        jsonKeys: outputs.tls.IndexUserInnerKeyValueValueJsonKey[];
         /**
          * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
          */
@@ -18376,7 +20155,7 @@ export declare namespace tls {
          */
         valueType: string;
     }
-    interface GetIndexUserInnerKeyValueValueJsonKey {
+    interface IndexUserInnerKeyValueValueJsonKey {
         /**
          * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
          */
@@ -18384,9 +20163,9 @@ export declare namespace tls {
         /**
          * Field description information required for configuring key-value indexes.
          */
-        value: outputs.tls.GetIndexUserInnerKeyValueValueJsonKeyValue;
+        value: outputs.tls.IndexUserInnerKeyValueValueJsonKeyValue;
     }
-    interface GetIndexUserInnerKeyValueValueJsonKeyValue {
+    interface IndexUserInnerKeyValueValueJsonKeyValue {
         /**
          * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
          */
@@ -18420,7 +20199,7 @@ export declare namespace tls {
          */
         valueType: string;
     }
-    interface GetProjectTag {
+    interface ProjectTag {
         /**
          * Tag key
          */
@@ -18430,472 +20209,494 @@ export declare namespace tls {
          */
         value: string;
     }
-    interface GetScheduleSqlTaskRequestCycle {
-        /**
-         * Cron expression, with a minimum granularity of minutes, using 24-hour format. For example, 0 18 * * * means execution at 18:00 every day.
-         */
-        cronTab: string;
+    interface RuleContainerRule {
         /**
-         * If Type is set to Cron, you must also set the time zone.
+         * Container name to collect. If no container name is specified, all containers in the machine group will be collected. Supports regex matching; for example, setting the container name to ^(container-test)$ will collect all containers named container-test.
          */
-        cronTimeZone: string;
+        containerNameRegex: string;
+        envTags: outputs.tls.RuleContainerRuleEnvTag[];
+        excludeContainerEnvRegexes: outputs.tls.RuleContainerRuleExcludeContainerEnvRegex[];
+        excludeContainerLabelRegexes: outputs.tls.RuleContainerRuleExcludeContainerLabelRegex[];
+        includeContainerEnvRegexes: outputs.tls.RuleContainerRuleIncludeContainerEnvRegex[];
+        includeContainerLabelRegexes: outputs.tls.RuleContainerRuleIncludeContainerLabelRegex[];
         /**
-         * Scheduling period or the time point for periodic execution (minutes from 00:00). Range: 1–1440 minutes.
+         * Kubernetes container collection rules.
          */
-        time: number;
+        kubernetesRule: outputs.tls.RuleContainerRuleKubernetesRule;
         /**
-         * Scheduling period type. Options: Period, Fixed, Cron.
+         * Collection information. stdout: Collects container standard output (stdout). stderr: Collects container standard error (stderr). all: Collects both container standard output (stdout) and standard error (stderr).
          */
-        type: string;
+        stream: string;
     }
-    interface GetTopicTag {
+    interface RuleContainerRuleEnvTag {
         /**
-         * User tag key.
+         * Key.
          */
         key: string;
         /**
-         * User tag value.
+         * Value.
          */
-        value: string;
+        val: string;
     }
-    interface ImportTaskImportSourceInfo {
+    interface RuleContainerRuleExcludeContainerEnvRegex {
         /**
-         * Kafka data source information. When sourceType is kafka, the KafkaSourceInfo field is required
+         * Key.
          */
-        kafkaSourceInfo: outputs.tls.ImportTaskImportSourceInfoKafkaSourceInfo;
+        key: string;
         /**
-         * TOS data source information. When sourceType is tos, the TosSourceInfo field is required.
+         * Value.
          */
-        tosSourceInfo: outputs.tls.ImportTaskImportSourceInfoTosSourceInfo;
+        val: string;
     }
-    interface ImportTaskImportSourceInfoKafkaSourceInfo {
+    interface RuleContainerRuleExcludeContainerLabelRegex {
         /**
-         * Data encoding format. Available options: UTF-8, GBK.
+         * Key.
          */
-        encode: string;
+        key: string;
         /**
-         * Kafka consumer group. If not specified, the system will automatically create a Kafka consumer group.
+         * Value.
          */
-        group: string;
+        val: string;
+    }
+    interface RuleContainerRuleIncludeContainerEnvRegex {
         /**
-         * The service addresses for different types of Kafka clusters vary. Details are as follows: Message Queue Kafka Edition: Use the access point of the Kafka instance. For more information, see Access Point. If the Kafka instance and the Log Service Project are in the same region, you can use private network access; otherwise, use public network access. Self-hosted Kafka clusters: Use the IP address and port number or the domain name and port number of the Kafka Broker. Only public network access is supported. Separate multiple service addresses with a comma (,).
+         * Key.
          */
-        host: string;
+        key: string;
         /**
-         * Starting position for data import. Options: 0: Earliest time, start importing from the first record in the specified Kafka Topic. 1: Latest time, start importing from the most recently generated record in the specified Kafka Topic.
+         * Value.
          */
-        initialOffset: number;
+        val: string;
+    }
+    interface RuleContainerRuleIncludeContainerLabelRegex {
         /**
-         * If you are using Message Queue Kafka Edition, set this to the Kafka instance ID.
+         * Key.
          */
-        instanceId: string;
+        key: string;
         /**
-         * Whether to enable authentication. If you use a public service address, it is recommended to enable authentication.
+         * Value.
          */
-        isNeedAuth: boolean;
+        val: string;
+    }
+    interface RuleContainerRuleKubernetesRule {
+        annotationTags: outputs.tls.RuleContainerRuleKubernetesRuleAnnotationTag[];
         /**
-         * Password authentication mechanism. Available options: PLAIN, SCRAM-SHA-256, and SCRAM-SHA-512.
+         * Whether to add all Kubernetes Labels as log tags to the original log data. When enabled, the log service adds fields for all Labels in the Kubernetes Pod to the logs. For example, if the Pod contains Label source=DC and destination=CS, the logs will include fields **tag**source__: DC and **tag**destination__: CS.
          */
-        mechanism: string;
+        enableAllLabelTag: boolean;
+        excludePodAnnotationRegexes: outputs.tls.RuleContainerRuleKubernetesRuleExcludePodAnnotationRegex[];
+        excludePodLabelRegexes: outputs.tls.RuleContainerRuleKubernetesRuleExcludePodLabelRegex[];
+        includePodAnnotationRegexes: outputs.tls.RuleContainerRuleKubernetesRuleIncludePodAnnotationRegex[];
+        includePodLabelRegexes: outputs.tls.RuleContainerRuleKubernetesRuleIncludePodLabelRegex[];
+        labelTags: outputs.tls.RuleContainerRuleKubernetesRuleLabelTag[];
         /**
-         * Kafka SASL user password for authentication.
+         * Name of the Kubernetes Namespace to collect. If no Namespace name is specified, all containers will be collected. Namespace names support regular expression matching. For example, if you set the Namespace name to ^(tcp|udp)$, it will collect all containers under the tcp and udp namespaces.
          */
-        password: string;
+        namespaceNameRegex: string;
         /**
-         * Secure transmission protocol. Options include plaintext, sasl*ssl, ssl, and sasl*plaintext
+         * Pod name is used to specify the Pod whose containers will be collected. If no Pod name is specified, all containers will be collected. Pod name supports regular expression matching. For example, setting the Pod name to ^(http.*)$ collects all containers under Pods whose names start with http.
          */
-        protocol: string;
+        podNameRegex: string;
         /**
-         * Specify log time. Options: 0: Use Kafka message timestamp. 1: Use current system time.
+         * 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.
          */
-        timeSourceDefault: number;
+        workloadNameRegex: string;
         /**
-         * Kafka Topic name. Separate multiple Kafka Topics with commas (,).
+         * Specify the container 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: Deployment: stateless workload StatefulSet: stateful workload DaemonSet: daemon process Job: task CronJob: scheduled task
          */
-        topic: string;
+        workloadType: string;
+    }
+    interface RuleContainerRuleKubernetesRuleAnnotationTag {
         /**
-         * Kafka SASL username for authentication.
+         * Key.
          */
-        username: string;
+        key: string;
+        /**
+         * Value.
+         */
+        val: string;
     }
-    interface ImportTaskImportSourceInfoTosSourceInfo {
+    interface RuleContainerRuleKubernetesRuleExcludePodAnnotationRegex {
         /**
-         * TOS bucket name
+         * Key.
          */
-        bucket: string;
+        key: string;
         /**
-         * Compression mode for data in the TOS bucket. none: No compression. snappy: Compress using snappy. gzip: Compress using gzip. lz4: Compress using lz4.
+         * Value.
          */
-        compressType: string;
+        val: string;
+    }
+    interface RuleContainerRuleKubernetesRuleExcludePodLabelRegex {
         /**
-         * Path of the file to be imported in the TOS bucket.
+         * Key.
          */
-        prefix: string;
+        key: string;
         /**
-         * Region where the TOS bucket is located. Cross-region data import is supported
+         * Value.
          */
-        region: string;
+        val: string;
     }
-    interface ImportTaskTargetInfo {
+    interface RuleContainerRuleKubernetesRuleIncludePodAnnotationRegex {
         /**
-         * Log extraction rule.
+         * Key.
          */
-        extractRule: outputs.tls.ImportTaskTargetInfoExtractRule;
+        key: string;
         /**
-         * Log sample. When LogType is set to multiline_log, you must configure log samples. It is recommended to provide more than two log entries as examples to ensure the regular expression matches the first line of each log. Use real samples from the production environment.
+         * Value.
          */
-        logSample: string;
+        val: string;
+    }
+    interface RuleContainerRuleKubernetesRuleIncludePodLabelRegex {
         /**
-         * Specify log parsing type during import. delimiter*log: CSV type. multiline*log: multiline full text type. minimalist*log: single line full text type. json*log: JSON type.
+         * Key.
          */
-        logType: string;
+        key: string;
         /**
-         * Region.
+         * Value.
          */
-        region: string;
+        val: string;
     }
-    interface ImportTaskTargetInfoExtractRule {
+    interface RuleContainerRuleKubernetesRuleLabelTag {
         /**
-         * Basic content of log extraction rules.
+         * Key.
          */
-        extractRule: outputs.tls.ImportTaskTargetInfoExtractRuleExtractRule;
+        key: string;
         /**
-         * Number of skipped rows. Only valid when the log type is delimiterLog and the import type is tos.
+         * Value.
          */
-        skipLineCount: number;
+        val: string;
+    }
+    interface RuleExcludePath {
         /**
-         * Time extraction regular expression, used to extract the time value from the TimeKey field and parse it as the collection time
+         * Collection path type. File: File name. Path: Directory.
          */
-        timeExtractRegex: string;
+        type: string;
         /**
-         * Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC. GMT format: GMT+08:00. UTC format: Asia/Shanghai.
+         * 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.
          */
-        timeZone: string;
+        value: string;
     }
-    interface ImportTaskTargetInfoExtractRuleExtractRule {
+    interface RuleExtractRule {
         /**
-         * Regular expression for identifying the first line of each log. The matched part is treated as the start of the log. When LogType is set to multiline_log, you must configure a log sample
+         * Regular expression that the first line of the log must match. Valid only when LogType is multiline*log or fullregex*log. Must be a valid regular expression.
          */
         beginRegex: string;
         /**
-         * Delimiter. Only valid when LogType is delimiter_log.
+         * Log delimiter. Valid only when LogType is delimiter_log.
          */
         delimiter: string;
         /**
-         * Enable nanoseconds.
+         * Enable nanosecond precision time. When enabled, log time parsing will include and report nanosecond precision. true: Enable nanosecond precision time. false: Disable nanosecond precision time.
          */
         enableNanosecond: boolean;
-        filterKeyRegexes: outputs.tls.ImportTaskTargetInfoExtractRuleExtractRuleFilterKeyRegex[];
+        filterKeyRegexes: outputs.tls.RuleExtractRuleFilterKeyRegex[];
         /**
-         * List of log field names (Key). Valid only when LogType is delimiter_log. Supports up to 100 field names. Duplicate field names are not allowed, and all field names cannot be left blank
+         * List of log field names (Key). This is only valid when LogType is delimiter*log or fullregex*log. You can configure up to 100 field names. When LogType is delimiter*log, field names must be unique and cannot all be empty. When LogType is fullregex*log, field names must be unique and cannot be empty.
          */
         keys: string[];
         /**
-         * Log regular expression
+         * The entire log must match the specified regular expression. This is only valid when the collected log type is fullregex_log. Must be a valid regular expression.
          */
         logRegex: string;
         /**
-         * Log template.
+         * Automatically extract log fields based on the specified log template
          */
-        logTemplate: outputs.tls.ImportTaskTargetInfoExtractRuleExtractRuleLogTemplate;
+        logTemplate: outputs.tls.RuleExtractRuleLogTemplate;
         /**
-         * Quotation mark. Content enclosed by the quotation mark will not be separated and will be parsed as a complete field. Only valid when LogType is delimiter_log.
+         * Quoting character. Content wrapped by a quoting character will not be split but parsed as a complete field. Only valid when LogType is delimiter_log.
          */
         quote: string;
         /**
-         * Parsing format for the time field. If you use a specified time field in the log as the log timestamp, you must fill in TimeKey and TimeFormat. TimeKey and TimeFormat must be paired. For configuration details, see time format.
+         * Regular expression for extracting time, used to extract the time value from the TimeKey field and parse it as the collection time
+         */
+        timeExtractRegex: string;
+        /**
+         * Parsing format for the time field. If you use a specific time field in the log as the log timestamp, you must provide both TimeKey and TimeFormat. TimeKey and TimeFormat must be used together.
          */
         timeFormat: string;
         /**
-         * Name of the log time field. If you use a specific time field in the log as the log timestamp, you must provide both TimeKey and TimeFormat. TimeKey and TimeFormat must appear in pairs
+         * Name of the log time field. If you want to use a specific time field in the log as the log timestamp, you need to specify both TimeKey and TimeFormat. TimeKey and TimeFormat must be provided together.
          */
         timeKey: string;
         /**
-         * Time sample. Used to verify whether the entered time parsing format is correct
+         * Time sample. Used to check whether the entered time parsing format is correct.
          */
         timeSample: string;
         /**
-         * When uploading logs that failed to parse, specify the key name for the failed logs. UnMatchUpLoadSwitch=true and UnMatchLogKey must be used together.
+         * Time zone. Supports machine time zone (default) and custom time zone. Custom time zone supports GMT and UTC. GMT format: GMT+08:00. UTC format: Asia/Shanghai.
+         */
+        timeZone: string;
+        /**
+         * Key name for unmatched logs.
          */
         unMatchLogKey: string;
         /**
-         * Whether to upload logs that failed to parse. UnMatchUpLoadSwitch=true and UnMatchLogKey must be paired. true: Upload logs that failed to parse. false: Do not upload logs that failed to parse.
+         * Switch for uploading unmatched logs.
          */
         unMatchUpLoadSwitch: boolean;
     }
-    interface ImportTaskTargetInfoExtractRuleExtractRuleFilterKeyRegex {
+    interface RuleExtractRuleFilterKeyRegex {
         /**
-         * Key.
+         * Name of the filter field.
          */
         key: string;
         /**
-         * Regular expression.
+         * The log content of the filter field must match the specified regular expression.
          */
         regex: string;
     }
-    interface ImportTaskTargetInfoExtractRuleExtractRuleLogTemplate {
+    interface RuleExtractRuleLogTemplate {
         /**
-         * Format.
+         * Log template format.
          */
         format: string;
         /**
-         * Type
+         * Log template types. Supported types: Nginx: Nginx log template.
          */
         type: string;
     }
-    interface ImportTaskTaskStatistics {
+    interface RuleHostGroupInfo {
         /**
-         * Total resource bytes enumerated
+         * Machine group ID
          */
-        bytesTotal: number;
+        hostGroupId: string;
+    }
+    interface RuleUserDefineRule {
         /**
-         * Bytes transferred.
+         * The Advanced parameter is 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 release conditions are specified, the handle is released and log file monitoring ends as soon as any condition is met.
          */
-        bytesTransferred: number;
+        advanced: outputs.tls.RuleUserDefineRuleAdvanced;
         /**
-         * Number of resources failed to import.
+         * Whether to upload the label information of the host group to the log service. The default is off. 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): Host group label information is not uploaded.
          */
-        failed: number;
+        enableHostGroupLabel: boolean;
         /**
-         * Number of resources not found.
+         * Upload the hostname field. Default is disabled. true: Add a field to the original log to record the source hostname. Specify the hostname field name using HostnameKey. false: (default) Do not add the hostname field.
          */
-        notExist: number;
+        enableHostname: boolean;
         /**
-         * Number of resources skipped during import
+         * Upload raw logs. true: Upload raw logs. false (default): Do not upload raw logs.
          */
-        skipped: number;
+        enableRawLog: boolean;
+        fields: outputs.tls.RuleUserDefineRuleField[];
         /**
-         * Task status. Status of the import task. Preparing: Preparing for import. Importing: Importing data. Success: Import completed successfully. Failed: Import failed. Stopped: Import paused.
+         * Field name used to store machine group label information
          */
-        taskStatus: string;
+        hostGroupLabelKey: string;
         /**
-         * Total number of resources enumerated.
+         * Hostname field name. Required only when EnableHostname is true.
          */
-        total: number;
+        hostnameKey: string;
         /**
-         * Number of records transferred.
+         * Ignore log files that have not been updated for a specified period (in hours).
          */
-        transferred: number;
-    }
-    interface IndexFullText {
+        ignoreOlder: number;
         /**
-         * Case sensitivity. true: Case sensitive. false: Not case sensitive.
+         * Allow multiple log file collections. Empty: Use log file ID (including file inode, device, and checksum of the first N bytes) to uniquely identify the log file. RuleID: Use collection rule ID and log file ID to uniquely identify the log file. TopicIDRuleName: Use log topic ID, collection rule name, and log file ID to uniquely identify the log file.
          */
-        caseSensitive: boolean;
+        multiCollectsType: string;
         /**
-         * Token separators for the full-text index. Each character in the string represents a token separator. Length: 1–256 bytes. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
+         * Rule for parsing the collection path. After setting the rule, fields in the collection path are extracted using the specified regular expression and added as metadata to the log data. Note: This parameter is not supported when collecting container standard output.
          */
-        delimiter: string;
+        parsePathRule: outputs.tls.RuleUserDefineRuleParsePathRule;
         /**
-         * When searching, specify whether to segment Chinese content in logs according to Chinese grammar. The default is false. true: For Chinese characters in logs, segment the log according to common Chinese grammar rules. Custom segmentation symbols for Chinese content are not supported. For non-Chinese characters in logs, segment the log using the segmentation symbols specified in the parameter. false: Segment the log using the segmentation symbols specified in the parameter.
+         * LogCollector plugin configuration. After enabling plugin configuration, you can add one or more LogCollector processor plugins to parse logs with complex or variable structures.
          */
-        includeChinese: boolean;
-    }
-    interface IndexKeyValue {
+        plugin: outputs.tls.RuleUserDefineRulePlugin;
         /**
-         * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
+         * Name of the raw log field. 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 along with the parsed log data.
          */
-        key: string;
+        rawLogKey: string;
         /**
-         * Field description information required for configuring key-value indexes.
+         * 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 this parameter is set, logs are collected using the HashKey routing Shard mode, and the log service writes data to the Shard containing the specified Key value
          */
-        value: outputs.tls.IndexKeyValueValue;
-    }
-    interface IndexKeyValueValue {
+        shardHashKey: outputs.tls.RuleUserDefineRuleShardHashKey;
         /**
-         * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
+         * LogCollector collection policy, which specifies whether LogCollector collects incremental logs or full logs. Default is false, meaning full log collection. true: incremental collection. LogCollector only collects newly added content in the file. When new logs are written to monitored log files, LogCollector triggers log collection. For first-time collection, 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 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, collecting only incremental logs. For subsequent collections, LogCollector determines the collection position based on Checkpoint and continues collecting. false: (default) full collection. LogCollector collects logs from the beginning of each file, including historical log data.
          */
-        autoIndexFlag: boolean;
+        tailFiles: boolean;
         /**
-         * Whether to distinguish case. Default is false.
+         * Backtracking threshold for incremental collection, 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 that is TailSizeKb from the end of the file.
          */
-        caseSensitive: boolean;
+        tailSizeKb: number;
+    }
+    interface RuleUserDefineRuleAdvanced {
         /**
-         * Token separators for the field. Default is empty (""). Each character in the string represents a token separator. Length: 0–256 bytes. If the length is 0, segmentation is disabled. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
+         * After reading to the end of the log file, choose whether to release the file handle. Default is false.
          */
-        delimiter: string;
+        closeEof: boolean;
         /**
-         * When searching, determines whether to segment Chinese log content according to Chinese syntax. Enabled: Chinese characters in logs are segmented based on common Chinese syntax; custom segmentation for Chinese content is not supported. Non-Chinese characters in logs are segmented using the token separators specified in the parameter. Disabled: Logs are segmented using the token separators specified in the parameter.
+         * Wait time to release log file handle. If no new logs are written to the log file within the specified time, the handle for that log file is released. Unit: seconds. Range: 1–300 seconds. Default: 60 seconds.
          */
-        includeChinese: boolean;
+        closeInactive: number;
         /**
-         * Create indexes for all fields with text values in the JSON field.
+         * Release the file handle after the log file is removed. Default is false.
          */
-        indexAll: boolean;
+        closeRemoved: boolean;
         /**
-         * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
+         * Release the file handle after the log file is renamed. Default is false.
          */
-        indexSqlAll: boolean;
-        jsonKeys: outputs.tls.IndexKeyValueValueJsonKey[];
+        closeRenamed: boolean;
         /**
-         * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
+         * Maximum monitoring duration for LogCollector log files, in seconds. The default is 0 seconds, meaning LogCollector does not limit the monitoring duration for log files. Timing starts when LogCollector begins monitoring the log file. Once the specified duration is exceeded, LogCollector immediately releases the file handle and stops monitoring, regardless of whether the log file has been fully read.
          */
-        sqlFlag: boolean;
+        closeTimeout: number;
         /**
-         * Field type. Currently supports long, double, text, and json. The long and double types do not support configuring delimiters, including Chinese, or case sensitivity. Only the json type supports further configuration of JsonKeys subfields.
+         * Maximum wait time when LogCollector does not detect a line break, in seconds. The default is 5s. Timing starts when LogCollector begins reading the log file. If no line break is detected within the specified time, LogCollector sends the logs in the buffer. If the file write interval is long, a complete log entry may be split into two parts and written separately. Adjust this parameter based on your log write interval.
          */
-        valueType: string;
+        noLineTerminatorEofMaxTime: number;
     }
-    interface IndexKeyValueValueJsonKey {
+    interface RuleUserDefineRuleField {
         /**
-         * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
+         * Key.
          */
         key: string;
         /**
-         * Field description information required for configuring key-value indexes.
+         * Value.
          */
-        value: outputs.tls.IndexKeyValueValueJsonKeyValue;
+        val: string;
     }
-    interface IndexKeyValueValueJsonKeyValue {
+    interface RuleUserDefineRuleParsePathRule {
         /**
-         * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
-         */
-        autoIndexFlag: boolean;
-        /**
-         * Whether to distinguish case. Default is false.
-         */
-        caseSensitive: boolean;
-        /**
-         * Token separators for the field. Default is empty (""). Each character in the string represents a token separator. Length: 0–256 bytes. If the length is 0, segmentation is disabled. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
-         */
-        delimiter: string;
-        /**
-         * When searching, determines whether to segment Chinese log content according to Chinese syntax. Enabled: Chinese characters in logs are segmented based on common Chinese syntax; custom segmentation for Chinese content is not supported. Non-Chinese characters in logs are segmented using the token separators specified in the parameter. Disabled: Logs are segmented using the token separators specified in the parameter.
+         * Field name list. The log service uses a regular expression (Regex) to parse the path sample (PathSample) into multiple fields. Keys specify the name of each field. You can configure up to 100 field names. Field names cannot be empty or duplicated.
          */
-        includeChinese: boolean;
+        keys: string[];
         /**
-         * Create indexes for all fields with text values in the JSON field.
+         * Sample collection path for actual scenarios. The sample collection path must be an absolute path. Wildcards *, ?, ** are not allowed in the path sample.
          */
-        indexAll: boolean;
+        pathSample: string;
         /**
-         * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
+         * Regular expression used to extract the path field. Must match the sample collection path, otherwise extraction will fail
          */
-        indexSqlAll: boolean;
+        regex: string;
+    }
+    interface RuleUserDefineRulePlugin {
         /**
-         * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
+         * LogCollector plugin. For the list of supported plugins and parameter descriptions, see LogCollector plugin overview.
          */
-        sqlFlag: boolean;
+        processors: string;
+    }
+    interface RuleUserDefineRuleShardHashKey {
         /**
-         * Field type. Currently supports long, double, text, and json. The long and double types do not support configuring delimiters, including Chinese, or case sensitivity. Only the json type supports further configuration of JsonKeys subfields.
+         * HashKey of the log group, used to specify the shard to which the current log group will be written. The value range for this parameter is [00000000000000000000000000000000-ffffffffffffffffffffffffffffffff).
          */
-        valueType: string;
+        hashKey: string;
     }
-    interface IndexUserInnerKeyValue {
+    interface ScheduleSqlTaskRequestCycle {
         /**
-         * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
+         * Cron expression, with a minimum granularity of minutes, using 24-hour format. For example, 0 18 * * * means execution at 18:00 every day.
          */
-        key: string;
+        cronTab: string;
         /**
-         * Field description information required for configuring key-value indexes.
+         * If Type is set to Cron, you must also set the time zone.
          */
-        value: outputs.tls.IndexUserInnerKeyValueValue;
-    }
-    interface IndexUserInnerKeyValueValue {
+        cronTimeZone: string;
         /**
-         * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
+         * Scheduling period or the time point for periodic execution (minutes from 00:00). Range: 1–1440 minutes.
          */
-        autoIndexFlag: boolean;
+        time: number;
         /**
-         * Whether to distinguish case. Default is false.
+         * Scheduling period type. Options: Period, Fixed, Cron.
          */
-        caseSensitive: boolean;
+        type: string;
+    }
+    interface ShipperContentInfo {
         /**
-         * Token separators for the field. Default is empty (""). Each character in the string represents a token separator. Length: 0–256 bytes. If the length is 0, segmentation is disabled. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
+         * CSV format log content configuration.
          */
-        delimiter: string;
+        csvInfo: outputs.tls.ShipperContentInfoCsvInfo;
         /**
-         * When searching, determines whether to segment Chinese log content according to Chinese syntax. Enabled: Chinese characters in logs are segmented based on common Chinese syntax; custom segmentation for Chinese content is not supported. Non-Chinese characters in logs are segmented using the token separators specified in the parameter. Disabled: Logs are segmented using the token separators specified in the parameter.
+         * Log content parsing format. Delivery to TOS supports json, jsonl, csv; delivery to Kafka supports original, json.
          */
-        includeChinese: boolean;
+        format: string;
         /**
-         * Create indexes for all fields with text values in the JSON field.
+         * JSON/JSONL format log content configuration.
          */
-        indexAll: boolean;
+        jsonInfo: outputs.tls.ShipperContentInfoJsonInfo;
+    }
+    interface ShipperContentInfoCsvInfo {
         /**
-         * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
+         * Delimiter. Supports comma, tab, pipe, semicolon, space.
          */
-        indexSqlAll: boolean;
-        jsonKeys: outputs.tls.IndexUserInnerKeyValueValueJsonKey[];
+        delimiter: string;
         /**
-         * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
+         * Escape character. When field content contains a delimiter, use an escape character to enclose it. Supports single quote, double quote, or empty character.
          */
-        sqlFlag: boolean;
+        escapeChar: string;
         /**
-         * Field type. Currently supports long, double, text, and json. The long and double types do not support configuring delimiters, including Chinese, or case sensitivity. Only the json type supports further configuration of JsonKeys subfields.
+         * Fields to be delivered. Supports letters, numbers, and _-./. Cannot start with an underscore. Length: 1–128.
          */
-        valueType: string;
-    }
-    interface IndexUserInnerKeyValueValueJsonKey {
+        keys: string[];
         /**
-         * Specify the field names for key-value indexing. Up to 100 fields can be added. Only letters, numbers, spaces, underscores (_), hyphens (-), and slashes (/) are supported, and field names cannot start or end with a space. Each key name must be unique within the same index. Length: 1–128 characters. For subfields in JSON-type key-value indexes, use a dot (.) to indicate the hierarchy between JSON fields. For example, if the JSON field 'namelist' contains a text-type subfield 'totalcount' and a JSON-type subfield 'info', and 'info' contains the field 'name', the field names should be configured as 'totalcount' and 'info.name' respectively.
+         * Content for invalid field padding. Length: 0–128.
          */
-        key: string;
+        nonFieldContent: string;
         /**
-         * Field description information required for configuring key-value indexes.
+         * Whether to print the key in the first row.
          */
-        value: outputs.tls.IndexUserInnerKeyValueValueJsonKeyValue;
+        printHeader: boolean;
     }
-    interface IndexUserInnerKeyValueValueJsonKeyValue {
+    interface ShipperContentInfoJsonInfo {
         /**
-         * Indicates whether the index was added automatically. true: The index was added automatically. false: The index was not added automatically.
+         * Enable flag.
          */
-        autoIndexFlag: boolean;
+        enable: boolean;
         /**
-         * Whether to distinguish case. Default is false.
+         * Whether to enable escaping. Must be set to true.
          */
-        caseSensitive: boolean;
+        escape: boolean;
         /**
-         * Token separators for the field. Default is empty (""). Each character in the string represents a token separator. Length: 0–256 bytes. If the length is 0, segmentation is disabled. Only one or more of the following characters are supported: letters, numbers, and !@#%^&*()-_=\\"', <>/?|;:\	\r[]{}. . Supports configuring both Chinese characters and token separators simultaneously.
+         * Delivery field list; if not configured, all fields will be delivered. When delivering in JSON/JSONL format, if this parameter is not set, all fields will be delivered, including **content** (required), **source**, **path**, **time**, **image_name**, **container_name**, **pod_name**, **pod_uid**, namespace, **tag****client_ip**, and **tag****receive_time**.
          */
-        delimiter: string;
+        keys: string[];
+    }
+    interface ShipperKafkaShipperInfo {
         /**
-         * When searching, determines whether to segment Chinese log content according to Chinese syntax. Enabled: Chinese characters in logs are segmented based on common Chinese syntax; custom segmentation for Chinese content is not supported. Non-Chinese characters in logs are segmented using the token separators specified in the parameter. Disabled: Logs are segmented using the token separators specified in the parameter.
+         * Compression format; supports snappy, gzip, lz4, none.
          */
-        includeChinese: boolean;
+        compress: string;
         /**
-         * Create indexes for all fields with text values in the JSON field.
+         * Delivery end time, in milliseconds. If not set, delivery continues indefinitely. Note: Milliseconds will be truncated. For example, if 1776761323455 is entered, it will become 1776761323000; if 1776761323 is entered, it will become 1776761323000.
          */
-        indexAll: boolean;
+        endTime: number;
         /**
-         * Enable automatic indexing and statistics for JSON fields. true: Enable automatic indexing and statistics. false: Disable automatic indexing and statistics.
+         * Kafka instance.
          */
-        indexSqlAll: boolean;
+        instance: string;
         /**
-         * Whether analysis is enabled for the field. Default is false. After enabling statistical analysis, you can configure token delimiters and whether to include Chinese content.
+         * Kafka topic name. All log data delivered through this configuration will be sent to this topic.
          */
-        sqlFlag: boolean;
+        kafkaTopic: string;
         /**
-         * Field type. Currently supports long, double, text, and json. The long and double types do not support configuring delimiters, including Chinese, or case sensitivity. Only the json type supports further configuration of JsonKeys subfields.
+         * Start time. If not configured, defaults to the current time. Note: Millisecond data will be ignored. For example, if 1776761323455 is entered, the result will be 1776761323000; if 1776761323 is entered, the result will be 1776761323000.
          */
-        valueType: string;
+        startTime: number;
     }
-    interface ProjectTag {
+    interface ShipperTosShipperInfo {
         /**
-         * Tag key
+         * Select a TOS bucket. Must be in the same region as the source log topic. Can only contain numbers, hyphens (-), and letters a–z. Must start and end with a number or letter. Length: 3–63 characters.
          */
-        key: string;
+        bucket: string;
         /**
-         * Tag value
+         * Compression format; supports snappy, gzip, lz4, none.
          */
-        value: string;
-    }
-    interface ScheduleSqlTaskRequestCycle {
+        compress: string;
         /**
-         * Cron expression, with a minimum granularity of minutes, using 24-hour format. For example, 0 18 * * * means execution at 18:00 every day.
+         * Delivery interval in seconds, range: 300–900.
          */
-        cronTab: string;
+        interval: number;
         /**
-         * If Type is set to Cron, you must also set the time zone.
+         * Maximum raw file size per partition for delivery, in MiB. Range: 5–256.
          */
-        cronTimeZone: string;
+        maxSize: number;
         /**
-         * Scheduling period or the time point for periodic execution (minutes from 00:00). Range: 1–1440 minutes.
+         * Partition rule for log delivery. Subdirectory naming format supports strftime syntax. Default: %Y/%m/%d/%H/%M.
          */
-        time: number;
+        partitionFormat: string;
         /**
-         * Scheduling period type. Options: Period, Fixed, Cron.
+         * Top-level directory name for the bucket. Cannot start with / or \, and cannot use consecutive /. Cannot use .. as a folder name. Duplicate names are not allowed within the same bucket.
          */
-        type: string;
+        prefix: string;
     }
     interface TopicTag {
         /**
@@ -19193,14 +20994,6 @@ export declare namespace vedbm {
          * Instance ID.
          */
         instanceId: string;
-        /**
-         * Instance name.
-         */
-        instanceName: string;
-        /**
-         * Instance VPC ID.
-         */
-        vpc: string;
     }
     interface DatabaseDatabasesPrivilege {
         /**
@@ -20236,6 +22029,38 @@ export declare namespace vepfs {
          */
         value: string;
     }
+    interface GetMountServiceAttachFileSystem {
+        /**
+         * Account ID.
+         */
+        accountId: string;
+        /**
+         * User mount path.
+         */
+        customerPath: string;
+        /**
+         * File system ID.
+         */
+        fileSystemId: string;
+        /**
+         * File system name.
+         */
+        fileSystemName: string;
+        /**
+         * Binding status. Details: Attaching: Attaching. AttachError: Attachment failed. Attached: Attached. Detaching: Detaching. DetachError: Detachment failed.
+         */
+        status: string;
+    }
+    interface GetMountServiceNode {
+        /**
+         * Node initial password.
+         */
+        defaultPassword: string;
+        /**
+         * Node instance ID.
+         */
+        nodeId: string;
+    }
     interface InstanceCapacityInfo {
         /**
          * Total file system capacity, unit: TiB. Note: Disk balancing time varies based on cluster capacity, cluster load, and other factors. For clusters above the PiB level, expansion typically requires day-level disk balancing time. The expansion capacity becomes effective (and is billed) only after disk balancing is complete.
@@ -20256,6 +22081,38 @@ export declare namespace vepfs {
          */
         value: string;
     }
+    interface MountServiceAttachFileSystem {
+        /**
+         * Account ID.
+         */
+        accountId: string;
+        /**
+         * User mount path.
+         */
+        customerPath: string;
+        /**
+         * File system ID.
+         */
+        fileSystemId: string;
+        /**
+         * File system name.
+         */
+        fileSystemName: string;
+        /**
+         * Binding status. Details: Attaching: Attaching. AttachError: Attachment failed. Attached: Attached. Detaching: Detaching. DetachError: Detachment failed.
+         */
+        status: string;
+    }
+    interface MountServiceNode {
+        /**
+         * Node initial password.
+         */
+        defaultPassword: string;
+        /**
+         * Node instance ID.
+         */
+        nodeId: string;
+    }
 }
 export declare namespace vke {
     interface AddonStatus {