Krishnan Parthasarathi

These metrics are also available via `mc admin tier info ALIAS`. Sample output ``` ┌──────────┬────────┬────┬───────┬───────┬────────┐ │ Name │ API │Type│ Usage │Objects│Versions│ ├──────────┼────────┼────┼───────┼───────┼────────┤ │ STANDARD │internal│hot │130 MiB│ 1 │...

@ravindk89 No, you can't. These metrics are aggregate statistics on a per-tier level. They don't retain any information on the buckets these objects are from.

@ryadav88 I shall try recreate this issue on a local DC/OS setup and share my findings. Thanks for the heads up.

@chshersh It would be awesome to have this feature in `hit`. I have a question regarding how listing of issues would work in the presence of forks. Usually the upstream...

@chshersh, I agree with the points you make above. I hadn't thought through the different combinations of forks vs owned repositories and maintainer vs contributor when I made the comment...

I followed the steps to reproduce with the only difference that I used another MinIO deployment as warm tier instead of Backblaze's B2. I **couldn't** recreate this issue. Could you...

@ir0nhide Thank you for your help with recreating this issue. I have sent a fix for this issue. I tested locally that the issue is resolved with this fix. It...

@RAlfoeldi Could you share the following information redacting anything that may be sensitive? 1. `mc ilm export ALIAS/bucket` - ILM policy configured on the MinIO bucket where you see this...

> mc ilm export requires a bucket. The UI only allows creating a new ilm. Yes, ilm-export command requires a bucket as an argument. I'd like to see the ILM...

@RAlfoeldi Would it be possible for you to enable some sort of audit logging at the AWS S3 bucket side? We could observe which application (incl. MinIO) is deleting objects...