Configure a central bucket

Preview

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

You can decide to not store logs in the _Default bucket to route them to a central networking bucket (or multiple buckets for larger organizations).

You can achieve this by performing any of the following:

• Use an aggregated sink configured at the folder or organization level. Optionally, such a sink allows intercept logs to avoid duplication.
• Manually configure sinks in projects to route traffic to specific buckets.

To analyze networking logs in the organization using Log Analytics, we recommend you route them to the central networking bucket before you enable VPC Flow Logs.

1. Create a bucket.
2. Route logs to the newly created bucket. For more information, see Route logs to supported destinations.
3. Collate and route organization-level logs to supported destinations.
4. Configure log routing for each project.
5. Enable VPC Flow Logs for each resource.

Route logs from the projects to a central bucket

By default, Log Analytics lets you analyze the logs in a single log bucket. To view data from multiple projects, you must create a central log bucket and route logs to this central bucket.

The bucket that is used to store networking logs must be upgraded to support Log Analytics.