forked from docs/doc-exports
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: gtema <artem.goncharov@gmail.com> Co-committed-by: gtema <artem.goncharov@gmail.com>
13 lines
1.3 KiB
HTML
13 lines
1.3 KiB
HTML
<a name="ces_faq_0045"></a><a name="ces_faq_0045"></a>
|
|
|
|
<h1 class="topictitle1">Why Is the Monitoring Data Not Displayed on the Cloud Eye Console?</h1>
|
|
<div id="body1564038663378"><p id="ces_faq_0045__p8060118">Possible causes are as follows:</p>
|
|
<ul id="ces_faq_0045__ul85038714123"><li id="ces_faq_0045__li9852442174415">The service is not interconnected with Cloud Eye. To check whether a service has been interconnected with Cloud Eye, see <a href="en-us_topic_0202622212.html">Services Interconnected with Cloud Eye</a>.</li><li id="ces_faq_0045__li212412843110">The service has been interconnected with Cloud Eye. However, the collection and monitoring frequency for each service varies. The data may have just not been collected yet.</li><li id="ces_faq_0045__li1250317718128">The ECS or BMS has been stopped for more than 1 hour.</li><li id="ces_faq_0045__li85541221151218">The EVS disk has not been attached to an ECS or BMS.</li><li id="ces_faq_0045__li062464519127">No backend server is bound to the elastic load balancer or all of the backend servers are shut down.</li><li id="ces_faq_0045__li42031754916">It has been less than 10 minutes since the resource was created.</li></ul>
|
|
</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>
|
|
|