# Service Metrics: Prometheus Configuration

You can use Prometheus to collect service metrics from ESS. ESS-specific metrics use the prefix **`application_com_inrupt_`**, followed by a service-specific key. For example, the [Query Service Indexer](https://docs.inrupt.com/ess/2.5/services/service-query/query-indexer) uses the prefix **`application_com_inrupt_query_fragments_ingest_`**.

To enable discovery and scraping by an appropriately configured Prometheus metrics scraper, those ESS services that emit metrics have the following annotations in their **`spec`**:

<pre class="language-yaml"><code class="lang-yaml">---
spec:
  template:
    metadata:
      annotations:
<strong>        prometheus.io/port: "8443"
</strong><strong>        prometheus.io/scheme: https
</strong><strong>        prometheus.io/scrape: "true"
</strong><strong>        prometheus.io/path: /q/metrics
</strong></code></pre>

For services with these annotations, the Prometheus metrics scraper can scrape the services’ Kubernetes pods by making an HTTPS request on port **`8443`** with a path of **`/q/metrics`**.

See also:

* [Storage Metrics](https://docs.inrupt.com/ess/2.5/administration/storage-metrics) for specifics on Pod storage metrics emitted.