Persistent volume claim monitoring/anomaly detection exclusion

[Babar_Qayyum]

Dear All,

To exclude a specific PVC from monitoring and disk space anomaly detection, what steps should be taken?

Regards,

Babar

[Peter_Youssef]

Hello @Babar_Qayyum 

As a suggestion you can refer to the attached resources if it can be configured from K8s side and reflected in Dynatrace:

• https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html/managing_and_al...
• https://kubernetes.io/docs/concepts/storage/persistent-volumes/
• https://kubernetes.io/docs/tasks/configure-pod-container/configure-persistent-volume-storage/#create...

If we used the anomaly detection API:

curl 'https:///e//api/v2/settings/objects' \
-X POST \
-H 'Accept: application/json; charset=utf-8' \
-H 'Content-Type: application/json; charset=utf-8' \
-H 'Authorization: Api-Token ACCESS_TOKEN' \
-d $'[{"schemaId":"builtin:anomaly-detection.kubernetes.pvc","schemaVersion":"1.2","scope":"environment","value":{"lowDiskSpaceCritical":{"enabled":true},"lowDiskSpaceCriticalPercentage":{"enabled":true,"configuration":{"threshold":3,"samplePeriodInMinutes":3,"observationPeriodInMinutes":5}}}}]'

The section that would be changed the scope instead of environment DevOps can specify specific PVCs and exclude the others.

Or

• Extract the Objects from the Environment API v2 and update the intended object via API and check if it's applied as expected or not.

Hopefully it adds value.
KR,

Peter.

[Babar_Qayyum]

Hello @Peter_Youssef 

Thank you for your feedback. We can implement changes on the namespaces individually rather than at the cluster or global level; however, this approach would be quite labor-intensive. Consequently, I am looking for a more straightforward method to exclude items, similar to how we exclude disks.

Regards,

Babar

[Peter_Youssef]

Hello @Babar_Qayyum 

Thanks for the updates, good to hear that.
Let's investigate the workaround 🚪😉😊.