# Kubernetes Node Condition NetworkUnavailable missing from metricbeat
**URL:** https://discuss.elastic.co/t/kubernetes-node-condition-networkunavailable-missing-from-metricbeat/326789
**Category:** Beats
**Tags:** metricbeat
**Created:** [March 1, 2023, 5:09pm UTC](https://discuss.elastic.co/t/kubernetes-node-condition-networkunavailable-missing-from-metricbeat/326789 "2023-03-01T17:09:55Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@kbujold\_wr](https://discuss.elastic.co/u/kbujold_wr)
#### Post date: [March 1, 2023, 5:09pm UTC](https://discuss.elastic.co/t/kubernetes-node-condition-networkunavailable-missing-from-metricbeat/326789/1 "2023-03-01T17:09:55Z")
The kubernetes Node Condition 'NetworkUnavailable' is missing from metricbeat. Can you please elaborate to why that is?
> **[Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/#condition)**
>
> Kubernetes runs your workload by placing containers into Pods to run on Nodes. A node may be a virtual or physical machine, depending on the cluster. Each node is managed by the control plane and contains the services necessary to run Pods.
> Typically...
> **[Kubernetes fields | Metricbeat Reference \[8.6\] | Elastic](https://www.elastic.co/guide/en/beats/metricbeat/current/exported-fields-kubernetes.html)**
Thank you,
Kris
---
### Author:  [@Tetiana\_Kravchenko](https://discuss.elastic.co/u/Tetiana_Kravchenko)
#### Post date: [March 2, 2023, 1:02pm UTC](https://discuss.elastic.co/t/kubernetes-node-condition-networkunavailable-missing-from-metricbeat/326789/2 "2023-03-02T13:02:39Z")
Hi @kbujold_wr
Might be that this condition was introduced later and it was not added. Could you please create an enhancement request in [beats](https://github.com/elastic/beats) repo for this?
Thank you!
---
### Author:  [@kbujold\_wr](https://discuss.elastic.co/u/kbujold_wr)
#### Post date: [March 2, 2023, 4:18pm UTC](https://discuss.elastic.co/t/kubernetes-node-condition-networkunavailable-missing-from-metricbeat/326789/3 "2023-03-02T16:18:17Z")
According to this [[Metricbeat] Add support for node conditions to state\_node metricset · Issue #18049 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/18049) Network Unavailable was already present. Its not clean from the above issue why it was not added.
---
### Author:  [@Tetiana\_Kravchenko](https://discuss.elastic.co/u/Tetiana_Kravchenko)
#### Post date: [March 2, 2023, 4:50pm UTC](https://discuss.elastic.co/t/kubernetes-node-condition-networkunavailable-missing-from-metricbeat/326789/4 "2023-03-02T16:50:51Z")
It was mentioned only in issue, but not in the related [PR](https://github.com/elastic/beats/pull/23905), since there is no relevant discussion around this status - I assume it is either a mistake, or might be related to the fact, that this condition was not reported in the older version of kube-state-metrics (related to this [comment](https://github.com/elastic/beats/issues/18049#issuecomment-768357908)).
thank you for the created issue!
---
### Author:  [@kbujold\_wr](https://discuss.elastic.co/u/kbujold_wr)
#### Post date: [March 2, 2023, 6:52pm UTC](https://discuss.elastic.co/t/kubernetes-node-condition-networkunavailable-missing-from-metricbeat/326789/5 "2023-03-02T18:52:05Z")
Mentioning the created issue here for traceability [Kubernetes Node Condition NetworkUnavailable missing from metricbeat · Issue #34724 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/34724#issuecomment-1452176217)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 30, 2023, 8:52pm UTC](https://discuss.elastic.co/t/kubernetes-node-condition-networkunavailable-missing-from-metricbeat/326789/6 "2023-03-30T20:52:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.