Open Source Training Seminar FreePBX Paid Support

Ticket #1843 (closed Feature Requests: fixed)

Opened 1 year ago

Last modified 2 months ago

freepbx_log shouldn't be in asterisk DB

Reported by: andrew4455 Assigned to:
Priority: major Milestone: 2.5
Component: Core Version:
Keywords: freepbx_log database Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

freepbx_log table should really be stored in a separate DB.

Here are some reasons IMHO:

  1. Dumping asterisk DB is huge once the log file has accumulated some history
  2. Could impact performace when the log is very big.
  3. Would make backups simpler since you don't need to backup the log (at least for quick recovery purposes)
  4. Asterisk DB is used to store configuration information, not logging information. asteriskcdrdb is where call detail records go.

Perhaps create an asterisklog database and put freepbx_log in there instead.

Change History

03/15/07 02:00:18 changed by p_lindheimer

I would agree with this. We should provide an option to the freepbx_log and by default it should not go in the main database. And the option should also determine if it even gets logged to a db or not. Let's make this change, maybe even in 2.2.2.

06/20/07 06:33:10 changed by p_lindheimer

  • version changed from 2.2.1 to 2.3-branch.

06/26/07 14:14:21 changed by p_lindheimer

  • priority changed from minor to major.

07/19/07 12:50:34 changed by fameal

I think that freepbx_log should be logged into a file and not to the database. It would make reading it easier and a lighter database.

07/19/07 14:34:14 changed by p_lindheimer

we are looking at options, like pear's log class which would allow the choice of log to be configurable.

07/26/07 07:52:05 changed by p_lindheimer

  • version changed from 2.3-branch to SVN-HEAD.
  • milestone changed from 2.3 to 3.0.

moving to post 2.3 - we can consider back porting when addressed. This really fits in the realm of a much improved logging infrastructure which can be enabled and disabled.

11/27/07 23:58:34 changed by p_lindheimer

  • confirmation set to Confirmed.
  • version deleted.
  • milestone changed from 2.4 to 3.0.

06/28/08 13:28:59 changed by lazytt

$me++ - log's should be log files in /var/log. (unless the log in the DB us being used for self-healing)

07/01/08 14:43:25 changed by lazytt

  • type changed from Bugs to Feature Requests.

07/19/08 08:20:33 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to fixed.

r6059

Added parameters and changed defaults to amportal.conf default is bold:

  • AMPDISABLELOG (true/false): whether or not to log, default is disabled
  • AMPENABLEDEVELDEBUG (true/false): whether or not to include devel-debug messages in log if enabled
  • AMPSYSLOGLEVEL: Where to log
    • SQL or LOG_SQL
      • log to the MySQL Log table (previous behavior)
    • LOG_EMERG, LOG_ALERT, LOG_CRIT, LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO, LOG_DEBUG
      • log to the syslog system log, using the log level and configuration specified
Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads