To be fair, I haven’t done an exhaustive search of our old apps. But as near as I can tell, we’ve never had nearly enough data to get this error. Something on the order of 10-20MB, total, across all our apps. I need to write a comprehensive monitoring app, to be sure.
Yet we did get this error. I think it was around 21:01 UTC.
I cleared out a few hundred obsolete database table rows, and things seem to be back to normal, for now.
Just wondering, is this a glitch? Or did we accidentally create a data monster, without realizing it?
Much of these concerns could be fixed by a monitoring tool built in to Anvil. I have a gut feeling (no real information!) that they are indeed working on this and other things.
Always frustrating to track down account level issues like that.
could be the starting point for a monitoring program of my own. The logic is straightforward:
Use the post’s clues to download a complete index of all of my Apps. Most of these are proof-of-concept cases, including clones posted in this forum.
For each App, download it as a .yaml file. This does not contain any table data, but if the App uses tables, then it contains descriptors for all of the App’s tables.
For each App that has tables, connect to the app via Uplink, and survey the tables. Anvil has at least two metrics of import: # of rows, and # of bytes in Media columns. Total both for the App. If any app is a surprise database hog, then this should reveal it.
Calculate grand totals, and compare against the published Plan limits.