FSM log contains a 'severity' field. Normally warning, critical, etc.
For elogs on IS and PE it returns a numeric value.
How are these interpreted - is there a mapping from a error tuple to a numeric value based on severity (info, warning, critical, severe) ? Can these be mapped to verbage so our TEC monitor can pick up these as critical from a consistent value in the log file?
Fri Jun 19 15:23:24 2009;;test1.x.fsm.net;;WARNING;;FileNetBasis;;not_ok;;
Fri Jun 19 15:28:01 2009;;test2.x.fsm.net;;2;;FN_IM_Logfile;;Error;;
Edited by: sbass_admin on Jul 17, 2009 1:17 PM
This topic has been locked.
3 replies Latest Post - 2009-06-30T21:47:05Z by lboghos2
Pinned topic Interpreting FSM log severity data
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2009-06-30T21:47:05Z at 2009-06-30T21:47:05Z by lboghos2
SystemAdmin 110000D4XK53 PostsACCEPTED ANSWER
Re: Interpreting FSM log severity data2009-06-19T21:34:07Z in response to lboghos2For the elog, FSM does map the error tuple to a number that represents a severity (0=HARMLESS, 1=WARNING, 2=CRITICAL, 3=FATAL).
Using IS as an example, the error tuple severity is determined by looking in the file, fnis_evt.map (not by FileNet severity specified in the elog itself. This was done to keep it configurable). Without getting into too much detail, there is also a mechanism to determine exceptions for certain error tuples since the same error tuple can be used for several situations (the error message will be different though).
haase 1000003KWN4 PostsACCEPTED ANSWER
Re: Interpreting FSM log severity data2009-06-21T09:51:17Z in response to lboghos2have a look in the FSM server cala/misc directory, there you can find a file like report*.tpl - if one of the fields contains status, try to replace the string "status" with "severity" and recycle the FSM server cala service/daemon and review the new created logfile message. if this does not help post the content of the .tpl file(s)
lboghos2 270000FH2D11 PostsACCEPTED ANSWER
Re: Interpreting FSM log severity data2009-06-30T21:47:05Z in response to haasehere is the report.tpl file:
I may just need to have the TEC monitor look for the value '2' as well as 'critical' in the severity field.