gdcloud logging targets create

NAME

gdcloud logging targets create - Create a logging target in the given namespace.

SYNOPSIS

gdcloud logging targets create LOGGING_TARGET_NAME [flags]

EXAMPLES

To create a logging target, run:

    gdcloud logging targets create logging-target-name \
        --namespace=sample_namespace  \
        --match-clusters=cluster1,cluster2 \
        --match-pod-name-prefixes=pod-prefix1,pod-prefix2 \
        --match-container-name-prefixes=container-prefix1,container-prefix2 \
        --parser=json \
        --log-access-level=pa \
        --service-name=sample_service_name \
        --additional-fields={\"fieldName\": \"field-value\"}

REQUIRED FLAGS

      --namespace string      Namespace of the operational logs to collect.
      --service-name string   Service name to apply as a label. For user workloads, this could be also considered as a workload name.

OPTIONAL FLAGS

      --additional-fields string               Additional static fields to apply to log entries. Field name must not contain '-' character.
      --log-access-level string                Access level for log entries. Available options are: [ao, pa, io]. (default "ao")
      --match-clusters string                  Comma-separated list of cluster names to consider for the log collection job.
      --match-container-name-prefixes string   Comma-separated list of container name prefixes where logs are collected.
      --match-pod-name-prefixes string         Comma-separated list of pod name prefixes where logs are collected.
      --parser string                          Predefined parser for log entries. Available options are: [klog_text, klog_json, klogr, gdch_json, json].

GDCLOUD WIDE FLAGS

These flags are available to all commands: --configuration, --format, --help, --project, --quiet.

For more information, see the gdcloud CLI reference overview page.