There is potential for a ton of logs here. Salesforce queries, WordPress queries, hook usage, cron events, cron failures.
We need to think about how to do this in a sustainable way that works within a distributable plugin. So it needs to not fill up people's admin area with junk, but it does need to be (maybe optionally) available in there.
We need a way to avoid filling up the database to the point that it becomes a performance issue, or overwhelming to the point that it's impossible to find anything helpful.
There is potential for a ton of logs here. Salesforce queries, WordPress queries, hook usage, cron events, cron failures.
We need to think about how to do this in a sustainable way that works within a distributable plugin. So it needs to not fill up people's admin area with junk, but it does need to be (maybe optionally) available in there.
We need a way to avoid filling up the database to the point that it becomes a performance issue, or overwhelming to the point that it's impossible to find anything helpful.
We also need to make sure it gets rid of itself in a good way if the plugin is deactivated. No reason to leave that lying around.