Auto report errors

I know a lot of applications out there do error reporting to the "mothership" to allow app developers to more rapidly troubleshoot and fix issues. Is this something the team has considered - with an option of course to opt in or opt out?

For example - right now I have this error. If it was auto added to a database, improved workflow for improving una, instead of individual reports. Focus on easy wins affecting the largest number of servers first?

PHP Warning: Undefined array key "txt_sample_comment_single" in /home/.sites/site11/wwwroot/web/template/scripts/BxBaseCmtsServices.php on line 416

  • View
    426
  • More
Replies (4)

    • Hello @gkuhnert !

      All similar errors / warning messages are placed into the server log files. The making of the special pages which will provide the same info like any hosting panel but often without full access, looks like isn't such necessary.

      • G

        I think you missed my point. I am talking about regular repetative errors caused by bugs in the UNA source code - instead of this just going to a local log file, why not add some optional logic that will send the details to the Una "mothership". Allow your team to find common patterns, to find and fix those items that are regularly cropping up. I know I've found more than a handful that need to be fixed with patches...

        • Oh, sorry. But I guess we have the fine "mothership" here and our developer are processing similar messages ASAP as they can.

          • G

            I think something is lost in translation. Let me try one more time.

            Option 1: Current situation: Users are required to open the emails that come from cron, and/or open log files on their server. Decide which ones are important to them, and decide to logon to the Una forum, create a post, wait, and hope its dealt with.

            Option 2: Proposed solution: Log data from PHP or SQL errors get auto sent to Unacms developers, and stored in a database systematically. As a developer, you would be able to see patterns across multiple customers/sites that indicate things that can be fixed, even before and end user realises there is a problem.

            Doesnt that sound nice?

            Login or Join to comment.