Monitoring for SysEdge and Specturm

Document ID : KB000093499
Last Modified Date : 23/05/2018
Show Technical Document Details
We want to monitor Spectrum Database operations ,error logs checking the feasibility with Sysegde09:46:59 Kindly let us know which all parameters needs to be monitored from Spectrum and SRM databases09:47:41 Also possibly can you please let us know the error logs names which needs to be monitored
On The SysEdge side, we monitor: Windows- C:\Documents and Settings\All Users\Application Data\CA\SystemEDGE\port161\sysedge.log Linux/Sol- /opt/CA/SystemEDGE/config/port161/sysedge.log To Add SysEdge Debug: 1. Stop Agent 2. Navigate to /SystemEDGE/config/port# folder 3. Edit and make the following change: sysedge_loglevel debug3 sysedge_logfile sysedgedbg.log 100000 5 3. Start Agent On the Spectrum side, we can enable some debugging on the Event side: Debugging against event 0x01169b18 to see what event processing is taking place. To enable the event debug: a. As the Spectrum Owner, open a command line or 'bash -login' shell on the SpectroSERVER recieving these traps. b. cd to the $SPECROOT/vnmsh directory. c. open a CLI connection by running ./connect d. enable the debug by running ./update action=0x10274 mh= index=0,attr=0,type=15,val=0x01169b18 where = the Landscape Handle of the SpectroSERVER in hex. The output will be written to the $SPECROOT/SS/VNM.OUT To enable the Alert Manager debug: a. In a OneClick Console, locate the VNM model. b. In the Component Details pane - Information Tab, scroll to the bott and expand the "Dynamic Debugging" subview. c. Turn on the Alert Manager debug. The output will be written to the $SPECROOT/SS/VNM.OUT. Let the event debug run until you see a few instances of the traps processed. Send me a copy of the VNM.OUT to review. Don't forget to go back and disable the debugs. To disable the event debug, run the following from the CLI: ./update action=0x10275 mh= index=0,attr=0,type=15,val=0x01169b18 While the SSDB is not accessible using MYSQL, you can access the Reporting and Events database. /mysql/bin/mysql -uroot -proot reporting for reporting and /mysql/bin/mysql -uroot -proot ddmdb for Events. From there you can run calls to the different tables to see the information you are looking for.