# What's the best practice to use metricbeat for prometeus protocol collection on Kubernetes cluster
**URL:** https://discuss.elastic.co/t/whats-the-best-practice-to-use-metricbeat-for-prometeus-protocol-collection-on-kubernetes-cluster/273096
**Category:** Beats
**Tags:** metricbeat
**Created:** [May 16, 2021, 1:04am UTC](https://discuss.elastic.co/t/whats-the-best-practice-to-use-metricbeat-for-prometeus-protocol-collection-on-kubernetes-cluster/273096 "2021-05-16T01:04:54Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@shoothzj](https://discuss.elastic.co/u/shoothzj)
#### Post date: [May 16, 2021, 1:04am UTC](https://discuss.elastic.co/t/whats-the-best-practice-to-use-metricbeat-for-prometeus-protocol-collection-on-kubernetes-cluster/273096/1 "2021-05-16T01:04:54Z")
We are deploying metricbeat as a daemon set to collect vm、docker metrics. It works well.
If we want metricbeat to collect Pulsar、Flink(they are Deploy on k8s）'s prometheus metrics.
Currently, I found that metricbeat promtheus module only support config ip address, which can changed all the time.
I was wondering if it will be nice for metricbeat to support service discovery mechanism ?
Additional, StatefulSet on k8s can be supported by deploy a single metricbeat and config these domains on metricbeat. For statefulset, is this better or service discover better?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 13, 2021, 3:05am UTC](https://discuss.elastic.co/t/whats-the-best-practice-to-use-metricbeat-for-prometeus-protocol-collection-on-kubernetes-cluster/273096/2 "2021-06-13T03:05:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.