# Using kube-state-metrics (custom resource state metrics) breaks metricbeat
**URL:** https://discuss.elastic.co/t/using-kube-state-metrics-custom-resource-state-metrics-breaks-metricbeat/341249
**Category:** Beats
**Tags:** metricbeat
**Created:** [August 21, 2023, 1:32pm UTC](https://discuss.elastic.co/t/using-kube-state-metrics-custom-resource-state-metrics-breaks-metricbeat/341249 "2023-08-21T13:32:03Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@MKruger777](https://discuss.elastic.co/u/MKruger777)
#### Post date: [August 21, 2023, 1:32pm UTC](https://discuss.elastic.co/t/using-kube-state-metrics-custom-resource-state-metrics-breaks-metricbeat/341249/1 "2023-08-21T13:32:04Z")
Hi there,
I am running metricbeat:8.6.1 and prometheus:2.43.1 on AKS 1.25.6
Both of these are scraping metrics from kube-state-metrics:2.8.2
Because of an edge case we were forced to make use of the Custom Resource State Metrics functionality within kube-state-metrics as described here: [https://github.com/kubernetes/kube-state-metrics/blob/main/docs/customresourcestate-metrics.md](https://github.com/kubernetes/kube-state-metrics/blob/main/docs/customresourcestate-metrics.md)
A new metric was introduced that is of the type “ **Info** ”.
After this was deployed to kube-state-metrics, Prometheus was able to scrape this and all worked perfect.
The only problem is that it seems to break meticbeat.
When looking in the logs, we see the following:
`decoding of metric family failed: text format parsing error in line 13966: unknown metric type "info".`
Is this a case of missing functionality or miss configuration?
Many thanks!
Kind regards,
Morné Kruger
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 18, 2023, 3:32pm UTC](https://discuss.elastic.co/t/using-kube-state-metrics-custom-resource-state-metrics-breaks-metricbeat/341249/2 "2023-09-18T15:32:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.