Apigee API hub
Feature
API insights in API hub
API insights is now available in API hub, providing a unified view of your API traffic and performance across all connected gateways. With API insights, you can gain a holistic understanding of your API ecosystem’s health and quickly identify areas for optimization.
Currently, API insights supports data sources from Apigee, Apigee hybrid, Apigee Edge Public Cloud, and Apigee Edge Private Cloud (OPDK).
For more information, see API insights overview.
Feature
Detailed API resource insights
A new Insights tab is now available on the API details page, providing API-centric analytics to help you understand usage patterns and performance for each of your APIs.
You can now analyze key metrics such as total traffic, average TPS, request/response latencies, and more, directly from the API details page.
For more information, see View API resource insights.
BigQuery
Feature
The BigQuery Data Transfer Service can now transfer data from the following data sources:
Transfers from these data sources are now generally available (GA).
Feature
Subscriber email logging lets you log the principal identifiers of users
who execute jobs and queries against linked datasets. You can enable
logging at the
listing level
and the
data exchange level.
The logged data is available in the job_principal_subject field of the
INFORMATION_SCHEMA.SHARED_DATASET_USAGE view.
This feature is
generally available.
Cloud Load Balancing
Feature
Application Load Balancers support authorization policies that let you establish access control checks for incoming traffic.
For details, see Authorization policy overview.
This feature is in General availability.
Feature
Both internal passthrough Network Load Balancers and external passthrough Network Load Balancers now support load balancing to managed instance groups (MIGs) comprised of IPv6-only VM instances.
For more details, see the following pages:
- Set up an external passthrough Network Load Balancer with a backend service
- Set up an internal passthrough Network Load Balancer with VM instance group backends
This feature is now in General availability.
Cloud SQL for MySQL
Feature
Cloud SQL has enhanced the optimized writes feature, which includes an improved crash recovery algorithm to reduce crash recovery time and utilizes unused disk I/O throughput adaptively to accelerate buffer pool warm-up. The optimized writes feature provides a set of write performance improvements that adjust MySQL configurations dynamically based on workload demand and underlying infrastructure.
By default these improvements are enabled for all new Cloud SQL Enterprise Plus edition instances that you create or that you upgrade to from Cloud SQL Enterprise edition.
For more information about optimized writes, see Configure database flags.
Compute Engine
Feature
Generally available: You can create managed instance groups (MIGs) comprised of IPv6-only VM instances.
For more information, see Basic scenarios for creating managed instance groups (MIGs).
Google Kubernetes Engine
Feature
Autoscaled blue-green upgrades are a type of node upgrade strategy that maximizes the amount of time before disruption-intolerant workloads are evicted, while minimizing cost. This feature is available in Preview for GKE Standard node pools. For more information, see Autoscaled blue-green upgrades.
Feature
You can use the G4 VM, powered by NVIDIA’s RTX PRO 6000 GPUs, with GKE Autopilot in version 1.34.1-gke.1829001 or later. To get started, see Deploy GPU workloads in Autopilot.
Google SecOps
Feature
Risk-based alerting with entity-only rules
With the new ENTITY_RISK_CHANGE UDM event type, you can now write YARA-L
detection rules that trigger independently of ingested events. This capability
lets you focus specifically on changes in an entity’s risk score, significantly
decreasing the time required for Google Security Operations to detect and alert
on shifting entity risk levels.
For more information, see Risk-based alerting with entity-only rules.
Google SecOps SIEM
Feature
Risk-based alerting with entity-only rules
With the new ENTITY_RISK_CHANGE UDM event type, you can now write YARA-L
detection rules that trigger independently of ingested events. This capability
lets you focus specifically on changes in an entity’s risk score, significantly
decreasing the time required for Google Security Operations to detect and alert
on shifting entity risk levels.
For more information, see Risk-based alerting with entity-only rules.
Feature
Risk-based alerting with entity-only rules
With the new ENTITY_RISK_CHANGE UDM event type, you can now write YARA-L
detection rules that trigger independently of ingested events. This capability
lets you focus specifically on changes in an entity’s risk score, significantly
decreasing the time required for Google Security Operations to detect and alert
on shifting entity risk levels.
For more information, see Risk-based alerting with entity-only rules.
Source: Google Cloud Platform
