Closed andersosthus closed 3 years ago
👋 @andersosthus. Please do not use the same bucket for blocks storage and ruler/alertmanager config. We recently updated the blocks storage architecture doc to mention it.
Thanks, didn't notice that when upgrading :)
Thanks, didn't notice that when upgrading :)
Our fault for not making it prominent enough. Sorry for that!
Hi,
May I know what needs to be present in the fake
directory that you have created.
When I upload the Alerting rules in the S3, the ruler is keep on complaining 'invalid rule group object key'. Can you please let me know what is the format of the alert group file that we need to use?
level=warn ts=2021-08-04T17:16:03.112097009Z caller=bucket_client.go:110 msg="invalid rule group object key found while listing rule groups" key=operations/ err="invalid rule group object key"
level=warn ts=2021-08-04T17:16:03.112201241Z caller=bucket_client.go:110 msg="invalid rule group object key found while listing rule groups" key=operations/rules-operations.yaml err="invalid rule group object key"
Describe the bug Setup:
Every minute I see the following in the Ruler log:
level=warn ts=2021-06-14T09:37:41.691305994Z caller=bucket_client.go:110 msg="invalid rule group object key found while listing rule groups" key=bucket-index.json.gz err="invalid rule group object key"
Looking in the S3 bucket, I see that under the prefix
rules/
, there is abucket-index.json.gz
file that I suspect the ruler tries to load.I haven't seen any recommendations about separating blocks and rules into separate S3 buckets, so that's why I've kept it all in one.
Not sure if this is "as intended", or a side-effect of the
blocks-index
feature not filtering out therules/
prefix, or the fact that the Ruler tries to load thebucket-index.json.gz
file even though it is not in an Org prefix.I've attached a screenshot of the S3
rules/
prefix below.Not sure if this is only present in 1.9.0, or also in earlier versions. We were running 1.6.0, so I upgraded through to 1.9.0 during this weekend, and didn't notice it until now.
Environment:
Storage Engine
Additional Context Ruler config:
Debug logs from Ruler during startup:
Logs during normal Ruler operation:
S3
rules/
prefix: