Mostyn Bramley-Moore

Hi, One way that you can achieve this is to setup a http reverse proxy which only allows GET and HEAD requests, and use firewall rules to allow your CI...

Hi, unfortunately I think bazel-remote's current metrics aren't good enough for your needs. Hopefully that will change soon (my target is 2-3 weeks) - I'm working on this in #472,...

One way that I use in .bazelci/system-test.sh is to run bazel with [--execution_log_json_file](https://docs.bazel.build/versions/main/command-line-reference.html#flag--execution_log_json_file) and then extract the number of hits and misses from that after the build finishes. You could...

bazel-remote has some hit/miss prometheus metrics, but all the request types (action cache, CAS) are mixed up so the numbers aren't particularly useful right now. High hit:miss ratios are generally...

I think the most important metric is the action cache hit rate, so for a particular time period you'd want to count `{status=="hit" && kind=="ac" && (method=="get" || method=="contains")}` and...

> Hi this is a question instead of a bug fix. I know for remote-cache request, it will first as AC and then CAS. But if we only have local...

@kragniz: if you'd be willing to share some example configurations, I'd love to add it to an examples doc or directory here.

@BoyangTian-Robinhood: are you still looking for help with this?

Hi, I don't think bazel-remote currently has a good solution for this. I suspect that most users of bazel-remote's s3 backend simply have deep pockets and never delete s3 objects,...

I don't think S3 keeps track of the last access time for a blob, so I'm not sure what we would scan for.