Observability Analytics

Related topics

• log bucket works with Observability Analytics From the official documentation: “Make sure that you have a log bucket that is upgraded to use Observability Analytics.”
• Logs Explorer is an alternative to Observability Analytics From the official documentation: “You can display the log entries in a log view by using the Logs Explorer or by using the **Observability Analytics** page.”
• BigQuery is an alternative to Observability Analytics From the official documentation: “To query your trace data by using SQL, you can either use Observability Analytics or BigQuery:”
• Observability Analytics depends on log bucket From the official documentation: “Ensure that your log buckets have been upgraded to use Observability Analytics:”
• BigQuery works with Observability Analytics From the official documentation: “To open BigQuery from the Observability Analytics and then query your log data, do the following:”
• log view works with Observability Analytics From the official documentation: “You can query log views with the Logs Explorer or with Observability Analytics.”
• Model Armor works with Observability Analytics From the official documentation: “To query and analyze telemetry data from Model Armor, use Observability Analytics, which provides a SQL-based query interface.”
• Observability Analytics is part of Cloud Logging From the official documentation: “You can view the log entries that result from your OTLP logs by using any of the Cloud Logging tools, including Logs Explorer and Observability Analytics.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• 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.”
• Logs Explorer is part of Cloud Logging From the official documentation: “To view and filter Model Armor logs, use the Logs Explorer in Logging:”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• 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 works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• 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”
• log bucket is part of Cloud Logging From the official documentation: “An export bucket in Cloud Logging.”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• 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 Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Cloud Logging works with Model Armor From the official documentation: “Use Cloud Logging to analyze Model Armor usage patterns, errors, and performance metrics.”
• 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.”
• log view is part of log bucket From the official documentation: “Each log view is on a log bucket.”
• 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 works with Cloud Monitoring From the official documentation: “If a log entry matches the filter of the alerting policy, then Cloud Logging extracts labels and forwards the data to Cloud Monitoring.”
• Cloud Monitoring works with Model Armor From the official documentation: “This graph uses the metrics that Model Armor publishes to Cloud Monitoring.”
• Customer-managed encryption keys secures Cloud Logging From the official documentation: “Cloud Logging supports encrypting Log storage with CMEK keys.”
• Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
• BigQuery works with log bucket From the official documentation: “The following error is shown in response to a `delete` command on a log bucket that has a linked BigQuery dataset:”
• 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.”
• Cloud Audit Logs works with Cloud Logging From the official documentation: “For real-time analysis, alerting, and visualization, stream the audit logs to [Cloud Logging](/logging/docs/overview).”
• Cloud Audit Logs works with Logs Explorer From the official documentation: “You can audit the history of BigQuery tables by querying Cloud Audit Logs in Logs Explorer.”
• Cloud Audit Logs works with Model Armor From the official documentation: “Model Armor uses audit logs to record administrative and resource management activities.”
• 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 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.”
• Cloud Logging works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
• Cloud Monitoring depends on Identity and Access Management From the official documentation: “To use Monitoring, you must have the appropriate [Identity and Access Management](/iam/docs/overview) (IAM) permissions.”
• Cloud Monitoring works with VPC Service Controls From the official documentation: “Cloud Monitoring performs the VPC perimeter check when a project is *added* to a metrics scope:”
• Customer-managed encryption keys secures log bucket From the official documentation: “Cloud Logging log buckets can be configured to encrypt data with CMEK.”
• Identity and Access Management secures Cloud Audit Logs From the official documentation: “IAM permissions and roles determine your ability to access audit logs data in the [Logging API](/logging/docs/reference/v2/rest), the [Logs Explorer](/logging/docs/view/logs-explorer-interface), and the [Google Cloud CLI](/logging/docs/reference/tools/gcloud-logging).”
• Identity and Access Management secures log bucket From the official documentation: “[IAM](/iam/docs/overview) permissions and roles control access to log data. For example, you can do all of the following: - Grant read and edit access to a log bucket.”
• Identity and Access Management secures log view From the official documentation: “You control access to a log view by using [Identity and Access Management (IAM)](/iam/docs/overview).”
• Identity and Access Management works with Logs Explorer From the official documentation: “To find audit logs for Identity and Access Management, use the following queries in the Logs Explorer:”
• Identity and Access Management secures Model Armor From the official documentation: “Model Armor uses Identity and Access Management (IAM) to control access to resources.”
• log view works with Logs Explorer From the official documentation: “You can query log views with the Logs Explorer or with Observability Analytics.”
• Logs Explorer works with Model Armor From the official documentation: “To query raw text security log entries in the **Logs Explorer**, you can use the `logName` field to search for Model Armor sanitization content results.”
• Logs Explorer works with Pub/Sub From the official documentation: “You can use **Logs Explorer** to view Pub/Sub logs.”
• Model Armor depends on Identity and Access Management From the official documentation: “Model Armor uses Identity and Access Management (IAM) to control access to resources.”
• VPC Service Controls secures Cloud Logging From the official documentation: “The API for Cloud Logging can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• VPC Service Controls secures Cloud Monitoring From the official documentation: “VPC Service Controls provides additional security for Cloud Monitoring to help mitigate the risk of data exfiltration.”
• VPC Service Controls secures Model Armor From the official documentation: “The API for Model Armor can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”