I found a query that maybe a problem:
When usage job start it founds a VOLUME.DELETE in usage_event table and after
that it look for a register in usage_volume table with that query:
SELECT usage_volume.id, usage_volume.zone_id, usage_volume.account_id,
usage_volume.domain_id, usage_volume.volum
Same here, exactly the same problem with volumes.
I've looked in github source for the SQL query that generates the
aggregated registries to try to understand but I couldn't find.
:/
Appreciate any help too.
Em ter., 26 de jul. de 2022 17:31, Matheus Fontes
escreveu:
> Hi,
> Is anyone having
