# Multiple Instance Per Exporter
**URL:** https://discuss.prometheus.io/t/multiple-instance-per-exporter/777
**Category:** Exporters and Metrics
**Created:** [February 6, 2022, 5:16pm UTC](https://discuss.prometheus.io/t/multiple-instance-per-exporter/777 "2022-02-06T17:16:05Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@guzelcihad](https://discuss.prometheus.io/u/guzelcihad)
#### Post date: [February 6, 2022, 5:16pm UTC](https://discuss.prometheus.io/t/multiple-instance-per-exporter/777/1 "2022-02-06T17:16:05Z")
Hi,
We currently installed memcached exporters into our system. We saw that 1:1 mapping between exporters and memcached instances. I just saw that there are some issues that people want to use one exporter to export metrics from multiple instances. It seems the committers don’t recommend this way but open for discussion. But I couldn’t see any discussion in github. So, I want to listen from you why you decide this 1:1 mapping and why you don’t want to support it 🙂
The issue I am talking about is [here](https://github.com/prometheus/memcached_exporter/issues/22)
---
### Author:  [@stuart](https://discuss.prometheus.io/u/stuart)
#### Post date: [February 6, 2022, 9:35pm UTC](https://discuss.prometheus.io/t/multiple-instance-per-exporter/777/2 "2022-02-06T21:35:22Z")
In general the model for Prometheus is to have applications instrumented & scraped directly, or to have an exporter that stands in for that. So in general the recommendation is 1:1 - ideally installing the exporter right next to the application it is monitoring (i.e on the same server).