-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
2 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -111,8 +111,7 @@ Follow the [instructions on GCP docs](https://cloud.google.com/sql/docs/postgres | |
resource.labels.database_id="<GCP_PROJECT_ID>:<CLOUDSQL_INSTANCE_NAME>" | ||
``` | ||
|
||
If you deployed the dummy postgres application used earlier in this tutorial, | ||
you should be seeing audit records generated by it periodically. | ||
If your Cloud SQL instance is handling any requests, you should be seeing audit records generated by it periodically. | ||
|
||
### Route Cloud SQL audit logs to a Pub/Sub destination | ||
Otterize Cloud consumes audit logs collected from your Cloud SQL instancec by subscribing to a pub/sub topic in your GCP project. | ||
|
@@ -132,7 +131,7 @@ to configure a log sink and route your Cloud SQL instance's audit logs through a | |
[email protected] | ||
``` | ||
|
||
If you deployed the dummy postgres application used earlier in this tutorial, | ||
If your Cloud SQL instance is handling any requests, | ||
you may now open your [Pub/Sub topic's metrics](https://console.cloud.google.com/cloudpubsub/topic/list) page | ||
and observe how audit log records are being directed to it. | ||
|
||
|