Topic
3 replies Latest Post - ‏2013-02-19T20:46:51Z by SystemAdmin
RaviM
RaviM
14 Posts
ACCEPTED ANSWER

Pinned topic mttrapd logging (more than 1 rolled file)

‏2013-01-24T22:14:55Z |
Is there a way to configure the mttrapd probe to log multiple log files and limit the size of each file. Currently it backs up just one and overwrites that when it backs up a new one. I thought there was a way to create multiple files. Can't seem to find any attributes in the props file.

Thanks
Ravi
Updated on 2013-02-19T20:46:51Z at 2013-02-19T20:46:51Z by SystemAdmin
  • GuyThorne
    GuyThorne
    50 Posts
    ACCEPTED ANSWER

    Re: mttrapd logging (more than 1 rolled file)

    ‏2013-01-25T09:09:18Z  in response to RaviM
    Hi Ravi,

    The probes do have the functionality you mention but only when running on Windows. Have a look for "LogFilePoolSize" and "LogFileUsePool" in the Probe/Gateway user guide if you are on Windows. http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc/omn_pdf_prgw_master_731.pdf

    If you have not already you can increase the MaxLogFileSize as the default is just 1MB.

    Cheers,

    Guy
  • SystemAdmin
    SystemAdmin
    1283 Posts
    ACCEPTED ANSWER

    Re: mttrapd logging (more than 1 rolled file)

    ‏2013-02-01T15:07:03Z  in response to RaviM
    Hi Ravi,

    Another option to look at is enabling Raw Capture, if you want to investigate on the past alarms.

    Regards,
    Raji.
    • SystemAdmin
      SystemAdmin
      1283 Posts
      ACCEPTED ANSWER

      Re: mttrapd logging (more than 1 rolled file)

      ‏2013-02-19T20:46:51Z  in response to SystemAdmin
      The generic time based log file rolling can be used for probes. It allows you to roll the log file at a predetermined time each day and, more importantly, specify the format of the 'old' log filename so that it is unique.

      https://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_OMNIbus.doc_7.3.1/omnibus/wip/install/reference/omn_con_unixsettingenvvariables.html

      $ export NDE_LOGFILE_ROTATION_FORMAT="yyyyMMddHHmmss"
      $ export NDE_LOGFILE_ROTATION_TIME=2044

      I then ran my simnet probe for a bit (so that it wrapped at 20:44) and now I have the following in my log dir:-

      $ ls -ltr log/sim*
      -rw-rw-r-- 1 alexg nco_src 375331 Feb 19 20:44 log/simnet.log_20130219204400
      -rw-rw-r-- 1 alexg nco_src 29619 Feb 19 20:44 log/simnet.log

      So you can see that a new logfile (simnet.log) was started at 20:44 with the old log rolled to a name based on the timestamp at that point.

      Also bear in mind the note on the page:-

      "
      If you set the NDE_LOGFILE_ROTATION_FORMAT environment variable, the NDE_LOGFILE_MAXSIZE environment is ignored.
      "

      So this can be used to give you daily log files that have unique names.

      Ta,

      -Alex