Google 对数据流生成的数据流作业日志收费
Google charging for Dataflow Job logs generated by the dataflow
Google 正在对管道本身生成的数据流作业日志收费，我们不会从该作业生成任何日志，我们是 运行 使用 python 通过 composer 的数据流作业-apache 光束。
这没有任何意义，因为我们没有生成任何日志，而且我们没有太多关于如何关闭生成的日志并提取到云日志记录的信息。
Google 我们收到了邮件
We’re writing to remind you that starting October 12, 2021, logs that your Dataflow applications generate (and are ingested and stored in Google Cloud Logging) will be charged at the standard Cloud Logging prices. You will still receive the free tier of 50 GB of total (across all log volume) ingested logs per project per month. This is a follow-up to the communication we sent on July 12, 2021.
What do I need to do?
We recommend that you review your usage of Dataflow Job logging in Cloud Logging by performing the following steps before October 12, 2021:
View your usage metrics using Metrics Explorer in Cloud Monitoring.
Save the chart you used in the previous step into a Cloud Monitoring dashboard or use the Dataflow usage open source dashboard template.
Refer to controlling Dataflow log volume for information on optimizing log volume for your Dataflow jobs.
从 Dataflow 查看 Cloud Logging 中的注入日志并搜索 LOG_ID，然后修改 _Default 接收器以排除它们。
默认配置如下：
NOT LOG_ID("cloudaudit.googleapis.com/activity") AND NOT
LOG_ID("externalaudit.googleapis.com/activity") AND NOT
LOG_ID("cloudaudit.googleapis.com/system_event") AND NOT
LOG_ID("externalaudit.googleapis.com/system_event") AND NOT
LOG_ID("cloudaudit.googleapis.com/access_transparency") AND NOT
LOG_ID("externalaudit.googleapis.com/access_transparency")
请参考docs
Google 正在对管道本身生成的数据流作业日志收费，我们不会从该作业生成任何日志，我们是 运行 使用 python 通过 composer 的数据流作业-apache 光束。
这没有任何意义，因为我们没有生成任何日志，而且我们没有太多关于如何关闭生成的日志并提取到云日志记录的信息。
Google 我们收到了邮件
We’re writing to remind you that starting October 12, 2021, logs that your Dataflow applications generate (and are ingested and stored in Google Cloud Logging) will be charged at the standard Cloud Logging prices. You will still receive the free tier of 50 GB of total (across all log volume) ingested logs per project per month. This is a follow-up to the communication we sent on July 12, 2021.
What do I need to do?
We recommend that you review your usage of Dataflow Job logging in Cloud Logging by performing the following steps before October 12, 2021: View your usage metrics using Metrics Explorer in Cloud Monitoring. Save the chart you used in the previous step into a Cloud Monitoring dashboard or use the Dataflow usage open source dashboard template. Refer to controlling Dataflow log volume for information on optimizing log volume for your Dataflow jobs.
从 Dataflow 查看 Cloud Logging 中的注入日志并搜索 LOG_ID，然后修改 _Default 接收器以排除它们。
默认配置如下：
NOT LOG_ID("cloudaudit.googleapis.com/activity") AND NOT LOG_ID("externalaudit.googleapis.com/activity") AND NOT LOG_ID("cloudaudit.googleapis.com/system_event") AND NOT LOG_ID("externalaudit.googleapis.com/system_event") AND NOT LOG_ID("cloudaudit.googleapis.com/access_transparency") AND NOT LOG_ID("externalaudit.googleapis.com/access_transparency")
请参考docs