Abstract
The third level of triage is to consider the full perspective of APM by exploiting historical metrics from other sources; this is called triage with trends. Trending is the consideration of data over some period of time, usually via statistical techniques; it’s something that IT is trying to do for all types of availability and performance problems, not simply those that have the benefit of APM visibility. The challenge is to bring together all of these disparate sources of data into something on which correlation techniques may be applied.
Opportunity is missed by most people because it is dressed in overalls and looks like work.—Thomas Alva Edison
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
Wikipedia, “root cause,” http://en.wikipedia.org/wiki/Root_cause
Wikipedia, “key performance indicator,” http://en.wikipedia.org/wiki/Key_performance_indicator
Wikipedia, “root cause analysis,” http://en.wikipedia.org/wiki/Root_cause_analysis
Wikipedia, “correlation,” http://en.wikipedia.org/wiki/Correlation
Wikipedia, “web log analysis software,” http://en.wikipedia.org/wiki/Web_log_analysis_software
Wikipedia, “SMF_120.9,” http://en.wikipedia.org/wiki/SMF_120.9
Wikipedia, “ping,” http://en.wikipedia.org/wiki/Ping
Wikipedia, “stand-alone,” http://en.wikipedia.org/wiki/Stand-alone
Wikipedia, “ent erprise app lication integration,” http://en.wikipedia.org/wiki/Enterprise_application_integration#Integration_patterns
“Future CMDB” by Hank Marquis www.itsmsolutions.com/newsletters/DITYvol6iss29.htm
Wikipedia, “CMDB,” http://en.wikipedia.org/wiki/CMDB
Wikipedia, “expert system,” http://en.wikipedia.org/wiki/Expert_system
The Organizational Implications of Chargeback Systems — March 2010 — http://wikibon.org/wiki/v/The_Organizational_Implications_of_Chargeback_Systems
What is.com, “IT chargeback system,” http://whatis.techtarget.com/definition/it-chargeback-system.html
Knowledgeleader.com, “Service Level Agreement Sample Template,” www.knowledgeleader.com/KnowledgeLeader/content.nsf/Web+Content/SAMServiceLevelAgreementSampleTemplate!OpenDocument
TechNet, “Establishing a Service Level Agreement, http://technet.microsoft.com/en-us/library/bb124886%28EXCHG.65%29.aspx
“Information Technology Service Level Agreement Template” www.purdue.edu/bscompt/Projects/SLAs/SLADraftTemplate_111901.doc
Sun Blueprints, “Service Level Agreement in the Data Center,” www.sun.com/blueprints/0402/sla.pdf
Ideabyte, “SLA Benchmark Metrics,” http://www.scribd.com/doc/8532482/Ideabyte-SLA-Benchmark-Metrics
Table adapted from “Capacity Planning for Web Performance”, p 255, Menasce and Almeida, Prentice Hall 1998, ISBN0-13-693822-1
Wikipedia, “state,” http://en.wikipedia.org/wiki/State_(computer_science)
Wikipedia, “framework,” http://en.wikipedia.org/wiki/Framework_(computer_science)
Rights and permissions
Copyright information
© 2010 CA Technologies
About this chapter
Cite this chapter
Sydor, M.J. (2010). Triage with Trends. In: APM Best Practices. Apress. https://doi.org/10.1007/978-1-4302-3142-4_16
Download citation
DOI: https://doi.org/10.1007/978-1-4302-3142-4_16
Publisher Name: Apress
Print ISBN: 978-1-4302-3141-7
Online ISBN: 978-1-4302-3142-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)