opentelekomcloud.LtsCceAccessV3
Explore with Pulumi AI
Manages an LTS CCE access resource within OpenTelekomCloud.
Example Usage
CCE Access With Container Stdout
Coming soon!
Coming soon!
Coming soon!
Coming soon!
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.opentelekomcloud.LtsCceAccessV3;
import com.pulumi.opentelekomcloud.LtsCceAccessV3Args;
import com.pulumi.opentelekomcloud.inputs.LtsCceAccessV3AccessConfigArgs;
import com.pulumi.opentelekomcloud.inputs.LtsCceAccessV3AccessConfigSingleLogFormatArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var config = ctx.config();
final var name = config.get("name");
final var logGroupId = config.get("logGroupId");
final var logStreamId = config.get("logStreamId");
final var hostGroupId = config.get("hostGroupId");
final var clusterId = config.get("clusterId");
var containerStdout = new LtsCceAccessV3("containerStdout", LtsCceAccessV3Args.builder()
.logGroupId(logGroupId)
.logStreamId(logStreamId)
.hostGroupIds(hostGroupId)
.clusterId(clusterId)
.accessConfig(LtsCceAccessV3AccessConfigArgs.builder()
.pathType("container_stdout")
.stdout(true)
.windowsLogInfo(%!v(PANIC=Format method: runtime error: invalid memory address or nil pointer dereference))
.singleLogFormat(LtsCceAccessV3AccessConfigSingleLogFormatArgs.builder()
.mode("system")
.build())
.build())
.build());
}
}
configuration:
name:
type: dynamic
logGroupId:
type: dynamic
logStreamId:
type: dynamic
hostGroupId:
type: dynamic
clusterId:
type: dynamic
resources:
containerStdout:
type: opentelekomcloud:LtsCceAccessV3
properties:
logGroupId: ${logGroupId}
logStreamId: ${logStreamId}
hostGroupIds:
- ${hostGroupId}
clusterId: ${clusterId}
accessConfig:
pathType: container_stdout
stdout: true
windowsLogInfo:
- categories:
- System
- Application
eventLevel:
- warning
- error
timeOffsetUnit: day
timeOffset: 7
singleLogFormat:
mode: system
CCE Access With Container File
import * as pulumi from "@pulumi/pulumi";
import * as opentelekomcloud from "@pulumi/opentelekomcloud";
const config = new pulumi.Config();
const name = config.requireObject("name");
const logGroupId = config.requireObject("logGroupId");
const logStreamId = config.requireObject("logStreamId");
const hostGroupId = config.requireObject("hostGroupId");
const clusterId = config.requireObject("clusterId");
const containerFile = new opentelekomcloud.LtsCceAccessV3("containerFile", {
logGroupId: logGroupId,
logStreamId: logStreamId,
hostGroupIds: [hostGroupId],
clusterId: clusterId,
accessConfig: {
pathType: "container_file",
paths: ["/var"],
singleLogFormat: {
mode: "system",
},
},
});
import pulumi
import pulumi_opentelekomcloud as opentelekomcloud
config = pulumi.Config()
name = config.require_object("name")
log_group_id = config.require_object("logGroupId")
log_stream_id = config.require_object("logStreamId")
host_group_id = config.require_object("hostGroupId")
cluster_id = config.require_object("clusterId")
container_file = opentelekomcloud.LtsCceAccessV3("containerFile",
log_group_id=log_group_id,
log_stream_id=log_stream_id,
host_group_ids=[host_group_id],
cluster_id=cluster_id,
access_config={
"path_type": "container_file",
"paths": ["/var"],
"single_log_format": {
"mode": "system",
},
})
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/opentelekomcloud/opentelekomcloud"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi/config"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
cfg := config.New(ctx, "")
name := cfg.RequireObject("name")
logGroupId := cfg.RequireObject("logGroupId")
logStreamId := cfg.RequireObject("logStreamId")
hostGroupId := cfg.RequireObject("hostGroupId")
clusterId := cfg.RequireObject("clusterId")
_, err := opentelekomcloud.NewLtsCceAccessV3(ctx, "containerFile", &opentelekomcloud.LtsCceAccessV3Args{
LogGroupId: pulumi.Any(logGroupId),
LogStreamId: pulumi.Any(logStreamId),
HostGroupIds: pulumi.StringArray{
hostGroupId,
},
ClusterId: pulumi.Any(clusterId),
AccessConfig: &opentelekomcloud.LtsCceAccessV3AccessConfigArgs{
PathType: pulumi.String("container_file"),
Paths: pulumi.StringArray{
pulumi.String("/var"),
},
SingleLogFormat: &opentelekomcloud.LtsCceAccessV3AccessConfigSingleLogFormatArgs{
Mode: pulumi.String("system"),
},
},
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Opentelekomcloud = Pulumi.Opentelekomcloud;
return await Deployment.RunAsync(() =>
{
var config = new Config();
var name = config.RequireObject<dynamic>("name");
var logGroupId = config.RequireObject<dynamic>("logGroupId");
var logStreamId = config.RequireObject<dynamic>("logStreamId");
var hostGroupId = config.RequireObject<dynamic>("hostGroupId");
var clusterId = config.RequireObject<dynamic>("clusterId");
var containerFile = new Opentelekomcloud.LtsCceAccessV3("containerFile", new()
{
LogGroupId = logGroupId,
LogStreamId = logStreamId,
HostGroupIds = new[]
{
hostGroupId,
},
ClusterId = clusterId,
AccessConfig = new Opentelekomcloud.Inputs.LtsCceAccessV3AccessConfigArgs
{
PathType = "container_file",
Paths = new[]
{
"/var",
},
SingleLogFormat = new Opentelekomcloud.Inputs.LtsCceAccessV3AccessConfigSingleLogFormatArgs
{
Mode = "system",
},
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.opentelekomcloud.LtsCceAccessV3;
import com.pulumi.opentelekomcloud.LtsCceAccessV3Args;
import com.pulumi.opentelekomcloud.inputs.LtsCceAccessV3AccessConfigArgs;
import com.pulumi.opentelekomcloud.inputs.LtsCceAccessV3AccessConfigSingleLogFormatArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var config = ctx.config();
final var name = config.get("name");
final var logGroupId = config.get("logGroupId");
final var logStreamId = config.get("logStreamId");
final var hostGroupId = config.get("hostGroupId");
final var clusterId = config.get("clusterId");
var containerFile = new LtsCceAccessV3("containerFile", LtsCceAccessV3Args.builder()
.logGroupId(logGroupId)
.logStreamId(logStreamId)
.hostGroupIds(hostGroupId)
.clusterId(clusterId)
.accessConfig(LtsCceAccessV3AccessConfigArgs.builder()
.pathType("container_file")
.paths("/var")
.singleLogFormat(LtsCceAccessV3AccessConfigSingleLogFormatArgs.builder()
.mode("system")
.build())
.build())
.build());
}
}
configuration:
name:
type: dynamic
logGroupId:
type: dynamic
logStreamId:
type: dynamic
hostGroupId:
type: dynamic
clusterId:
type: dynamic
resources:
containerFile:
type: opentelekomcloud:LtsCceAccessV3
properties:
logGroupId: ${logGroupId}
logStreamId: ${logStreamId}
hostGroupIds:
- ${hostGroupId}
clusterId: ${clusterId}
accessConfig:
pathType: container_file
paths:
- /var
singleLogFormat:
mode: system
CCE Access With Host File
import * as pulumi from "@pulumi/pulumi";
import * as opentelekomcloud from "@pulumi/opentelekomcloud";
const config = new pulumi.Config();
const name = config.requireObject("name");
const logGroupId = config.requireObject("logGroupId");
const logStreamId = config.requireObject("logStreamId");
const hostGroupId = config.requireObject("hostGroupId");
const clusterId = config.requireObject("clusterId");
const hostFile = new opentelekomcloud.LtsCceAccessV3("hostFile", {
logGroupId: logGroupId,
logStreamId: logStreamId,
hostGroupIds: [hostGroupId],
clusterId: clusterId,
accessConfig: {
pathType: "host_file",
paths: ["/var"],
singleLogFormat: {
mode: "system",
},
},
});
import pulumi
import pulumi_opentelekomcloud as opentelekomcloud
config = pulumi.Config()
name = config.require_object("name")
log_group_id = config.require_object("logGroupId")
log_stream_id = config.require_object("logStreamId")
host_group_id = config.require_object("hostGroupId")
cluster_id = config.require_object("clusterId")
host_file = opentelekomcloud.LtsCceAccessV3("hostFile",
log_group_id=log_group_id,
log_stream_id=log_stream_id,
host_group_ids=[host_group_id],
cluster_id=cluster_id,
access_config={
"path_type": "host_file",
"paths": ["/var"],
"single_log_format": {
"mode": "system",
},
})
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/opentelekomcloud/opentelekomcloud"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi/config"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
cfg := config.New(ctx, "")
name := cfg.RequireObject("name")
logGroupId := cfg.RequireObject("logGroupId")
logStreamId := cfg.RequireObject("logStreamId")
hostGroupId := cfg.RequireObject("hostGroupId")
clusterId := cfg.RequireObject("clusterId")
_, err := opentelekomcloud.NewLtsCceAccessV3(ctx, "hostFile", &opentelekomcloud.LtsCceAccessV3Args{
LogGroupId: pulumi.Any(logGroupId),
LogStreamId: pulumi.Any(logStreamId),
HostGroupIds: pulumi.StringArray{
hostGroupId,
},
ClusterId: pulumi.Any(clusterId),
AccessConfig: &opentelekomcloud.LtsCceAccessV3AccessConfigArgs{
PathType: pulumi.String("host_file"),
Paths: pulumi.StringArray{
pulumi.String("/var"),
},
SingleLogFormat: &opentelekomcloud.LtsCceAccessV3AccessConfigSingleLogFormatArgs{
Mode: pulumi.String("system"),
},
},
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Opentelekomcloud = Pulumi.Opentelekomcloud;
return await Deployment.RunAsync(() =>
{
var config = new Config();
var name = config.RequireObject<dynamic>("name");
var logGroupId = config.RequireObject<dynamic>("logGroupId");
var logStreamId = config.RequireObject<dynamic>("logStreamId");
var hostGroupId = config.RequireObject<dynamic>("hostGroupId");
var clusterId = config.RequireObject<dynamic>("clusterId");
var hostFile = new Opentelekomcloud.LtsCceAccessV3("hostFile", new()
{
LogGroupId = logGroupId,
LogStreamId = logStreamId,
HostGroupIds = new[]
{
hostGroupId,
},
ClusterId = clusterId,
AccessConfig = new Opentelekomcloud.Inputs.LtsCceAccessV3AccessConfigArgs
{
PathType = "host_file",
Paths = new[]
{
"/var",
},
SingleLogFormat = new Opentelekomcloud.Inputs.LtsCceAccessV3AccessConfigSingleLogFormatArgs
{
Mode = "system",
},
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.opentelekomcloud.LtsCceAccessV3;
import com.pulumi.opentelekomcloud.LtsCceAccessV3Args;
import com.pulumi.opentelekomcloud.inputs.LtsCceAccessV3AccessConfigArgs;
import com.pulumi.opentelekomcloud.inputs.LtsCceAccessV3AccessConfigSingleLogFormatArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var config = ctx.config();
final var name = config.get("name");
final var logGroupId = config.get("logGroupId");
final var logStreamId = config.get("logStreamId");
final var hostGroupId = config.get("hostGroupId");
final var clusterId = config.get("clusterId");
var hostFile = new LtsCceAccessV3("hostFile", LtsCceAccessV3Args.builder()
.logGroupId(logGroupId)
.logStreamId(logStreamId)
.hostGroupIds(hostGroupId)
.clusterId(clusterId)
.accessConfig(LtsCceAccessV3AccessConfigArgs.builder()
.pathType("host_file")
.paths("/var")
.singleLogFormat(LtsCceAccessV3AccessConfigSingleLogFormatArgs.builder()
.mode("system")
.build())
.build())
.build());
}
}
configuration:
name:
type: dynamic
logGroupId:
type: dynamic
logStreamId:
type: dynamic
hostGroupId:
type: dynamic
clusterId:
type: dynamic
resources:
hostFile:
type: opentelekomcloud:LtsCceAccessV3
properties:
logGroupId: ${logGroupId}
logStreamId: ${logStreamId}
hostGroupIds:
- ${hostGroupId}
clusterId: ${clusterId}
accessConfig:
pathType: host_file
paths:
- /var
singleLogFormat:
mode: system
Create LtsCceAccessV3 Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new LtsCceAccessV3(name: string, args: LtsCceAccessV3Args, opts?: CustomResourceOptions);
@overload
def LtsCceAccessV3(resource_name: str,
args: LtsCceAccessV3Args,
opts: Optional[ResourceOptions] = None)
@overload
def LtsCceAccessV3(resource_name: str,
opts: Optional[ResourceOptions] = None,
access_config: Optional[LtsCceAccessV3AccessConfigArgs] = None,
cluster_id: Optional[str] = None,
log_group_id: Optional[str] = None,
log_stream_id: Optional[str] = None,
binary_collect: Optional[bool] = None,
host_group_ids: Optional[Sequence[str]] = None,
log_split: Optional[bool] = None,
lts_cce_access_v3_id: Optional[str] = None,
name: Optional[str] = None,
tags: Optional[Mapping[str, str]] = None)
func NewLtsCceAccessV3(ctx *Context, name string, args LtsCceAccessV3Args, opts ...ResourceOption) (*LtsCceAccessV3, error)
public LtsCceAccessV3(string name, LtsCceAccessV3Args args, CustomResourceOptions? opts = null)
public LtsCceAccessV3(String name, LtsCceAccessV3Args args)
public LtsCceAccessV3(String name, LtsCceAccessV3Args args, CustomResourceOptions options)
type: opentelekomcloud:LtsCceAccessV3
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args LtsCceAccessV3Args
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args LtsCceAccessV3Args
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args LtsCceAccessV3Args
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args LtsCceAccessV3Args
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args LtsCceAccessV3Args
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var ltsCceAccessV3Resource = new Opentelekomcloud.LtsCceAccessV3("ltsCceAccessV3Resource", new()
{
AccessConfig = new Opentelekomcloud.Inputs.LtsCceAccessV3AccessConfigArgs
{
PathType = "string",
LogEnvs =
{
{ "string", "string" },
},
MultiLogFormat = new Opentelekomcloud.Inputs.LtsCceAccessV3AccessConfigMultiLogFormatArgs
{
Mode = "string",
Value = "string",
},
ExcludeK8sLabels =
{
{ "string", "string" },
},
ExcludeLabels =
{
{ "string", "string" },
},
IncludeEnvs =
{
{ "string", "string" },
},
IncludeK8sLabels =
{
{ "string", "string" },
},
IncludeLabels =
{
{ "string", "string" },
},
BlackPaths = new[]
{
"string",
},
ExcludeEnvs =
{
{ "string", "string" },
},
LogK8s =
{
{ "string", "string" },
},
LogLabels =
{
{ "string", "string" },
},
NameSpaceRegex = "string",
ContainerNameRegex = "string",
Paths = new[]
{
"string",
},
PodNameRegex = "string",
SingleLogFormat = new Opentelekomcloud.Inputs.LtsCceAccessV3AccessConfigSingleLogFormatArgs
{
Mode = "string",
Value = "string",
},
Stderr = false,
Stdout = false,
},
ClusterId = "string",
LogGroupId = "string",
LogStreamId = "string",
BinaryCollect = false,
HostGroupIds = new[]
{
"string",
},
LogSplit = false,
LtsCceAccessV3Id = "string",
Name = "string",
Tags =
{
{ "string", "string" },
},
});
example, err := opentelekomcloud.NewLtsCceAccessV3(ctx, "ltsCceAccessV3Resource", &opentelekomcloud.LtsCceAccessV3Args{
AccessConfig: &opentelekomcloud.LtsCceAccessV3AccessConfigArgs{
PathType: pulumi.String("string"),
LogEnvs: pulumi.StringMap{
"string": pulumi.String("string"),
},
MultiLogFormat: &opentelekomcloud.LtsCceAccessV3AccessConfigMultiLogFormatArgs{
Mode: pulumi.String("string"),
Value: pulumi.String("string"),
},
ExcludeK8sLabels: pulumi.StringMap{
"string": pulumi.String("string"),
},
ExcludeLabels: pulumi.StringMap{
"string": pulumi.String("string"),
},
IncludeEnvs: pulumi.StringMap{
"string": pulumi.String("string"),
},
IncludeK8sLabels: pulumi.StringMap{
"string": pulumi.String("string"),
},
IncludeLabels: pulumi.StringMap{
"string": pulumi.String("string"),
},
BlackPaths: pulumi.StringArray{
pulumi.String("string"),
},
ExcludeEnvs: pulumi.StringMap{
"string": pulumi.String("string"),
},
LogK8s: pulumi.StringMap{
"string": pulumi.String("string"),
},
LogLabels: pulumi.StringMap{
"string": pulumi.String("string"),
},
NameSpaceRegex: pulumi.String("string"),
ContainerNameRegex: pulumi.String("string"),
Paths: pulumi.StringArray{
pulumi.String("string"),
},
PodNameRegex: pulumi.String("string"),
SingleLogFormat: &opentelekomcloud.LtsCceAccessV3AccessConfigSingleLogFormatArgs{
Mode: pulumi.String("string"),
Value: pulumi.String("string"),
},
Stderr: pulumi.Bool(false),
Stdout: pulumi.Bool(false),
},
ClusterId: pulumi.String("string"),
LogGroupId: pulumi.String("string"),
LogStreamId: pulumi.String("string"),
BinaryCollect: pulumi.Bool(false),
HostGroupIds: pulumi.StringArray{
pulumi.String("string"),
},
LogSplit: pulumi.Bool(false),
LtsCceAccessV3Id: pulumi.String("string"),
Name: pulumi.String("string"),
Tags: pulumi.StringMap{
"string": pulumi.String("string"),
},
})
var ltsCceAccessV3Resource = new LtsCceAccessV3("ltsCceAccessV3Resource", LtsCceAccessV3Args.builder()
.accessConfig(LtsCceAccessV3AccessConfigArgs.builder()
.pathType("string")
.logEnvs(Map.of("string", "string"))
.multiLogFormat(LtsCceAccessV3AccessConfigMultiLogFormatArgs.builder()
.mode("string")
.value("string")
.build())
.excludeK8sLabels(Map.of("string", "string"))
.excludeLabels(Map.of("string", "string"))
.includeEnvs(Map.of("string", "string"))
.includeK8sLabels(Map.of("string", "string"))
.includeLabels(Map.of("string", "string"))
.blackPaths("string")
.excludeEnvs(Map.of("string", "string"))
.logK8s(Map.of("string", "string"))
.logLabels(Map.of("string", "string"))
.nameSpaceRegex("string")
.containerNameRegex("string")
.paths("string")
.podNameRegex("string")
.singleLogFormat(LtsCceAccessV3AccessConfigSingleLogFormatArgs.builder()
.mode("string")
.value("string")
.build())
.stderr(false)
.stdout(false)
.build())
.clusterId("string")
.logGroupId("string")
.logStreamId("string")
.binaryCollect(false)
.hostGroupIds("string")
.logSplit(false)
.ltsCceAccessV3Id("string")
.name("string")
.tags(Map.of("string", "string"))
.build());
lts_cce_access_v3_resource = opentelekomcloud.LtsCceAccessV3("ltsCceAccessV3Resource",
access_config={
"path_type": "string",
"log_envs": {
"string": "string",
},
"multi_log_format": {
"mode": "string",
"value": "string",
},
"exclude_k8s_labels": {
"string": "string",
},
"exclude_labels": {
"string": "string",
},
"include_envs": {
"string": "string",
},
"include_k8s_labels": {
"string": "string",
},
"include_labels": {
"string": "string",
},
"black_paths": ["string"],
"exclude_envs": {
"string": "string",
},
"log_k8s": {
"string": "string",
},
"log_labels": {
"string": "string",
},
"name_space_regex": "string",
"container_name_regex": "string",
"paths": ["string"],
"pod_name_regex": "string",
"single_log_format": {
"mode": "string",
"value": "string",
},
"stderr": False,
"stdout": False,
},
cluster_id="string",
log_group_id="string",
log_stream_id="string",
binary_collect=False,
host_group_ids=["string"],
log_split=False,
lts_cce_access_v3_id="string",
name="string",
tags={
"string": "string",
})
const ltsCceAccessV3Resource = new opentelekomcloud.LtsCceAccessV3("ltsCceAccessV3Resource", {
accessConfig: {
pathType: "string",
logEnvs: {
string: "string",
},
multiLogFormat: {
mode: "string",
value: "string",
},
excludeK8sLabels: {
string: "string",
},
excludeLabels: {
string: "string",
},
includeEnvs: {
string: "string",
},
includeK8sLabels: {
string: "string",
},
includeLabels: {
string: "string",
},
blackPaths: ["string"],
excludeEnvs: {
string: "string",
},
logK8s: {
string: "string",
},
logLabels: {
string: "string",
},
nameSpaceRegex: "string",
containerNameRegex: "string",
paths: ["string"],
podNameRegex: "string",
singleLogFormat: {
mode: "string",
value: "string",
},
stderr: false,
stdout: false,
},
clusterId: "string",
logGroupId: "string",
logStreamId: "string",
binaryCollect: false,
hostGroupIds: ["string"],
logSplit: false,
ltsCceAccessV3Id: "string",
name: "string",
tags: {
string: "string",
},
});
type: opentelekomcloud:LtsCceAccessV3
properties:
accessConfig:
blackPaths:
- string
containerNameRegex: string
excludeEnvs:
string: string
excludeK8sLabels:
string: string
excludeLabels:
string: string
includeEnvs:
string: string
includeK8sLabels:
string: string
includeLabels:
string: string
logEnvs:
string: string
logK8s:
string: string
logLabels:
string: string
multiLogFormat:
mode: string
value: string
nameSpaceRegex: string
pathType: string
paths:
- string
podNameRegex: string
singleLogFormat:
mode: string
value: string
stderr: false
stdout: false
binaryCollect: false
clusterId: string
hostGroupIds:
- string
logGroupId: string
logSplit: false
logStreamId: string
ltsCceAccessV3Id: string
name: string
tags:
string: string
LtsCceAccessV3 Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The LtsCceAccessV3 resource accepts the following input properties:
- Access
Config LtsCce Access V3Access Config - Specifies the configurations of CCE access. The access_config structure is documented below.
- Cluster
Id string - Specifies the CCE cluster ID. Changing this creates a new resource.
- Log
Group stringId - Specifies the log group ID. Changing this creates a new resource.
- Log
Stream stringId - Specifies the log stream ID. Changing this creates a new resource.
- Binary
Collect bool - Specifies whether collect in binary format. Default is
false
. - Host
Group List<string>Ids - Specifies the log access host group ID list.
- Log
Split bool Specifies whether to split log. Default is false.
The
access_config
block supports:- Lts
Cce stringAccess V3Id - The resource ID.
- Name string
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - Dictionary<string, string>
- Specifies the key/value pairs to associate with the CCE access.
- Access
Config LtsCce Access V3Access Config Args - Specifies the configurations of CCE access. The access_config structure is documented below.
- Cluster
Id string - Specifies the CCE cluster ID. Changing this creates a new resource.
- Log
Group stringId - Specifies the log group ID. Changing this creates a new resource.
- Log
Stream stringId - Specifies the log stream ID. Changing this creates a new resource.
- Binary
Collect bool - Specifies whether collect in binary format. Default is
false
. - Host
Group []stringIds - Specifies the log access host group ID list.
- Log
Split bool Specifies whether to split log. Default is false.
The
access_config
block supports:- Lts
Cce stringAccess V3Id - The resource ID.
- Name string
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - map[string]string
- Specifies the key/value pairs to associate with the CCE access.
- access
Config LtsCce Access V3Access Config - Specifies the configurations of CCE access. The access_config structure is documented below.
- cluster
Id String - Specifies the CCE cluster ID. Changing this creates a new resource.
- log
Group StringId - Specifies the log group ID. Changing this creates a new resource.
- log
Stream StringId - Specifies the log stream ID. Changing this creates a new resource.
- binary
Collect Boolean - Specifies whether collect in binary format. Default is
false
. - host
Group List<String>Ids - Specifies the log access host group ID list.
- log
Split Boolean Specifies whether to split log. Default is false.
The
access_config
block supports:- lts
Cce StringAccess V3Id - The resource ID.
- name String
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - Map<String,String>
- Specifies the key/value pairs to associate with the CCE access.
- access
Config LtsCce Access V3Access Config - Specifies the configurations of CCE access. The access_config structure is documented below.
- cluster
Id string - Specifies the CCE cluster ID. Changing this creates a new resource.
- log
Group stringId - Specifies the log group ID. Changing this creates a new resource.
- log
Stream stringId - Specifies the log stream ID. Changing this creates a new resource.
- binary
Collect boolean - Specifies whether collect in binary format. Default is
false
. - host
Group string[]Ids - Specifies the log access host group ID list.
- log
Split boolean Specifies whether to split log. Default is false.
The
access_config
block supports:- lts
Cce stringAccess V3Id - The resource ID.
- name string
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - {[key: string]: string}
- Specifies the key/value pairs to associate with the CCE access.
- access_
config LtsCce Access V3Access Config Args - Specifies the configurations of CCE access. The access_config structure is documented below.
- cluster_
id str - Specifies the CCE cluster ID. Changing this creates a new resource.
- log_
group_ strid - Specifies the log group ID. Changing this creates a new resource.
- log_
stream_ strid - Specifies the log stream ID. Changing this creates a new resource.
- binary_
collect bool - Specifies whether collect in binary format. Default is
false
. - host_
group_ Sequence[str]ids - Specifies the log access host group ID list.
- log_
split bool Specifies whether to split log. Default is false.
The
access_config
block supports:- lts_
cce_ straccess_ v3_ id - The resource ID.
- name str
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - Mapping[str, str]
- Specifies the key/value pairs to associate with the CCE access.
- access
Config Property Map - Specifies the configurations of CCE access. The access_config structure is documented below.
- cluster
Id String - Specifies the CCE cluster ID. Changing this creates a new resource.
- log
Group StringId - Specifies the log group ID. Changing this creates a new resource.
- log
Stream StringId - Specifies the log stream ID. Changing this creates a new resource.
- binary
Collect Boolean - Specifies whether collect in binary format. Default is
false
. - host
Group List<String>Ids - Specifies the log access host group ID list.
- log
Split Boolean Specifies whether to split log. Default is false.
The
access_config
block supports:- lts
Cce StringAccess V3Id - The resource ID.
- name String
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - Map<String>
- Specifies the key/value pairs to associate with the CCE access.
Outputs
All input properties are implicitly available as output properties. Additionally, the LtsCceAccessV3 resource produces the following output properties:
- Access
Type string - The log access type.
- Created
At string - The creation time of the CCE access, in RFC3339 format.
- Id string
- The provider-assigned unique ID for this managed resource.
- Log
Group stringName - The log group name.
- Log
Stream stringName - The log stream name.
- Region string
- Shows the region in the cce access resource created.
- Access
Type string - The log access type.
- Created
At string - The creation time of the CCE access, in RFC3339 format.
- Id string
- The provider-assigned unique ID for this managed resource.
- Log
Group stringName - The log group name.
- Log
Stream stringName - The log stream name.
- Region string
- Shows the region in the cce access resource created.
- access
Type String - The log access type.
- created
At String - The creation time of the CCE access, in RFC3339 format.
- id String
- The provider-assigned unique ID for this managed resource.
- log
Group StringName - The log group name.
- log
Stream StringName - The log stream name.
- region String
- Shows the region in the cce access resource created.
- access
Type string - The log access type.
- created
At string - The creation time of the CCE access, in RFC3339 format.
- id string
- The provider-assigned unique ID for this managed resource.
- log
Group stringName - The log group name.
- log
Stream stringName - The log stream name.
- region string
- Shows the region in the cce access resource created.
- access_
type str - The log access type.
- created_
at str - The creation time of the CCE access, in RFC3339 format.
- id str
- The provider-assigned unique ID for this managed resource.
- log_
group_ strname - The log group name.
- log_
stream_ strname - The log stream name.
- region str
- Shows the region in the cce access resource created.
- access
Type String - The log access type.
- created
At String - The creation time of the CCE access, in RFC3339 format.
- id String
- The provider-assigned unique ID for this managed resource.
- log
Group StringName - The log group name.
- log
Stream StringName - The log stream name.
- region String
- Shows the region in the cce access resource created.
Look up Existing LtsCceAccessV3 Resource
Get an existing LtsCceAccessV3 resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: LtsCceAccessV3State, opts?: CustomResourceOptions): LtsCceAccessV3
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
access_config: Optional[LtsCceAccessV3AccessConfigArgs] = None,
access_type: Optional[str] = None,
binary_collect: Optional[bool] = None,
cluster_id: Optional[str] = None,
created_at: Optional[str] = None,
host_group_ids: Optional[Sequence[str]] = None,
log_group_id: Optional[str] = None,
log_group_name: Optional[str] = None,
log_split: Optional[bool] = None,
log_stream_id: Optional[str] = None,
log_stream_name: Optional[str] = None,
lts_cce_access_v3_id: Optional[str] = None,
name: Optional[str] = None,
region: Optional[str] = None,
tags: Optional[Mapping[str, str]] = None) -> LtsCceAccessV3
func GetLtsCceAccessV3(ctx *Context, name string, id IDInput, state *LtsCceAccessV3State, opts ...ResourceOption) (*LtsCceAccessV3, error)
public static LtsCceAccessV3 Get(string name, Input<string> id, LtsCceAccessV3State? state, CustomResourceOptions? opts = null)
public static LtsCceAccessV3 get(String name, Output<String> id, LtsCceAccessV3State state, CustomResourceOptions options)
resources: _: type: opentelekomcloud:LtsCceAccessV3 get: id: ${id}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Access
Config LtsCce Access V3Access Config - Specifies the configurations of CCE access. The access_config structure is documented below.
- Access
Type string - The log access type.
- Binary
Collect bool - Specifies whether collect in binary format. Default is
false
. - Cluster
Id string - Specifies the CCE cluster ID. Changing this creates a new resource.
- Created
At string - The creation time of the CCE access, in RFC3339 format.
- Host
Group List<string>Ids - Specifies the log access host group ID list.
- Log
Group stringId - Specifies the log group ID. Changing this creates a new resource.
- Log
Group stringName - The log group name.
- Log
Split bool Specifies whether to split log. Default is false.
The
access_config
block supports:- Log
Stream stringId - Specifies the log stream ID. Changing this creates a new resource.
- Log
Stream stringName - The log stream name.
- Lts
Cce stringAccess V3Id - The resource ID.
- Name string
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - Region string
- Shows the region in the cce access resource created.
- Dictionary<string, string>
- Specifies the key/value pairs to associate with the CCE access.
- Access
Config LtsCce Access V3Access Config Args - Specifies the configurations of CCE access. The access_config structure is documented below.
- Access
Type string - The log access type.
- Binary
Collect bool - Specifies whether collect in binary format. Default is
false
. - Cluster
Id string - Specifies the CCE cluster ID. Changing this creates a new resource.
- Created
At string - The creation time of the CCE access, in RFC3339 format.
- Host
Group []stringIds - Specifies the log access host group ID list.
- Log
Group stringId - Specifies the log group ID. Changing this creates a new resource.
- Log
Group stringName - The log group name.
- Log
Split bool Specifies whether to split log. Default is false.
The
access_config
block supports:- Log
Stream stringId - Specifies the log stream ID. Changing this creates a new resource.
- Log
Stream stringName - The log stream name.
- Lts
Cce stringAccess V3Id - The resource ID.
- Name string
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - Region string
- Shows the region in the cce access resource created.
- map[string]string
- Specifies the key/value pairs to associate with the CCE access.
- access
Config LtsCce Access V3Access Config - Specifies the configurations of CCE access. The access_config structure is documented below.
- access
Type String - The log access type.
- binary
Collect Boolean - Specifies whether collect in binary format. Default is
false
. - cluster
Id String - Specifies the CCE cluster ID. Changing this creates a new resource.
- created
At String - The creation time of the CCE access, in RFC3339 format.
- host
Group List<String>Ids - Specifies the log access host group ID list.
- log
Group StringId - Specifies the log group ID. Changing this creates a new resource.
- log
Group StringName - The log group name.
- log
Split Boolean Specifies whether to split log. Default is false.
The
access_config
block supports:- log
Stream StringId - Specifies the log stream ID. Changing this creates a new resource.
- log
Stream StringName - The log stream name.
- lts
Cce StringAccess V3Id - The resource ID.
- name String
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - region String
- Shows the region in the cce access resource created.
- Map<String,String>
- Specifies the key/value pairs to associate with the CCE access.
- access
Config LtsCce Access V3Access Config - Specifies the configurations of CCE access. The access_config structure is documented below.
- access
Type string - The log access type.
- binary
Collect boolean - Specifies whether collect in binary format. Default is
false
. - cluster
Id string - Specifies the CCE cluster ID. Changing this creates a new resource.
- created
At string - The creation time of the CCE access, in RFC3339 format.
- host
Group string[]Ids - Specifies the log access host group ID list.
- log
Group stringId - Specifies the log group ID. Changing this creates a new resource.
- log
Group stringName - The log group name.
- log
Split boolean Specifies whether to split log. Default is false.
The
access_config
block supports:- log
Stream stringId - Specifies the log stream ID. Changing this creates a new resource.
- log
Stream stringName - The log stream name.
- lts
Cce stringAccess V3Id - The resource ID.
- name string
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - region string
- Shows the region in the cce access resource created.
- {[key: string]: string}
- Specifies the key/value pairs to associate with the CCE access.
- access_
config LtsCce Access V3Access Config Args - Specifies the configurations of CCE access. The access_config structure is documented below.
- access_
type str - The log access type.
- binary_
collect bool - Specifies whether collect in binary format. Default is
false
. - cluster_
id str - Specifies the CCE cluster ID. Changing this creates a new resource.
- created_
at str - The creation time of the CCE access, in RFC3339 format.
- host_
group_ Sequence[str]ids - Specifies the log access host group ID list.
- log_
group_ strid - Specifies the log group ID. Changing this creates a new resource.
- log_
group_ strname - The log group name.
- log_
split bool Specifies whether to split log. Default is false.
The
access_config
block supports:- log_
stream_ strid - Specifies the log stream ID. Changing this creates a new resource.
- log_
stream_ strname - The log stream name.
- lts_
cce_ straccess_ v3_ id - The resource ID.
- name str
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - region str
- Shows the region in the cce access resource created.
- Mapping[str, str]
- Specifies the key/value pairs to associate with the CCE access.
- access
Config Property Map - Specifies the configurations of CCE access. The access_config structure is documented below.
- access
Type String - The log access type.
- binary
Collect Boolean - Specifies whether collect in binary format. Default is
false
. - cluster
Id String - Specifies the CCE cluster ID. Changing this creates a new resource.
- created
At String - The creation time of the CCE access, in RFC3339 format.
- host
Group List<String>Ids - Specifies the log access host group ID list.
- log
Group StringId - Specifies the log group ID. Changing this creates a new resource.
- log
Group StringName - The log group name.
- log
Split Boolean Specifies whether to split log. Default is false.
The
access_config
block supports:- log
Stream StringId - Specifies the log stream ID. Changing this creates a new resource.
- log
Stream StringName - The log stream name.
- lts
Cce StringAccess V3Id - The resource ID.
- name String
- Specifies the name of the CCE access. The name consists of
1
to64
characters. Only letters, digits, underscores (_), and periods (.) are allowed, and the period cannot be the first or last character. Changing this creates a new resource. - region String
- Shows the region in the cce access resource created.
- Map<String>
- Specifies the key/value pairs to associate with the CCE access.
Supporting Types
LtsCceAccessV3AccessConfig, LtsCceAccessV3AccessConfigArgs
- Path
Type string - Specifies the type of the CCE access. The options are as follows:
- Black
Paths List<string> - Specifies the collection path blacklist.
- Container
Name stringRegex - Specifies the regular expression matching of kubernetes container names. LTS will collect logs of the containers with names matching this expression. To collect logs of all containers, leave this field empty.
- Exclude
Envs Dictionary<string, string> - Specifies the environment variable blacklist. A maximum of
30
tags can be created. The key names must be unique. LTS will exclude all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - Exclude
K8s Dictionary<string, string>Labels Specifies the kubernetes label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are excluded. If labelValue is not empty, only containers whose K8s label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a K8s Label can be excluded as long as it meets any of the blacklists.These parameters include
name_space_regex
,pod_name_regex
,container_name_regex
,log_labels
,include_labels
,exclude_labels
,log_envs
,include_envs
,exclude_envs
,log_k8s
,include_k8s_labels
andexclude_k8s_labels
are available, onlypath_type
is not host_file.The
single_log_format
block supports:- Exclude
Labels Dictionary<string, string> - Specifies the container label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are excluded. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a container label can be excluded as long as it meets any of the blacklists. - Include
Envs Dictionary<string, string> - Specifies the environment variable whitelist. A maximum of
30
tags can be created. The key names must be unique. LTS will match all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - Include
K8s Dictionary<string, string>Labels - Specifies the kubernetes label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are matched. If labelValue is not empty, only containers whose K8s Label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a K8s label can be matched as long as it meets any of the whitelists. - Include
Labels Dictionary<string, string> - Specifies the container label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are matched. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a container label can be matched as long as it meets any of the whitelists. - Log
Envs Dictionary<string, string> - Specifies the environment variable tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each environment variable key has a corresponding environment variable value. For example, if you enterapp
as the key andapp_alias
as the value, when the kubernetes environment variable containsapp=lts
,{app_alias: lts}
will be added to the log. - Log
K8s Dictionary<string, string> - Specifies the kubernetes label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the K8s label containsapp=lts
,{app_alias: lts}
will be added to the log. - Log
Labels Dictionary<string, string> - Specifies the container label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the Container label containsapp=lts
,{app_alias: lts}
will be added to the log. - Multi
Log LtsFormat Cce Access V3Access Config Multi Log Format Specifies the configuration multi-line logs. Multiple lines of exception log events can be displayed as a single log event. This is helpful when you check logs to locate problems. The multi_log_format structure is documented below.
single_log_format
ormulti_log_format
must be specified.- Name
Space stringRegex - Specifies the regular expression matching of kubernetes namespaces. LTS will collect logs of the namespaces with names matching this expression. To collect logs of all namespaces, leave this field empty.
- Paths List<string>
- Specifies the collection paths. Required when
path_type
iscontainer_file
,container_stdout
orhost_file
. - Pod
Name stringRegex - Specifies the regular expression matching of kubernetes pods. LTS will collect logs of the Pods with names matching this expression. To collect logs of all Pods, leave this field empty.
- Single
Log LtsFormat Cce Access V3Access Config Single Log Format - Specifies the configuration single-line logs. Each log line is displayed as a single log event. The single_log_format structure is documented below.
- Stderr bool
Specifies whether error output is standard. Default is
false
.If the value of
path_type
iscontainer_stdout
,stdout
orstderr
must betrue
.- Stdout bool
- Specifies whether output is standard. Default is false.
- Path
Type string - Specifies the type of the CCE access. The options are as follows:
- Black
Paths []string - Specifies the collection path blacklist.
- Container
Name stringRegex - Specifies the regular expression matching of kubernetes container names. LTS will collect logs of the containers with names matching this expression. To collect logs of all containers, leave this field empty.
- Exclude
Envs map[string]string - Specifies the environment variable blacklist. A maximum of
30
tags can be created. The key names must be unique. LTS will exclude all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - Exclude
K8s map[string]stringLabels Specifies the kubernetes label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are excluded. If labelValue is not empty, only containers whose K8s label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a K8s Label can be excluded as long as it meets any of the blacklists.These parameters include
name_space_regex
,pod_name_regex
,container_name_regex
,log_labels
,include_labels
,exclude_labels
,log_envs
,include_envs
,exclude_envs
,log_k8s
,include_k8s_labels
andexclude_k8s_labels
are available, onlypath_type
is not host_file.The
single_log_format
block supports:- Exclude
Labels map[string]string - Specifies the container label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are excluded. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a container label can be excluded as long as it meets any of the blacklists. - Include
Envs map[string]string - Specifies the environment variable whitelist. A maximum of
30
tags can be created. The key names must be unique. LTS will match all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - Include
K8s map[string]stringLabels - Specifies the kubernetes label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are matched. If labelValue is not empty, only containers whose K8s Label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a K8s label can be matched as long as it meets any of the whitelists. - Include
Labels map[string]string - Specifies the container label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are matched. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a container label can be matched as long as it meets any of the whitelists. - Log
Envs map[string]string - Specifies the environment variable tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each environment variable key has a corresponding environment variable value. For example, if you enterapp
as the key andapp_alias
as the value, when the kubernetes environment variable containsapp=lts
,{app_alias: lts}
will be added to the log. - Log
K8s map[string]string - Specifies the kubernetes label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the K8s label containsapp=lts
,{app_alias: lts}
will be added to the log. - Log
Labels map[string]string - Specifies the container label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the Container label containsapp=lts
,{app_alias: lts}
will be added to the log. - Multi
Log LtsFormat Cce Access V3Access Config Multi Log Format Specifies the configuration multi-line logs. Multiple lines of exception log events can be displayed as a single log event. This is helpful when you check logs to locate problems. The multi_log_format structure is documented below.
single_log_format
ormulti_log_format
must be specified.- Name
Space stringRegex - Specifies the regular expression matching of kubernetes namespaces. LTS will collect logs of the namespaces with names matching this expression. To collect logs of all namespaces, leave this field empty.
- Paths []string
- Specifies the collection paths. Required when
path_type
iscontainer_file
,container_stdout
orhost_file
. - Pod
Name stringRegex - Specifies the regular expression matching of kubernetes pods. LTS will collect logs of the Pods with names matching this expression. To collect logs of all Pods, leave this field empty.
- Single
Log LtsFormat Cce Access V3Access Config Single Log Format - Specifies the configuration single-line logs. Each log line is displayed as a single log event. The single_log_format structure is documented below.
- Stderr bool
Specifies whether error output is standard. Default is
false
.If the value of
path_type
iscontainer_stdout
,stdout
orstderr
must betrue
.- Stdout bool
- Specifies whether output is standard. Default is false.
- path
Type String - Specifies the type of the CCE access. The options are as follows:
- black
Paths List<String> - Specifies the collection path blacklist.
- container
Name StringRegex - Specifies the regular expression matching of kubernetes container names. LTS will collect logs of the containers with names matching this expression. To collect logs of all containers, leave this field empty.
- exclude
Envs Map<String,String> - Specifies the environment variable blacklist. A maximum of
30
tags can be created. The key names must be unique. LTS will exclude all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - exclude
K8s Map<String,String>Labels Specifies the kubernetes label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are excluded. If labelValue is not empty, only containers whose K8s label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a K8s Label can be excluded as long as it meets any of the blacklists.These parameters include
name_space_regex
,pod_name_regex
,container_name_regex
,log_labels
,include_labels
,exclude_labels
,log_envs
,include_envs
,exclude_envs
,log_k8s
,include_k8s_labels
andexclude_k8s_labels
are available, onlypath_type
is not host_file.The
single_log_format
block supports:- exclude
Labels Map<String,String> - Specifies the container label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are excluded. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a container label can be excluded as long as it meets any of the blacklists. - include
Envs Map<String,String> - Specifies the environment variable whitelist. A maximum of
30
tags can be created. The key names must be unique. LTS will match all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - include
K8s Map<String,String>Labels - Specifies the kubernetes label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are matched. If labelValue is not empty, only containers whose K8s Label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a K8s label can be matched as long as it meets any of the whitelists. - include
Labels Map<String,String> - Specifies the container label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are matched. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a container label can be matched as long as it meets any of the whitelists. - log
Envs Map<String,String> - Specifies the environment variable tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each environment variable key has a corresponding environment variable value. For example, if you enterapp
as the key andapp_alias
as the value, when the kubernetes environment variable containsapp=lts
,{app_alias: lts}
will be added to the log. - log
K8s Map<String,String> - Specifies the kubernetes label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the K8s label containsapp=lts
,{app_alias: lts}
will be added to the log. - log
Labels Map<String,String> - Specifies the container label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the Container label containsapp=lts
,{app_alias: lts}
will be added to the log. - multi
Log LtsFormat Cce Access V3Access Config Multi Log Format Specifies the configuration multi-line logs. Multiple lines of exception log events can be displayed as a single log event. This is helpful when you check logs to locate problems. The multi_log_format structure is documented below.
single_log_format
ormulti_log_format
must be specified.- name
Space StringRegex - Specifies the regular expression matching of kubernetes namespaces. LTS will collect logs of the namespaces with names matching this expression. To collect logs of all namespaces, leave this field empty.
- paths List<String>
- Specifies the collection paths. Required when
path_type
iscontainer_file
,container_stdout
orhost_file
. - pod
Name StringRegex - Specifies the regular expression matching of kubernetes pods. LTS will collect logs of the Pods with names matching this expression. To collect logs of all Pods, leave this field empty.
- single
Log LtsFormat Cce Access V3Access Config Single Log Format - Specifies the configuration single-line logs. Each log line is displayed as a single log event. The single_log_format structure is documented below.
- stderr Boolean
Specifies whether error output is standard. Default is
false
.If the value of
path_type
iscontainer_stdout
,stdout
orstderr
must betrue
.- stdout Boolean
- Specifies whether output is standard. Default is false.
- path
Type string - Specifies the type of the CCE access. The options are as follows:
- black
Paths string[] - Specifies the collection path blacklist.
- container
Name stringRegex - Specifies the regular expression matching of kubernetes container names. LTS will collect logs of the containers with names matching this expression. To collect logs of all containers, leave this field empty.
- exclude
Envs {[key: string]: string} - Specifies the environment variable blacklist. A maximum of
30
tags can be created. The key names must be unique. LTS will exclude all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - exclude
K8s {[key: string]: string}Labels Specifies the kubernetes label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are excluded. If labelValue is not empty, only containers whose K8s label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a K8s Label can be excluded as long as it meets any of the blacklists.These parameters include
name_space_regex
,pod_name_regex
,container_name_regex
,log_labels
,include_labels
,exclude_labels
,log_envs
,include_envs
,exclude_envs
,log_k8s
,include_k8s_labels
andexclude_k8s_labels
are available, onlypath_type
is not host_file.The
single_log_format
block supports:- exclude
Labels {[key: string]: string} - Specifies the container label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are excluded. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a container label can be excluded as long as it meets any of the blacklists. - include
Envs {[key: string]: string} - Specifies the environment variable whitelist. A maximum of
30
tags can be created. The key names must be unique. LTS will match all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - include
K8s {[key: string]: string}Labels - Specifies the kubernetes label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are matched. If labelValue is not empty, only containers whose K8s Label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a K8s label can be matched as long as it meets any of the whitelists. - include
Labels {[key: string]: string} - Specifies the container label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are matched. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a container label can be matched as long as it meets any of the whitelists. - log
Envs {[key: string]: string} - Specifies the environment variable tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each environment variable key has a corresponding environment variable value. For example, if you enterapp
as the key andapp_alias
as the value, when the kubernetes environment variable containsapp=lts
,{app_alias: lts}
will be added to the log. - log
K8s {[key: string]: string} - Specifies the kubernetes label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the K8s label containsapp=lts
,{app_alias: lts}
will be added to the log. - log
Labels {[key: string]: string} - Specifies the container label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the Container label containsapp=lts
,{app_alias: lts}
will be added to the log. - multi
Log LtsFormat Cce Access V3Access Config Multi Log Format Specifies the configuration multi-line logs. Multiple lines of exception log events can be displayed as a single log event. This is helpful when you check logs to locate problems. The multi_log_format structure is documented below.
single_log_format
ormulti_log_format
must be specified.- name
Space stringRegex - Specifies the regular expression matching of kubernetes namespaces. LTS will collect logs of the namespaces with names matching this expression. To collect logs of all namespaces, leave this field empty.
- paths string[]
- Specifies the collection paths. Required when
path_type
iscontainer_file
,container_stdout
orhost_file
. - pod
Name stringRegex - Specifies the regular expression matching of kubernetes pods. LTS will collect logs of the Pods with names matching this expression. To collect logs of all Pods, leave this field empty.
- single
Log LtsFormat Cce Access V3Access Config Single Log Format - Specifies the configuration single-line logs. Each log line is displayed as a single log event. The single_log_format structure is documented below.
- stderr boolean
Specifies whether error output is standard. Default is
false
.If the value of
path_type
iscontainer_stdout
,stdout
orstderr
must betrue
.- stdout boolean
- Specifies whether output is standard. Default is false.
- path_
type str - Specifies the type of the CCE access. The options are as follows:
- black_
paths Sequence[str] - Specifies the collection path blacklist.
- container_
name_ strregex - Specifies the regular expression matching of kubernetes container names. LTS will collect logs of the containers with names matching this expression. To collect logs of all containers, leave this field empty.
- exclude_
envs Mapping[str, str] - Specifies the environment variable blacklist. A maximum of
30
tags can be created. The key names must be unique. LTS will exclude all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - exclude_
k8s_ Mapping[str, str]labels Specifies the kubernetes label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are excluded. If labelValue is not empty, only containers whose K8s label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a K8s Label can be excluded as long as it meets any of the blacklists.These parameters include
name_space_regex
,pod_name_regex
,container_name_regex
,log_labels
,include_labels
,exclude_labels
,log_envs
,include_envs
,exclude_envs
,log_k8s
,include_k8s_labels
andexclude_k8s_labels
are available, onlypath_type
is not host_file.The
single_log_format
block supports:- exclude_
labels Mapping[str, str] - Specifies the container label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are excluded. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a container label can be excluded as long as it meets any of the blacklists. - include_
envs Mapping[str, str] - Specifies the environment variable whitelist. A maximum of
30
tags can be created. The key names must be unique. LTS will match all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - include_
k8s_ Mapping[str, str]labels - Specifies the kubernetes label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are matched. If labelValue is not empty, only containers whose K8s Label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a K8s label can be matched as long as it meets any of the whitelists. - include_
labels Mapping[str, str] - Specifies the container label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are matched. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a container label can be matched as long as it meets any of the whitelists. - log_
envs Mapping[str, str] - Specifies the environment variable tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each environment variable key has a corresponding environment variable value. For example, if you enterapp
as the key andapp_alias
as the value, when the kubernetes environment variable containsapp=lts
,{app_alias: lts}
will be added to the log. - log_
k8s Mapping[str, str] - Specifies the kubernetes label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the K8s label containsapp=lts
,{app_alias: lts}
will be added to the log. - log_
labels Mapping[str, str] - Specifies the container label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the Container label containsapp=lts
,{app_alias: lts}
will be added to the log. - multi_
log_ Ltsformat Cce Access V3Access Config Multi Log Format Specifies the configuration multi-line logs. Multiple lines of exception log events can be displayed as a single log event. This is helpful when you check logs to locate problems. The multi_log_format structure is documented below.
single_log_format
ormulti_log_format
must be specified.- name_
space_ strregex - Specifies the regular expression matching of kubernetes namespaces. LTS will collect logs of the namespaces with names matching this expression. To collect logs of all namespaces, leave this field empty.
- paths Sequence[str]
- Specifies the collection paths. Required when
path_type
iscontainer_file
,container_stdout
orhost_file
. - pod_
name_ strregex - Specifies the regular expression matching of kubernetes pods. LTS will collect logs of the Pods with names matching this expression. To collect logs of all Pods, leave this field empty.
- single_
log_ Ltsformat Cce Access V3Access Config Single Log Format - Specifies the configuration single-line logs. Each log line is displayed as a single log event. The single_log_format structure is documented below.
- stderr bool
Specifies whether error output is standard. Default is
false
.If the value of
path_type
iscontainer_stdout
,stdout
orstderr
must betrue
.- stdout bool
- Specifies whether output is standard. Default is false.
- path
Type String - Specifies the type of the CCE access. The options are as follows:
- black
Paths List<String> - Specifies the collection path blacklist.
- container
Name StringRegex - Specifies the regular expression matching of kubernetes container names. LTS will collect logs of the containers with names matching this expression. To collect logs of all containers, leave this field empty.
- exclude
Envs Map<String> - Specifies the environment variable blacklist. A maximum of
30
tags can be created. The key names must be unique. LTS will exclude all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - exclude
K8s Map<String>Labels Specifies the kubernetes label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are excluded. If labelValue is not empty, only containers whose K8s label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a K8s Label can be excluded as long as it meets any of the blacklists.These parameters include
name_space_regex
,pod_name_regex
,container_name_regex
,log_labels
,include_labels
,exclude_labels
,log_envs
,include_envs
,exclude_envs
,log_k8s
,include_k8s_labels
andexclude_k8s_labels
are available, onlypath_type
is not host_file.The
single_log_format
block supports:- exclude
Labels Map<String> - Specifies the container label blacklist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are excluded. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are excluded. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple blacklists are in the OR relationship. That is, a container label can be excluded as long as it meets any of the blacklists. - include
Envs Map<String> - Specifies the environment variable whitelist. A maximum of
30
tags can be created. The key names must be unique. LTS will match all containers with environment variables containing either an environment variable key with an empty corresponding environment variable value, or an environment variable key with its corresponding environment variable value. LabelKey must be fully matched, and labelValue supports regular expression matching. - include
K8s Map<String>Labels - Specifies the kubernetes label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose K8s label contains labelKey are matched. If labelValue is not empty, only containers whose K8s Label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a K8s label can be matched as long as it meets any of the whitelists. - include
Labels Map<String> - Specifies the container label whitelist. A maximum of
30
tags can be created. The key names must be unique. If labelValue is empty, all containers whose container label contains labelKey are matched. If labelValue is not empty, only containers whose container label containsLabelKey=LabelValue
are matched. LabelKey must be fully matched, and labelValue supports regular expression matching. Multiple whitelists are in the OR relationship. That is, a container label can be matched as long as it meets any of the whitelists. - log
Envs Map<String> - Specifies the environment variable tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each environment variable key has a corresponding environment variable value. For example, if you enterapp
as the key andapp_alias
as the value, when the kubernetes environment variable containsapp=lts
,{app_alias: lts}
will be added to the log. - log
K8s Map<String> - Specifies the kubernetes label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the K8s label containsapp=lts
,{app_alias: lts}
will be added to the log. - log
Labels Map<String> - Specifies the container label log tag. A maximum of
30
tags can be created. The key names must be unique. LTS adds the specified fields to the log when each label key has a corresponding label value. For example, if you enterapp
as the key andapp_alias
as the value, when the Container label containsapp=lts
,{app_alias: lts}
will be added to the log. - multi
Log Property MapFormat Specifies the configuration multi-line logs. Multiple lines of exception log events can be displayed as a single log event. This is helpful when you check logs to locate problems. The multi_log_format structure is documented below.
single_log_format
ormulti_log_format
must be specified.- name
Space StringRegex - Specifies the regular expression matching of kubernetes namespaces. LTS will collect logs of the namespaces with names matching this expression. To collect logs of all namespaces, leave this field empty.
- paths List<String>
- Specifies the collection paths. Required when
path_type
iscontainer_file
,container_stdout
orhost_file
. - pod
Name StringRegex - Specifies the regular expression matching of kubernetes pods. LTS will collect logs of the Pods with names matching this expression. To collect logs of all Pods, leave this field empty.
- single
Log Property MapFormat - Specifies the configuration single-line logs. Each log line is displayed as a single log event. The single_log_format structure is documented below.
- stderr Boolean
Specifies whether error output is standard. Default is
false
.If the value of
path_type
iscontainer_stdout
,stdout
orstderr
must betrue
.- stdout Boolean
- Specifies whether output is standard. Default is false.
LtsCceAccessV3AccessConfigMultiLogFormat, LtsCceAccessV3AccessConfigMultiLogFormatArgs
- Mode string
- Specifies mode of multi-line log format. The options are as follows:
- Value string
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- Mode string
- Specifies mode of multi-line log format. The options are as follows:
- Value string
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- mode String
- Specifies mode of multi-line log format. The options are as follows:
- value String
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- mode string
- Specifies mode of multi-line log format. The options are as follows:
- value string
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- mode str
- Specifies mode of multi-line log format. The options are as follows:
- value str
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- mode String
- Specifies mode of multi-line log format. The options are as follows:
- value String
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
LtsCceAccessV3AccessConfigSingleLogFormat, LtsCceAccessV3AccessConfigSingleLogFormatArgs
- Mode string
- Specifies mode of multi-line log format. The options are as follows:
- Value string
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- Mode string
- Specifies mode of multi-line log format. The options are as follows:
- Value string
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- mode String
- Specifies mode of multi-line log format. The options are as follows:
- value String
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- mode string
- Specifies mode of multi-line log format. The options are as follows:
- value string
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- mode str
- Specifies mode of multi-line log format. The options are as follows:
- value str
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
- mode String
- Specifies mode of multi-line log format. The options are as follows:
- value String
Specifies value of multi-line log format.
- If mode is
regular
, the value is a regular expression. - If mode is
time
, the value is a time wildcard, which is used to look for the log printing time as the beginning of a log event. If the time format in a log event is2019-01-01 23:59:59
, the time wildcard isYYYY-MM-DD hh:mm:ss
. If the time format in a log event is19-1-1 23:59:59
, the time wildcard isYY-M-D hh:mm:ss
.
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. In general cases, you are advised to select
Single-line
for Log Format andsystem
time for Log Time.- If mode is
Import
The CCE access can be imported using id
, e.g.
bash
$ pulumi import opentelekomcloud:index/ltsCceAccessV3:LtsCceAccessV3 test <id>
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- opentelekomcloud opentelekomcloud/terraform-provider-opentelekomcloud
- License
- Notes
- This Pulumi package is based on the
opentelekomcloud
Terraform Provider.