forked from docs/doc-exports
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Youyuan, Pan <panyouyuan@huawei.com> Co-committed-by: Youyuan, Pan <panyouyuan@huawei.com>
15 lines
1.2 KiB
HTML
15 lines
1.2 KiB
HTML
<a name="ces_faq_0008"></a><a name="ces_faq_0008"></a>
|
|
|
|
<h1 class="topictitle1">Why Are the Network Traffic Metric Values in Cloud Eye Different from Those Detected in ECS?</h1>
|
|
<div id="body8662426"><p id="ces_faq_0008__en-us_topic_0021062283_p62387627161931">Because the sampling period in Cloud Eye is different from that of the metric monitoring tool in ECS.</p>
|
|
<p id="ces_faq_0008__en-us_topic_0021062283_p23431297162820">Cloud Eye collects ECS and EVS disk data every 4 minutes (5 minutes for KVM ECSs). In contrast, the metric monitoring tool in ECS collects data every second.</p>
|
|
<p id="ces_faq_0008__en-us_topic_0021062283_p53344722163133">The larger the sampling period, the greater the data distortion in the short term. Cloud Eye is more suitable for long-term monitoring for websites and applications running on ECSs.</p>
|
|
<p id="ces_faq_0008__en-us_topic_0021062283_p2928922161916">Furthermore, to improve reliability, you can configure alarm thresholds to enable Cloud Eye to generate alarms where there are resource exceptions or insufficiencies.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="ces_faq_0062.html">Monitored Data Exceptions</a></div>
|
|
</div>
|
|
</div>
|
|
|