-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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.
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
downsample: Downsample requires gcs_bucket even when using S3 #494
Comments
Happens even on the latest image: |
Valid bug |
I have submitted #496 for this bug. It should fix this issue, however I do not have any google cloud storage to test against to verify. I also included a very small fix to the contributors guide, as the instructions for setting up the remote were backwards. ("git add remote", vs "git remote add".) |
@xphyr waiting for you to rebase and feel free to update contributor guide as well. Thanks! |
Oh, sorry. I will rebase and resubmit. Sorry for the delay. |
should be closed |
Thanos, Prometheus and Golang version used
docker improbable/thanos:v0.1.0-rc.2
What happened
Attempt to run thanos downsample with only s3 and thanos exits saying that the gcs_bucket hasn't been defined.
downsample --data-dir /prometheus --s3.endpoint ourserver:46214 --s3.bucket prometheus --s3.access-key stuff --log.level=debug
Error parsing commandline arguments: required flag --gcs.bucket not provided
usage: thanos downsample --gcs.bucket=<bucket> [<flags>]
What you expected to happen
Thanos downsample to run like compact minus the compact
How to reproduce it (as minimally and precisely as possible):
See command above
Environment:
uname -a
): 4.14.62-70.117.amzn2.x86_64The text was updated successfully, but these errors were encountered: