# How to delete whole tenant from loki **URL:** \ **Category:** Grafana Loki\ **Created:** [February 5, 2026, 4:58pm UTC](https://community.grafana.com/t/how-to-delete-whole-tenant-from-loki/161543 "2026-02-05T16:58:33Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![wohnout](https://avatars.discourse-cdn.com/v4/letter/w/e19b73/32.png) [@wohnout](https://community.grafana.com/u/wohnout)\ **Post date:** [February 5, 2026, 4:58pm UTC](https://community.grafana.com/t/how-to-delete-whole-tenant-from-loki/161543/1 "2026-02-05T16:58:33Z")
Hi, I have multitenance set. I have been testing data scraping for one of the tenants and created a lot of unwanted data which are preventing loading actual data. These data are for 90 days and I need to properly place them to the series. I have loki 3.6, using tsdb and azure storage. I have tried deleting index data of the tenant and whole tenant folder from blob storage and from tsdb\_shipper\_cache, deleted postions on promtail agent and still it doesn’t want to load data back to tenant. When I have redirected promtail to different tenant it collected data properly and displayed them in grafana. Is there any posibility how to totally delete tenant from loki totally? ---
**Author:** ![tonyswumac](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/tonyswumac/32/22401_2.png) [@tonyswumac](https://community.grafana.com/u/tonyswumac)\ **Post date:** [February 6, 2026, 3:40am UTC](https://community.grafana.com/t/how-to-delete-whole-tenant-from-loki/161543/2 "2026-02-06T03:40:41Z")
I don’t think your issue has anything to do with whatever data you deleted for the tenant. If you are able to send data to Loki, then it’s probably working fine. 1. What errors do you see on Loki? 2. What errors do you see on your log agent (sounds like you are using promtail?) ---
**Author:** ![wohnout](https://avatars.discourse-cdn.com/v4/letter/w/e19b73/32.png) [@wohnout](https://community.grafana.com/u/wohnout)\ **Post date:** [February 6, 2026, 7:00am UTC](https://community.grafana.com/t/how-to-delete-whole-tenant-from-loki/161543/3 "2026-02-06T07:00:28Z")
1. I am getting 404 from azure blob doesn’t exist like this: 2. There are no errors on promtail actually. Just empty ring after loki restart I have compactor turned on and this system is under big load as it is digesting quite a lot of data. ---
**Author:** ![wohnout](https://avatars.discourse-cdn.com/v4/letter/w/e19b73/32.png) [@wohnout](https://community.grafana.com/u/wohnout)\ **Post date:** [February 6, 2026, 7:04am UTC](https://community.grafana.com/t/how-to-delete-whole-tenant-from-loki/161543/4 "2026-02-06T07:04:20Z")
and important to say newly digested data are stored and retrieved properly even in the original tenant. ---
**Author:** ![tonyswumac](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/tonyswumac/32/22401_2.png) [@tonyswumac](https://community.grafana.com/u/tonyswumac)\ **Post date:** [February 7, 2026, 12:19am UTC](https://community.grafana.com/t/how-to-delete-whole-tenant-from-loki/161543/5 "2026-02-07T00:19:39Z")
Ok, now I am confused on what exactly you are asking for. From your posts, I understand that: 1. You’ve removed old chunk files for this one tenant. 2. New logs are coming in correctly. 3. When querying logs against the tenant you get errors where certain chunks cannot be located. This is because you removed some chunk files, so this is expected. So if new logs are coming in and old logs are gone, sounds that’s what you were looking for. What exactly are you looking to solve? ---
**Author:** ![wohnout](https://avatars.discourse-cdn.com/v4/letter/w/e19b73/32.png) [@wohnout](https://community.grafana.com/u/wohnout)\ **Post date:** [February 11, 2026, 2:05pm UTC](https://community.grafana.com/t/how-to-delete-whole-tenant-from-loki/161543/6 "2026-02-11T14:05:05Z")
I’ve removed whole tenant folder with all chunks, I’ve deleted all index files for this tenant. Restarted loki. Stopped promtail on server with logs, remove positions for log files I want to digest again. Started promtail again. expected result: Logs are digested again and I can go through them. Actual result: New chunks with old logs are generated but index files references old chunks (nonexisting) again.