<h1 id="monitor">Monitor<a aria-hidden="true" class="anchor-heading icon-link" href="#monitor"></a></h1>
<h1 id="monitor-1">Monitor<a aria-hidden="true" class="anchor-heading icon-link" href="#monitor-1"></a></h1>
<h2 id="work-metrics">work metrics<a aria-hidden="true" class="anchor-heading icon-link" href="#work-metrics"></a></h2>
<ul>
<li>throughput:rps</li>
<li>success</li>
<li>error</li>
<li>performance: response time</li>
</ul>
<h2 id="resource-metrics">resource metrics<a aria-hidden="true" class="anchor-heading icon-link" href="#resource-metrics"></a></h2>
<ul>
<li>utilization: percentage time that the resource is busy</li>
<li>saturation: measure of the amount of requested work that resource cannot yet service, often queued</li>
<li>errors: internal error that cannot observed in the resource produces</li>
<li>availability: represents the percentage of time that the resource responded to requests. This metric is only well-defined for resources that can be actively and regularly checked for availability.</li>
</ul>
<h2 id="event-metrics">event metrics<a aria-hidden="true" class="anchor-heading icon-link" href="#event-metrics"></a></h2>
<ul>
<li>Changes: Internal code releases, builds, and build failures</li>
<li>Alerts: Internally generated alerts or third-party notifications</li>
<li>Scaling events: Adding or subtracting hosts</li>
</ul>