Establish a Data Lake from Cloud Logging to BigQuery with Apigee




Create a sink

Create a service account using IAM and service key

Exporting logs in bigquery

Testing the API Proxy in Apigee REST Client

Establish a Data Lake from Cloud Logging to BigQuery with Apigee

1時間 30分 クレジット: 5


Google Cloud Self-Paced Labs


Apigee Edge enables you to quickly expose backend services as APIs. You do this by creating an API proxy that provides a facade for the backend service that you want to expose. You only need to provide the network address for the backend service, along with some information that Edge uses to create the API proxy that is exposed to developers.

The API proxy decouples your backend service implementation from the API that developers consume. This shields developers from future changes to your backend services. As you update backend services, developers, insulated from those changes, can continue to call the API uninterrupted.

API proxies give you the full power of Apigee's API platform to secure API calls, throttle traffic, mediate messages, control error handling, cache things, build developer portals, document APIs, analyze API traffic data, make money on the use of your APIs, protect against bad bots, and more.

Apigee Extensions is a feature that can help you integrate external resources into your API proxies. For example, you could integrate Google Cloud services such as Google Cloud Storage, Cloud Logging (formerly Stackdriver Logging), BigQuery etc. with your API proxy running on Apigee Edge. At run time, an API proxy uses the extension to exchange requests and responses with the external resource.

In this lab, you will learn how to export Cloud Logging data to BigQuery for analysis, then provide access to this aggregated data via APIs using Apigee Edge.

Qwiklabs に参加してこのラボの残りの部分や他のラボを確認しましょう。

  • Google Cloud Console への一時的なアクセス権を取得します。
  • 初心者レベルから上級者レベルまで 200 を超えるラボが用意されています。
  • ご自分のペースで学習できるように詳細に分割されています。