Postgres disk full, how configure sentry retention?

Hi all, i install sentry helm chart in k8s cluster, sentry version 21.3.0, chart version 10.1.0. Now i try configure retention option
https://github.com/sentry-kubernetes/charts/blob/05698720bc8a5eedcbaa847f766ac6a669360ec5/sentry/values.yaml#L145

As I understand, sentry-cleaner works well, examplelog:

12:10:43 [WARNING] sentry.utils.geo: settings.GEOIP_PATH_MMDB not configured.
12:10:47 [INFO] sentry.plugins.github: apps-not-configured
Removing expired values for LostPasswordHash
Removing expired values for OrganizationMember
Removing expired values for ApiGrant
Removing expired values for ApiToken
Removing expired files associated with ExportedData
Removing old NodeStore values
Removing UserReport for days=7 project=*
Removing GroupEmailThread for days=7 project=*
Removing GroupRuleStatus for days=7 project=*
Removing EventAttachment for days=7 project=*
12:25:58 [WARNING] sentry.utils.geo: settings.GEOIP_PATH_MMDB not configured.
12:26:04 [INFO] sentry.plugins.github: apps-not-configured
Removing Group for days=7 project=*
12:26:06 [INFO] sentry.deletions.async: object.delete.executed (object_id=72 transaction_id='eeae4fdf4abf4861bd3a0fd08f5453c8' app_label='sentry' model='Group')
12:26:06 [INFO] sentry.deletions.async: object.delete.executed (object_id=21 transaction_id='eeae4fdf4abf4861bd3a0fd08f5453c8' app_label='sentry' model='Group')
12:26:06 [INFO] sentry.deletions.async: object.delete.executed (object_id=181 transaction_id='eeae4fdf4abf4861bd3a0fd08f5453c8' app_label='sentry' model='Group')
12:26:07 [INFO] sentry.deletions.async: object.delete.executed (object_id=27 transaction_id='eeae4fdf4abf4861bd3a0fd08f5453c8' app_label='sentry' model='Group')
12:26:07 [INFO] sentry.deletions.async: object.delete.executed (object_id=97 transaction_id='eeae4fdf4abf4861bd3a0fd08f5453c8' app_label='sentry' model='Group')
12:26:07 [INFO] sentry.deletions.async: object.delete.executed (object_id=68 transaction_id='eeae4fdf4abf4861bd3a0fd08f5453c8' app_label='sentry' model='Group')
12:26:07 [INFO] sentry.deletions.async: object.delete.executed (object_id=89 transaction_id='eeae4fdf4abf4861bd3a0fd08f5453c8' app_label='sentry' model='Group')
12:26:07 [INFO] sentry.deletions.async: object.delete.executed (object_id=31 transaction_id='eeae4fdf4abf4861bd3a0fd08f5453c8' app_label='sentry' model='Group')
12:26:07 [INFO] sentry.deletions.async: object.delete.executed (object_id=15 transaction_id='eeae4fdf4abf4861bd3a0fd08f5453c8' app_label='sentry' model='Group')
 
Cleaning up unused FileBlob references

                                                                               

File Blobs: N/A% |                                             | ETA:  --:--:--
                                                                               

File Blobs: N/A% |                                             | ETA:  --:--:--
                                                                               

File Blobs:  10% |#####                                          | ETA: 0:00:01
                                                                               

File Blobs: 100% |##############################################| Time: 0:00:00

But postgres database size has not decreased. I set up the cleaning option for 7 days, but the database still contains events older than 7 days. I try run postgres vacuum cleaner - nothing. My question is, how properly configure sentry retentions?

can you figure out which table is taking up most disk?

table name is “nodestore_node”

Could you tell me what the oldest timestamp column value in that table is? If it’s older than 90d we may have a bug. But other than that it should be safe to truncate that table to 7 days, it just means you won’t be able to view events older than that properly. I don’t think we support any way of configuring the event retention to 7 days with just setting one option.

Thanks for the help, it seems that the retention works, I just had to wait a while. Sorry, my mistake.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.