# Use otel prometheus receiver or prometheus scrape component

**URL:** <https://community.grafana.com/t/use-otel-prometheus-receiver-or-prometheus-scrape-component/128423>\
**Category:** Grafana Alloy\
**Tags:** promethues, grafana, alloy\
**Created:** [August 12, 2024, 12:42pm UTC](https://community.grafana.com/t/use-otel-prometheus-receiver-or-prometheus-scrape-component/128423 "2024-08-12T12:42:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chetanmehta1910](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chetanmehta1910](https://community.grafana.com/u/chetanmehta1910)\
**Post date:** [August 12, 2024, 12:42pm UTC](https://community.grafana.com/t/use-otel-prometheus-receiver-or-prometheus-scrape-component/128423/1 "2024-08-12T12:42:39Z")

</div>

Hello, I am exploring the usage of otel prometheus receiver vs prometheus scrape component in my setup.

Current setup:

- Microservices are instrumented with Prometheus client library and are exposing metrics in Prometheus format
- There is a central Prometheus backend
- The central Prometheus server is directly scraping metrics from all hosts - a small test setup of 2 host with 10x microservices.

Requirement: Scale the setup for prod - 10s of microservices on 100s of hosts.

Possible scraping setup:  
It seems efficient to run a light-weight Prometheus agent on each host machine that just scrapes and sends the data to remote Prometheus server - could be distributed and horizontally scaled using Thanos/mimir in future

Understanding:

- Prometheus agent mode is interesting but still experimental
- Prometheus federation setup would be heavyweight and overkill
- Grafana alloy prometheus scrape or prometheus otel collector component can cater to the usecase

Query:

1. Can you please suggest which would be the right component for such a usecase ?
2. Does otel collector convert the prometheus metrics to opentelemetry metrics implicitly. If yes, what is the performance impact ?