Logs Explorer

Related topics

• Cloud Audit Logs works with Logs Explorer From the official documentation: “You can query these logs in the Logs Explorer and check which API methods generate Cloud Audit Logs.”
• Cloud Logging works with Logs Explorer From the official documentation: “VM serial console logs are streamed to Cloud Logging and can be viewed in Logs Explorer.”
• logs works with Logs Explorer From the official documentation: “You can also click **View Logs** and view the log by using the Logs Explorer.”
• Logs Explorer is part of Cloud Logging From the official documentation: “To view and filter Model Armor logs, use the Logs Explorer in Logging:”
• Logs Explorer works with Managed Service for Apache Airflow From the official documentation: “You can query these logs in the Logs Explorer and check which Managed Service for Apache Airflow API methods generate Cloud Audit Logs.”
• BigQuery Data Transfer Service works with Logs Explorer From the official documentation: “You can also view error messages for a specific transfer job using the [Logs Explorer](/logging/docs/view/logs-explorer-interface).”
• log entries works with Logs Explorer From the official documentation: “You can use the Logs Explorer to find, filter, and exclude log entries that belong to [error groups](/error-reporting/docs/grouping-errors) to help identify trends and recurring problems in your environment.”
• Logs Explorer works with Looker (Google Cloud core) From the official documentation: “To find audit logs for Looker (Google Cloud core), use the following queries in the Logs Explorer:”
• Logs Explorer works with Pub/Sub From the official documentation: “You can use **Logs Explorer** to view Pub/Sub logs.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Customer-Managed Encryption Keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• BigQuery works with BigQuery Data Transfer Service From the official documentation: “The BigQuery Data Transfer Service uses load jobs to load Amazon S3 data into BigQuery.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• BigQuery is an alternative to Google Cloud Storage From the official documentation: “The training data can be either a CSV file in Cloud Storage or a table in BigQuery.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Audit Logs works with Cloud Storage From the official documentation: “This page provides supplemental information for using [Cloud Audit Logs](/logging/docs/audit) with Cloud Storage.”
• Cloud Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Customer-Managed Encryption Keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
• Customer-Managed Encryption Keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
• BigQuery works with Managed Service for Apache Airflow From the official documentation: “You can use Managed Airflow to orchestrate services in your data pipelines, such as triggering a job in BigQuery or starting a Dataflow pipeline.”
• BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• BigQuery Data Transfer Service works with Cloud Storage From the official documentation: “- [Cloud Storage](/bigquery/docs/cloud-storage-transfer)”
• Customer-Managed Encryption Keys secures Managed Service for Apache Airflow From the official documentation: “This page describes how to use [Customer Managed Encryption Keys (CMEK)](/kms/docs/cmek) to protect Managed Airflow environments.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• VPC Service Controls secures Managed Service for Apache Airflow From the official documentation: “Managed Airflow can be selected as a secured service inside a VPC Service Controls perimeter.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Looker (Google Cloud core) From the official documentation: “If your Looker instance relies on BigQuery, you must explicitly grant the required BigQuery roles to your Looker service agent:”
• BigQuery Data Transfer Service works with Cloud Logging From the official documentation: “The BigQuery Data Transfer Service exports logs and metrics to Cloud Monitoring and Cloud Logging that provide observability into your transfers.”
• BigQuery Data Transfer Service works with Pub/Sub From the official documentation: “If you intend to set up transfer run notifications for Pub/Sub, you must have `pubsub.topics.setIamPolicy` permissions.”
• Cloud Audit Logs works with Pub/Sub From the official documentation: “Working with audit logs Learn about the default and optional logs created by Pub/Sub as part of Cloud Audit Logs”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Logging works with Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud Logging works with Google Cloud Storage From the official documentation: “Cloud Logging can [route logs](/logging/docs/export/configure_export_v2) to Cloud Storage by Google SecOps on a scheduled basis.”
• Cloud Logging is an alternative to Google Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs in a Cloud Logging bucket, in a user-created Cloud Storage bucket, or in a Google Cloud-created and user-owned Cloud Storage bucket.”
• Cloud Monitoring works with Managed Service for Apache Airflow From the official documentation: “To learn about Cloud Logging and Cloud Monitoring for your Managed Airflow environment, see [Monitor environments](/composer/docs/composer-2/monitor-environments).”
• Cloud Monitoring works with Pub/Sub From the official documentation: “Use Cloud Monitoring and Pub/Sub to set up custom monitoring and alerting policies for exported logs.”
• Cloud Storage works with Managed Service for Apache Airflow From the official documentation: “When you upload your DAG file to the `dags/` folder in Cloud Storage, Managed Airflow parses the file.”
• Customer-Managed Encryption Keys depends on Cloud Storage From the official documentation: “If used for storing Customer-managed Encryption Keys (CMEK): Cloud Storage (See [Cloud Storage pricing](/storage/pricing).)”
• Customer-Managed Encryption Keys secures Looker (Google Cloud core) From the official documentation: “Looker (Google Cloud core) uses a single CMEK key (through a hierarchy of secondary keys) to help protect the sensitive data that is managed by the Looker (Google Cloud core) instance.”
• Looker (Google Cloud core) works with VPC Service Controls From the official documentation: “VPC Service Controls support for Looker (Google Cloud core)”
• Managed Service for Apache Airflow depends on Google Cloud Storage From the official documentation: “Managed Airflow uses a [Cloud Storage](/storage) bucket to store DAGs of your Managed Airflow environment.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with VPC Service Controls From the official documentation: “BigQuery integrates with VPC Service Controls to restrict access to your BigQuery resources from specific networks.”
• BigQuery Data Transfer Service works with Cloud Monitoring From the official documentation: “The BigQuery Data Transfer Service exports logs and metrics to Cloud Monitoring and Cloud Logging that provide observability into your transfers.”
• BigQuery Data Transfer Service works with Customer-Managed Encryption Keys From the official documentation: “When you specify a CMEK with a transfer, the BigQuery Data Transfer Service applies the CMEK to any intermediate on-disk cache of ingested data so that the entire data transfer workflow is CMEK compliant.”
• BigQuery Data Transfer Service works with Google Cloud Storage From the official documentation: “As part of the data transfer, BigQuery Data Transfer Service writes data from Amazon Redshift to Cloud Storage as CSV files.”
• BigQuery Data Transfer Service works with Managed Service for Apache Airflow From the official documentation: “**Managed Service for Apache Airflow jobs**: you can schedule [Managed Service for Apache Airflow](/composer) jobs to issue ETL jobs that create regional subsets before triggering the BigQuery Data Transfer Service through its [client API](/bigquery/docs/reference/libraries).”
• BigQuery Data Transfer Service depends on Pub/Sub From the official documentation: “The communication channel between the agent running on premises and BigQuery Data Transfer Service is by publishing Pub/Sub messages to a per transfer topic.”
• Cloud Audit Logs secures BigQuery From the official documentation: “For BigQuery, [Cloud Audit Logs](/logging/docs/audit) is used for both data access logs and audit logs, which are enabled by default.”