gcloud alpha logging locations describe - display information about a location
gcloud alpha logging locations describe LOCATION_ID [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...]
(ALPHA) Displays information about a location.
To describe a location in a project, run:
$ gcloud alpha logging locations describe my-location
- LOCATION_ID
Id of the location to describe.
- At most one of these can be specified:
- --billing-account=BILLING_ACCOUNT_ID
Billing account of the location to describe.
- --folder=FOLDER_ID
Folder of the location to describe.
- --organization=ORGANIZATION_ID
Organization of the location to describe.
- --project=PROJECT_ID
Project of the location 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.
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.
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 locations describe
$ gcloud beta logging locations describe