# Kubernetes.node.status.\* metrics not available for alerting

**URL:** <https://discuss.elastic.co/t/kubernetes-node-status-metrics-not-available-for-alerting/323901>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [January 25, 2023, 9:31am UTC](https://discuss.elastic.co/t/kubernetes-node-status-metrics-not-available-for-alerting/323901 "2023-01-25T09:31:37Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Maksym\_Postument](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maksym_postument/32/106661_2.png) [@Maksym\_Postument](https://discuss.elastic.co/u/Maksym_Postument)\
**Post date:** [January 25, 2023, 11:43am UTC](https://discuss.elastic.co/t/kubernetes-node-status-metrics-not-available-for-alerting/323901/3 "2023-01-25T11:43:52Z")

</div>

Thank you Tetiana. I looked at thread which you shared. It is look similar, but my field is not boolean type, but keyword. Which may have one of following values true, false or unknown.

I found this [thread](https://discuss.elastic.co/t/alerts-on-kubernetes-node-status-fields/290780) which looks exactly like my issue. Trying to solution from it

---

_[View the full topic](https://discuss.elastic.co/t/kubernetes-node-status-metrics-not-available-for-alerting/323901)._