📄 lib0127.html
字号:
<html>
<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<head>
<title>Application-Monitoring Guidelines</title>
<link rel="STYLESHEET" type="text/css" href="images/xpolecat.css">
<link rel="STYLESHEET" type="text/css" href="images/ie.content.css">
</head>
<body>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr><td><div STYLE="MARGIN-LEFT: 0.15in;"><a href="toc.html"><img src="images/teamlib.gif" width="62" height="15" border="0" align="absmiddle" alt="Team LiB"></a></div></td>
<td align="right"><div STYLE="MARGIN-LEFT: 0.15in;">
<a href="LiB0126.html"><img src="images/previous.gif" width="62" height="15" border="0" align="absmiddle" alt="Previous Section"></a>
<a href="LiB0128.html"><img src="images/next.gif" width="41" height="15" border="0" align="absmiddle" alt="Next Section"></a>
</div></td></tr></table>
<br>
<div class="chapter">
<a name="ch20"></a>
<div class="section">
<h2 class="first-section-title"><a name="632"></a><a name="ch20lev1sec1"></a>Application-Monitoring Guidelines</h2><a name="633"></a><a name="IDX-264"></a>
<p class="para">Many organizations consider application monitoring as a simple matter of purchasing the right software—BMC Patrol<span class="unicode">™</span> or EcoTools<span class="unicode">™</span>, for example. Usually, however these tools are not used effectively. And even when used to their potential, they monitor server and database health much better than they do custom applications.</p>
<p class="para">Monitoring software can determine if your application is available and measure the performance of common tasks but not much more. No product currently on the market can tell you <i class="emphasis">why</i> your application isn't available or find bugs that prevent users from getting what they want. Although purchasing a monitoring tool may be the first step in effective application monitoring, the task certainly doesn't end there.</p>
<p class="para">The objectives of monitoring applications are to detect and notify application administrators of ongoing issues and problems. You can address these objectives in several ways without using monitoring software. Here are some guidelines for using your application's functionality to its best advantage.</p>
<p class="para">
<b class="bold">Look for every opportunity to improve the quality and completeness of</b> <b class="bold">your regression test.</b> The first place to discover application issues and problems is in the application regression test. In earlier chapters, I recommended constructing test cases along with the application. Now you need to combine these test cases into a regression test. Bugs and errors caught at this stage are often found and fixed without incident. The more comprehensive your regression test is, the greater your chances of catching bugs before your application is released.</p>
<p class="para">
<b class="bold">Improve the quality and completeness of application error reports.</b> The best sources of information you have about application issues and problems after code has deployed are the error reports your application generates (reports of runtime errors). Application runtime errors are usually either software bugs or the result of environmental issues (e.g., the database is unavailable). With environmental issues, the earlier you act on the error report, the fewer users are affected.</p>
<p class="para">Using the information in the application error report, you can solve most bugs resulting in log entries or reports. I still recommend writing test cases that replicate bugs and including them in your regression test later. But any time you can save identifying the problem will in turn save time for your support staff.</p>
<a name="634"></a><a name="IDX-265"></a>
<p class="para">
<b class="bold">Broadcast application error messages to provide opportunities for quicker</b> <b class="bold">responses.</b> Often an environmental issue shows up as a system error report and can be corrected before too many users are affected. I have found that most developers look at logs only when an end user has reported a problem. Therefore, I usually broadcast error reports to the development team over some medium (e.g., e-mail) to increase the probability that someone will fix the errors before users notice.</p>
<p class="para">Some developers don't like receiving broadcasted application error reports because the volume of broadcast reports can be substantial in the beginning. Usually, however, the volume of error reports decreases over time as application bugs are fixed.</p>
<p class="para">
<b class="bold">Make the first sentence or subject of an error report descriptive and meaningful.</b> Because applications commonly generate many reports of the same error, you can save the support staff time by providing a reasonable description of the error in the subject line of an e-mail or in the first sentence of the message. This is especially important in companies in which the support staff does not develop applications.</p>
<p class="para">System error reports tend to be more comprehensive than user bug reports. In my experience, users don't report all the errors they experience. And often the information a user provides is less than complete.</p>
<p class="last-para">Nonetheless, user bug reports can be valuable sources of information. Often users can help you replicate the bug. Because the goal of using test cases and system error reports is to reduce the number of bugs reported by end users, the quantity of bugs reported is an indicator of the quality of your test cases and error reports.</p>
</div>
</div><br>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr><td><div STYLE="MARGIN-LEFT: 0.15in;"><a href="toc.html"><img src="images/teamlib.gif" width="62" height="15" border="0" align="absmiddle" alt="Team LiB"></a></div></td>
<td align="right"><div STYLE="MARGIN-LEFT: 0.15in;">
<a href="LiB0126.html"><img src="images/previous.gif" width="62" height="15" border="0" align="absmiddle" alt="Previous Section"></a>
<a href="LiB0128.html"><img src="images/next.gif" width="41" height="15" border="0" align="absmiddle" alt="Next Section"></a>
</div></td></tr></table>
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -