Centralized logging

In SCI, no logs were seen in the Centralized log/Alarm folder. But logs seen in the Centralized log\Standard or Interaction or Trace folders.

I did not see any errors in the Message server logs and the connection looks ok. Also, I looked in the database for the messages that gets populated in the Alarm folder (messages with priority = 5) and I found that no messages seen in the database.
SELECT * from dbo.G_LOG_MESSAGES where PRIORITY = ‘5’ order by TIMEWRITTEN desc

Message server log:
15:21:35.975 Trc 23010 Msg(id=2929801,from=344): t=1101, pr=2, o=275, key={f=3,i=275,l=10612,s=(null)}

SCS Log:
15:21:35.960 ### LOCAL MESSAGE#=10612, 'Active Alarm ‘Gim Etl Job Completed Unsuccessfully’ created for Application ‘sac_gim_etl_81’ ’
15:21:35.960 Alarm sac_gim_etl_81 GCTI-00-04115 Gim Etl Job Completed Unsuccessfully, alarm condition(144)
15:21:35.960 ### LOCAL MESSAGE#=4115, ‘Gim Etl Job Completed Unsuccessfully, alarm condition(144)’
Sent Email for the alarm condition.

Any other suggestions on how to troubleshoot further?

Thank you.

How did you configure network logging to the message server? Having network logging with high logging level is way to hell - using standard level only is a standard.

Yes, I configured network logging to the message server and in Standard mode. But there is one more message server, which need to be configured for network logging. Let me try and post the result.

Still no luck.

Try changing the verbose level on your SCS, Message Server, and Log DB Server temporarily to “trace” or “all”. Also make sure that you set standard, interaction, and trace to all write to both network and to a local file, and debug to the local file as well.

If it’s a high volume environment, only let it run for 5 - 10 minutes, then change it back and examine the logs.

Make sure that you have connections between SCS and Message Server, and Message Server and Log DAP. Also make sure that your Log DAP account settings are correct.

SCI/GA must have connection to DAP. plz chk.