# AutoDiscover ServiceMonitor CRD on Kubernetes
**URL:** https://discuss.elastic.co/t/autodiscover-servicemonitor-crd-on-kubernetes/286642
**Category:** Beats
**Tags:** metricbeat
**Created:** [October 13, 2021, 3:28pm UTC](https://discuss.elastic.co/t/autodiscover-servicemonitor-crd-on-kubernetes/286642 "2021-10-13T15:28:27Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@julianxhokaxhiu](https://discuss.elastic.co/u/julianxhokaxhiu)
#### Post date: [October 13, 2021, 3:28pm UTC](https://discuss.elastic.co/t/autodiscover-servicemonitor-crd-on-kubernetes/286642/1 "2021-10-13T15:28:27Z")
Hi,
I have a question about Metricsbeat. I've seen in the official documentation that the service supports AutoDiscovery which is great ( [Autodiscover | Metricbeat Reference [7.15] | Elastic](https://www.elastic.co/guide/en/beats/metricbeat/current/configuration-autodiscover.html) ).
Officially it supports Nodes, Pods and Services. Would it be possible to support the ServiceMonitor CRD manifest type too? I'd be happy to contribute with a Go patch if required, but I'd need some help to understand what to patch on the (official?) Metricbeats Github repository ( [beats/metricbeat at master · elastic/beats · GitHub](https://github.com/elastic/beats/tree/master/metricbeat) ).
Supporting this manifest type would solve once and for all the scenario where Charts do deploy this service type, thinking you'll pair them with Prometheus and ensure we can still forward metrics to Elasticsearch through Metricsbeat.
Thank you in advance,
Julian
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 10, 2021, 5:29pm UTC](https://discuss.elastic.co/t/autodiscover-servicemonitor-crd-on-kubernetes/286642/2 "2021-11-10T17:29:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.