# Promproxy -- A more flexible and simple way to implement PushProx

**URL:** <https://discuss.prometheus.io/t/promproxy-a-more-flexible-and-simple-way-to-implement-pushprox/2209>\
**Category:** Development\
**Created:** [March 22, 2024, 8:39am UTC](https://discuss.prometheus.io/t/promproxy-a-more-flexible-and-simple-way-to-implement-pushprox/2209 "2024-03-22T08:39:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![LawyZheng](https://dub1.discourse-cdn.com/flex017/user_avatar/discuss.prometheus.io/lawyzheng/32/934_2.png) [@LawyZheng](https://discuss.prometheus.io/u/LawyZheng)\
**Post date:** [March 22, 2024, 8:39am UTC](https://discuss.prometheus.io/t/promproxy-a-more-flexible-and-simple-way-to-implement-pushprox/2209/1 "2024-03-22T08:39:10Z")

</div>

Based on PushProx, but trying to do it more simply and flexibly.

No need to deploy a client, no need to open an HTTP port waiting to be scraped in your application.  
You just need to add two lines to get it to work.

Github: [GitHub - LawyZheng/promproxy: Go libarary to allow Prometheus to scrape through NAT etc.](https://github.com/LawyZheng/promproxy)