Skip to main content
Announcements
Global Transformation Awards! Applications are now open. Submit Entry
cancel
Showing results for 
Search instead for 
Did you mean: 
korsikov
Partner - Specialist III
Partner - Specialist III

Monitoring Apps contain only WARN and ERROR but in log had INFO and DEBUG

my operation monitor contains only WARN and ERROR but in log had INFO and DEBUG

how I can load all value on application?

I found in load script

//List of all log files to load -- and which ones to load fully (logRead = 1) or Errors and Warnings only (logRead = 0)

In addition to this line, this parameter is not present anywhere else. How do I enable it?

4 Replies
korsikov
Partner - Specialist III
Partner - Specialist III
Author

i'm add to

SUB serviceLog

  justErrorsWarnings:

  LOAD errorWarn INLINE [

    errorWarn

    ERROR

    WARN

    WARNING

    FAIL

    FATAL

   INFO

    DEBUG

  ];

and now I have in the application INFO message

Tyler_Waterfall
Employee
Employee

You can update the load script to include INFO and DEBUG, but it defeats the purpose of the Errors and Warnings table in Log Details. Adding INFO and DEBUG will mean that INFO messages will be included in the "Errors and Warnings" table.

You can already find that information in the Log Details table.

korsikov
Partner - Specialist III
Partner - Specialist III
Author

You may suggest how to add events "info" and "debug" to the application loading

Tyler_Waterfall
Employee
Employee

INFO and DEBUG log entries are already being loaded in the app but do not include a separate field to say whether it is INFO or DEBUG.

In Sense server logs, the Service log for each service (Engine, Repository, etc.) contains a copy of all error and warning entries for each service. This is the log with the "Severity" column of ERROR, WARN, etc.

However, since these log entries are already present in the AuditActivity and AuditSecurity logs (and are read into the Operations Monitor app), there is no need to include any INFO or DEBUG entries which might also exist in the service logs.