forked from docs/doc-exports
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com> Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
14 lines
1.2 KiB
HTML
14 lines
1.2 KiB
HTML
<a name="cce_faq_00316"></a><a name="cce_faq_00316"></a>
|
|
|
|
<h1 class="topictitle1">Can CCE PVCs Detect Underlying Storage Faults?</h1>
|
|
<div id="body0000001214442702"><p id="cce_faq_00316__p101037381087">CCE PersistentVolumeClaims (PVCs) are implemented as they are in Kubernetes. A PVC is defined as a storage declaration and is decoupled from underlying storage. It is not responsible for detecting underlying storage details. Therefore, CCE PVCs cannot detect underlying storage faults.</p>
|
|
<p id="cce_faq_00316__p186311971488">Cloud Eye allows users to view cloud service metrics. These metrics are built-in based on cloud service attributes. After users enable a cloud service on the cloud platform, Cloud Eye automatically associates its built-in metrics. Users can track the cloud service status by monitoring these metrics.</p>
|
|
<p id="cce_faq_00316__p6631271086">It is recommended that users who have storage fault detection requirements use Cloud Eye to monitor underlying storage and send alarm notifications.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cce_faq_00037.html">Storage</a></div>
|
|
</div>
|
|
</div>
|
|
|