RE: re: updated blog entry - Sitworld: Auditing TEMS for Improved Performance
John Alvord <jalvord-r/[email protected]>
| Newsgroups | gmane.comp.sysutils.tivoli.general |
|---|---|
| Message-ID | <OF9F9F4181.87118681-ON88257BBB.0051124B-88257BBB.00524854__20074.1885150366$1375455565$gmane$org@us.ibm.com> |
(NULL)- means "not a situation". That means it is coming from a TEP workspace view or SQL [usually SOAP requests]. It feels like a TEP Workspace - some Unix OS Summary view that has been set up to refresh fairly often. On the one hand. 53K bytes per minute is not very much - the trouble shows up when you go over 1meg a minute. The worst case I have seen so far was 92 megs/minute. So... you could probably ignore it. If you want to track it down, you can discover the SQL fairly easily by tracing the TEPS with "error (unit:ctsql in er)". Backtracking to the workspace view(s) is challenging. I did do it once at a customer site -in order to close a 400+ day PMR from some Turkish Bank... it took a few days with the trace and a migrate-export dump of their TEPS database. If there are relatively few users you could just check with them and see what they use... and what the refresh rate. Maybe there is a standard workspace for operators. When you find the workspace, you can just increase the refresh rate time - say from 30 seconds to 2 minutes - and get a linear decrease in impact. Regards, ______________________________________________ John Alvord Advisory Engineer IBM Tivoli Monitoring 6 Platform Customer Support Office: 1-720-396-2788 Mobile: none jalvord-r/[email protected] Cloud & Smarter Infrastructure IBM Support Portal Open a New Service Request Update your PMR via Email Escalate your PMR My Blog: Wonderful World of Situations Secure upload to ECUREP From: "Shickell, Matt X" <Matt.X.Shickell-2/khivBkHQhWk0Htik3J/[email protected]> To: "Discussion list for Tivoli product and Tivoli Ready products." <[email protected]>, Date: 08/02/2013 01:19 AM Subject: RE: [TME10] re: updated blog entry - Sitworld: Auditing TEMS for Improved Performance Sent by: [email protected] Hi John, Thanks for this ? enable us to get rid of a situation that was no longer required that was second in the Situation Summery Report. Any idea what this is that always appears at the top: Situation Summary Report Situation Table Count Rows ResultBytes Result/Min Fraction Cumulative% MinResults MaxResults MaxNode (NULL)-*.UNIXOS *.UNIXOS 24935 24935 20346960 53626 52.98% 52.98% 816 816 xxxxxxxx:KUX Regards Matt From: [email protected] [ mailto:[email protected]] On Behalf Of John Alvord Sent: 29 July 2013 15:35 To: Discussion list for Tivoli product and Tivoli Ready products. ([email protected]) Subject: [TME10] re: updated blog entry - Sitworld: Auditing TEMS for Improved Performance New TEMS Audit version 1.05 that measures tracing impact and counts remote SQL failures. Sitworld: Auditing TEMS for Improved Performance https://www.ibm.com/developerworks/community/blogs/jalvord/entry/sitworld_auditing_tems_for_improved_performance73?lang=en Regards, ______________________________________________ John Alvord Advisory Engineer IBM Tivoli Monitoring 6 Platform Customer Support Office: 1-720-396-2788 Mobile: none jalvord-r/[email protected] Cloud & Smarter Infrastructure IBM Support Portal Open a New Service Request Update your PMR via Email Escalate your PMR My Blog: Wonderful World of Situations Secure upload to ECUREP _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected] _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected]