# Prometheus as remote write receiver from prometheus agent

**URL:** <https://discuss.prometheus.io/t/prometheus-as-remote-write-receiver-from-prometheus-agent/1642>\
**Category:** Prometheus server\
**Created:** [May 10, 2023, 10:32am UTC](https://discuss.prometheus.io/t/prometheus-as-remote-write-receiver-from-prometheus-agent/1642 "2023-05-10T10:32:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bogdanblinov](https://dub1.discourse-cdn.com/flex017/user_avatar/discuss.prometheus.io/bogdanblinov/32/704_2.png) [@bogdanblinov](https://discuss.prometheus.io/u/bogdanblinov)\
**Post date:** [May 10, 2023, 10:32am UTC](https://discuss.prometheus.io/t/prometheus-as-remote-write-receiver-from-prometheus-agent/1642/1 "2023-05-10T10:32:59Z")

</div>

Hello Guys!  
I want to use prometheus as a central metrics storage (aka push based metrics solution) with remote receive capability enabled and push metrics to this prometheus server through remote write api with prometheus agents from multiple kubernetes clusters. I’ve found that it’s supported configuration from official docs.

But I also found that remote-write-receiver capability of prometheus should be used only for low-volume use cases with caution. And it’s confusing. Is prometheus server strong enough to handle load from multiple prometheus agents? Which cases should be avoided when we enable remote receive capability?

> **[HTTP API | Prometheus](https://prometheus.io/docs/prometheus/latest/querying/api/#remote-write-receiver)**
>
> An open-source monitoring system with a dimensional data model, flexible query language, efficient time series database and modern alerting approach.

It would be highly appreciated, if someone can share real experience with this setup in production. Thank you!