Yuchen Liang e374d6778e feat(storcon): store scrubber metadata scan result (#8480) ...

Part of #8128, followed by #8502.

## Problem

Currently we lack mechanism to alert unhealthy `scan_metadata` status if
we start running this scrubber command as part of a cronjob. With the
storage controller client introduced to storage scrubber in #8196, it is
viable to set up alert by storing health status in the storage
controller database.

We intentionally do not store the full output to the database as the
json blobs potentially makes the table really huge. Instead, only a
health status and a timestamp recording the last time metadata health
status is posted on a tenant shard.

Signed-off-by: Yuchen Liang <yuchen@neon.tech>

2024-07-30 14:32:00 +01:00

..

down.sql

feat(storcon): store scrubber metadata scan result (#8480)

2024-07-30 14:32:00 +01:00

up.sql

feat(storcon): store scrubber metadata scan result (#8480)

2024-07-30 14:32:00 +01:00