<p>I am using elastic search exporter to pull elastic search metrics to prometheus.
I installed the helm chart and could see the metrics on <a href="http://127.0.0.1:9108/metrics" rel="nofollow noreferrer">http://127.0.0.1:9108/metrics</a> with port forwarding.
But i don't see any metrics coming to prometheus.
Can someone please tell me where to start troubleshooting the issue?</p>

Kumar
<p>There are a few options that might help you:</p>
<ul>
<li>Check <a href="https://github.com/prometheus-community/helm-charts/blob/main/charts/prometheus-elasticsearch-exporter/values.yaml" rel="nofollow noreferrer">ServiceMonitor</a> configuration of <code>prometheus-elasticsearch-exporter</code> and ensure that it is  enabled:</li>
</ul>
<pre><code>serviceMonitor:
  enabled: true
</code></pre>
<ul>
<li>Read about <a href="https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack#prometheusioscrape" rel="nofollow noreferrer">Scrape</a> configuration of <code>kube-prometheus-stack</code> and setup it according to your goals.</li>
</ul>
<blockquote>
<p>By default, Prometheus discovers PodMonitors and ServiceMonitors within its namespace, that are labeled with the same release tag as the prometheus-operator release. Sometimes, you may need to discover custom PodMonitors/ServiceMonitors, for example used to scrape data from third-party applications. An easy way of doing this, without compromising the default PodMonitors/ServiceMonitors discovery, is allowing Prometheus to discover all PodMonitors/ServiceMonitors within its namespace, without applying label filtering. <strong>To do so, you can set prometheus.prometheusSpec.podMonitorSelectorNilUsesHelmValues and prometheus.prometheusSpec.serviceMonitorSelectorNilUsesHelmValues to false.</strong></p>
</blockquote>
