Application Log

 

SapphireIMS provides interfaces to monitor custom logs (generated by applications/ systems etc). This provides crucial insights to specific entries in the log files generated by these applications and helps you stay in control of these applications as well.

 

To configure application log monitoring follow the steps below:

 

 

Note: Before you add a new application log for monitoring, provide the credentials of the local system. A default profile for the local system is available as part of the system, this needs to be edited as appropriate. To perform this, click  ‘Settings’, from ‘Asset and Inventory’ section click ‘Profile Manager’ and edit the profile ‘Default local system profile’.

 

Once the file monitoring is configured as shown below, the file will be polled in the specified time interval, and the matching content will be stored in SapphireIMS.

application_log_monitoring.gif

Custom Log Monitoring

Sr. No

Field Name

Description

 

    1

Title

Title to identify the application log resource

 

    2

Description

Brief description of the resource

 

    3

Server IP/Host Name

 

Enter the host name/ IP address of the system where the log file is located

    4

Application Name

Select the application name that is to be monitored if it is displayed in the drop down list. If the application is previously configured, it will appear in the list. If not you need to enter the name.

     5

Operating System

Specify the OS of the target device (whether the log file resides in UNIX or Windows)

 

     6

Application Log Present in Remote Host

 

Profiles

Select this check box to enable the ‘Profiles’ drop down box

 

 

Select the profile that is required to connect to the target  system

Add New Profile: If the required profile does not exist, then click ‘Add New Profile’ to create a new profile

 

      7

File Path

For Windows servers, the folder containing the log files must be shared and the UNC path has to be given in file path (\\172.16.11.2\AppLogs)

 

      8

File Name

The actual log file name with the date format. For instance 'fzs-%Y-%m-%d.log'. The following list provides the format of the date codes used.

%a

Weekday as three-character string. Possible values are 'Sun', 'Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat'.This replacement character is most useful for DHCP log files.

%A

Full weekday name (Sunday, Monday....)

%b

Month as three-character string. (Jan, Feb., Mar....)

%B

Month (January, February...)

%d

Day of month with two digits (e.g. March, 1st becomes "01")

%j

Day of year as decimal number (001 - 366)

%m

Month with two digits (e.g. March becomes "03")

%U

Week of year as decimal number, with Sunday as first day of week (00 - 53)

%w

Weekday as decimal number (0 - 6, Sunday is 0)

%W

Week of year as decimal number, with Monday as first day of week (00 - 53)

%y

Year with two digits (e.g. 2002 becomes "02")

%Y

Year with 4 digits

 

 

       9

Backup File Name

Backup file name that needs to be read (similar to the file name)

      10

Search Pattern

The pattern that needs to be matched in the log file. Whenever this pattern is matched in the log file, the contents will be stored in the 'Log Archival' path

 

      11

Poll Interval

Specify the poll interval for periodically reading the log file . By default this is 5 minutes. The read is always incremental and will not be full.