audit logs

Related topics

• audit logs is part of Cloud Logging From the official documentation: “You can run [BigQuery-standard SQL](/bigquery/docs/reference/standard-sql) queries on the **Observability Analytics** page to aggregate and analyze your Cloud Logging audit logs.”
• audit logs is part of Compute Engine From the official documentation: “Compute Engine audit logs contain the same information that is available through activity logs, and more.”
• audit logs works with logs From the official documentation: “- **Audit logs** (`auditloki`) to display audit logs.”
• audit logs works with Private Service Connect From the official documentation: “Audit logs let you monitor Private Service Connect activity.”
• Data Access audit logs is part of audit logs From the official documentation: “- **Data Access audit logs**: Data Access audit logs record API calls that read the configuration or metadata of resources, as well as user-driven API calls that create, modify, or read user-provided resource data. Because accessing data is a frequent API operation, these logs…”
• Pub/Sub configures audit logs From the official documentation: “If the subscription and the topic are in different Google Cloud projects, the Pub/Sub service adds an entry to the audit logs of both projects.”
• 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.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• 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 Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• 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.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• 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 Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• 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.”
• 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 Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• Cloud Service Mesh works with Private Service Connect From the official documentation: “Published service backends let you configure regional Cloud Service Mesh to route traffic to published services through Private Service Connect.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• App Engine works with Cloud Logging From the official documentation: “App Engine automatically sends both the request logs and app logs to the [Cloud Logging](/logging/docs/overview) agent.”
• App Engine works with Cloud Monitoring From the official documentation: “This tutorial shows how to set up an uptime alert for the [Python Hello World app](/python/getting-started/hello-world) running on App Engine flexible environment using [Cloud Monitoring](/monitoring/docs).”
• App Engine works with Cloud Storage From the official documentation: “To use a Cloud Storage bucket from an App Engine app:”
• App Engine works with Compute Engine From the official documentation: “Your App Engine app can communicate with services hosted on Compute Engine within the same project without going through the public internet.”
• App Engine works with Pub/Sub From the official documentation: “Pub/Sub is now the preferred way of performing pull queue work in App Engine.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Data Access audit logs From the official documentation: “- Search for changes to a specific BigQuery dataset in the Data Access audit logs:”
• BigQuery works with Private Service Connect From the official documentation: “Click the private zone that contains the DNS records for the Private Service Connect endpoints, which you created to allow BigQuery Toolkit for SAP to privately connect to the BigQuery and IAM APIs.”
• 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 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 Service Mesh works with Compute Engine From the official documentation: “Cloud Service Mesh supports a variety of infrastructures (GKE/Kubernetes, Compute Engine) and environments (on-premises, other clouds).”
• GKE works with Pub/Sub From the official documentation: “GKE publishes upgrade notifications to [Pub/Sub](/pubsub/docs/overview), providing you with a channel to receive information from GKE about your clusters.”
• App Engine works with BigQuery From the official documentation: “App Engine - Scalable platform as a service (PaaS) solution used to call the Monitoring API and write to BigQuery.”
• App Engine depends on Cloud Storage From the official documentation: “App Engine creates a [default Cloud Storage multi-regional bucket](/appengine/docs/flexible/locations#cloud-storage-location) on your behalf on the same region where it creates your application. It requires this bucket to store the contents of your application.”
• App Engine is an alternative to Cloud Storage From the official documentation: “You can use durable storage like Cloud Storage or an in-memory cache like App Engine to share data between pipeline instances.”
• App Engine works with Private Service Connect From the official documentation: “App Engine instances with external IP addresses can send traffic to Private Service Connect endpoints without any requirements.”
• 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 Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• BigQuery works with GKE From the official documentation: “Subsequently, by integrating BigQuery with GKE, you can use BigQuery to efficiently handle massive datasets (like Google Analytics) and the model's natural language understanding capabilities to generate meaningful insights.”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
• Cloud Monitoring works with Private Service Connect From the official documentation: “Private Service Connect exposes key metrics to Cloud Monitoring that give you insights into your Private Service Connect connections.”
• Cloud Storage works with Data Access audit logs From the official documentation: “- To identify potential misuse of APIs, or data hosted in services like Cloud Storage or BigQuery, use Data Access audit logs. For a sample query that identifies this scenario, see [Identify high API usage by a principal](#high-api-usage).”
• Data Access audit logs is part of Cloud Service Mesh From the official documentation: “The following types of audit logs are available for Cloud Service Mesh:”
• GKE works with Private Service Connect From the official documentation: “This page provides an overview of Private Service Connect in Google Kubernetes Engine (GKE) clusters.”