Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added docs for GCP configuration. #595

Merged
merged 1 commit into from
Mar 16, 2021
Merged

Added docs for GCP configuration. #595

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/tempo/website/configuration/gcs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,19 @@ GCS backend is configured in the storage block. Tempo requires a dedicated bucke
storage:
trace:
backend: gcs # store traces in gcs
s3:
gcs:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:D

bucket_name: tempo # store traces in this bucket
chunk_buffer_size: 10485760 # optional. buffer size for reads. default = 10MiB
endpoint: https://storage.googleapis.com/storage/v1/ # optional. api endpoint override
insecure: false # optional. Set to true to disable authentication
# and certificate checks.
```
## Permissions
The following authentication methods are supported:
- GCP environment variable GOOGLE_APPLICATION_CREDENTIALS

The (service-)account that will communicate towards GCS should be assigned to the bucket which will receive the traces and should have the following IAM polices within the bucket:

- `storage.objects.create`
- `storage.objects.delete`
- `storage.objects.get`