Feature - send error logs to eramba core team

Every time the daily cron runs and randomly when a user logins (always the first login after fresh install) eramba sends to our servers some data that helps us:

  • validate your license
  • make sure you are not using outdated parameters (www crons)
  • log how long it took your daily cron to run (we used this to promptly detect failed crons or crons which are taking too long and warn the customer before hand)

this is a sample of the JSON we receive:

[{"appVersion":"e2.20.0","dbVersion":"e2.20.0","phpVersion":"7.3.23","integrityHash":"xxxxxxxx","lastCron":{"execution_time":"1992.2","created":"2020-10-16 00:00:01","completed":"2020-10-16 00:33:13","status":"success","url":null,"message":"Your CRON Job has been completed successfully","cron_type":"cli"}}](http://)

we are considering sending to eramba, as part of the hourly cron the “error.log” file which you all have in order to find out code issues, in particular sql issues that might not be prompted to you on the web interface but might be going on.

needless to say the error.log has no private data or anything that could resemble what you do on eramba , is just completed when an error on the code or sql happens. the hourly log will look for the new lines on the error log since the last hour, search for specific issues using regex, for example:

  • fatals
  • timeouts
  • sql issues

put only those lines on the json them and send it to us at the core team.

i never liked this type of feature on software but now that we run something used by many people i can not deny is actually useful to detect things under the radar. unlike closed apps, our code is open so anyone can validate that this data is the only data sent.

int ref: https://github.com/eramba/eramba_v2/issues/2800

we have looked at statistics on cron duration (we receive this information as part of the json above) and noticed the average daily cron takes 250-320 seconds … we will be contacting everyone whos daily cron runs for twice as long the average to know the reason.