gcloud alpha logging settings describe

NAME
gcloud alpha logging settings describe - display the settings for the Cloud Logging Logs Router
SYNOPSIS
gcloud alpha logging settings describe [--billing-account=BILLING_ACCOUNT_ID     | --folder=FOLDER_ID     | --organization=ORGANIZATION_ID     | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) If kmsKeyName is present in the output, then CMEK is enabled for your project, folder, organization or billing-account. You can also find the Logs Router service account using this command.
EXAMPLES
To describe the Logs Router settings for a project, run:
gcloud alpha logging settings describe --project=[PROJECT_ID]

To describe the Logs Router settings for an organization, run:

gcloud alpha logging settings describe --organization=[ORGANIZATION_ID]
kmsKeyName:
'projects/my-project/locations/my-location/keyRings/my-keyring/cryptoKeys/key'
name: 'organizations/[ORGANIZATION_ID]/settings'
serviceAccountId:
'[SERVICE_ACCOUNT_ID]@gcp-sa-logging.iam.gserviceaccount.com'
FLAGS
At most one of these can be specified:
--billing-account=BILLING_ACCOUNT_ID
Billing account of the settings to describe.
--folder=FOLDER_ID
Folder of the settings to describe.
--organization=ORGANIZATION_ID
Organization of the settings to describe.
--project=PROJECT_ID
Project of the settings to describe.

The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be listed using gcloud config list --format='text(core.project)' and can be set using gcloud config set project PROJECTID.

--project and its fallback core/project property play two roles in the invocation. It specifies the project of the resource to operate on. It also specifies the project for API enablement check, quota, and billing. To specify a different project for quota and billing, use --billing-project or billing/quota_project property.

GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.

Run $ gcloud help for details.

NOTES
This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. These variants are also available:
gcloud logging settings describe
gcloud beta logging settings describe