3 Replies Latest reply on Jan 7, 2015 7:20 AM by levi

    Is there a way to increase the size of the Event History Log?

    asteriskuser New Member

      Hello All,

       

      Currently, it appears that this log only holds about one page worth of entries.  In our case, that amounts to only about three hours worth of  entries and old entries are falling off the end too quickly to be useful.  I get the same result if I view this log via the GUI or CLI (#show event-history).

       

      Your help is appreciated!

        • Re: Is there a way to increase the size of the Event History Log?
          levi Employee

          Asteriskuser:

           

          Thank you for this question.  To increase the size of the event-history, I recommend logging the desired output to a syslog server. (Note: in AOS 11.5.0 the command event-history size <kilobytes> was added.  The valid range is from 6-256 kilobytes.) The details of how to configure the syslog server are described in the Configuring Syslog Logging in AOS document, but I have included the relevant information below:

           

          Configuring via the Web Interface

           

          Configuring logging via the Web Interface is supported in AOS firmware revisions 12 and higher. If your AOS device does not support AOS firmware revision 12, you should use the section titled “Configuring via the Command Line Interface.” For more information about accessing the web interface, consult the guide Accessing the Web Interface in AOS.


          Enabling Logging:

          1)      Click Logging under Utilities in the left menu.

          2)      Check the Event History check box.

          Enabling Syslog:

          3)      Click the Syslog Forwarding tab.

          4)      Check the Syslog Forwarding checkbox.

          Configuring Syslog Options:

          5)      Choose a Syslog Forwarding Priority Level. ‘Info (0)’ is the most verbose and ‘fatal (5)’ is the least verbose. For general information about interface state changes and firewall messages, choose ‘Notice (3)’.

          6)      Enter the Syslog Receiver IP Address. This is the IP Address of the computer hosting your Syslog server software.

          7)      Choose a Logging Facility between ‘Local 0’ and ‘Local 9’. The logging facility level is an arbitrary value that can be used in the Syslog Server software for filtering.

          8)      Click Apply.

          Saving the Configuration:

          9)      Click the Save button in the upper-right corner. Not clicking the Save button will cause the router to loose the changes you have made upon the next reboot.

          Note: Your AOS device will now send syslog messages to your syslog server.

           

          Configuring via the Command Line Interface

           

          Syslog logging can be configured via the Command Line Interface in all versions of AOS. For more information about access the Command Line Interface, consult the guide Accessing the Command Line Interface in AOS.

           

          Accessing Global Configuration Mode:

          1)      Type enable to enter Privileged Exec mode. You may be prompted for a password. If you do not know this password, consult the guide Password Recovery in AOS.

          2)      Type configure terminal to access Global Configuration Mode.

          Enabling Event Logging:

          3)      Type event-history on to enable event history logging.

          Enabling Syslog:

          4)      Type logging forwarding on to enable syslog logging.

          Configuring Syslog Options:

          5)      Type logging facility local0 to set the logging facility. The logging facility option is used by the Syslog server for filtering.

          6)      Type logging forwarding receiver-ip  <ip-address> to set the IP Address to which Syslog entries should be forwarded.

          (Example: logging forwarding receiver-ip 192.168.1.1)

          7)      Type logging forwarding priority-level <priority-level> to set the priority level. The priority level options are ‘error’, ‘fatal’, ‘warning’, ‘notice’ and  ‘info’ in ascending order of verbosity (‘error’ being the least verbose and ‘info’ being the most verbose).

          (Example: logging forwarding priority-level notice)

          Note: Your AOS device will now begin forwarding syslog entries to your Syslog Server.

           

          I hope that makes sense, but please, do not hesitate to reply to this chain with any questions or additional information and I will be happy to help in any way I can.

           

          Levi