Is your feature request related to a problem? Please describe.

There is apache pulsar deploy-monitoring article, it describes how to to collect metrics.

These are exposes metrics (via prometheus endpoint)

https://github.com/apache/pulsar/blob/master/site2/docs/reference-metrics.md

Most of them are performance

OS:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic

Hi,
I have Pulsar instance running in standalone mode.
Also I started Pulsar-Manager with docker. Here is the command line:
`docker run -it -p 9527:9527 -e REDIRECT_HOST=http://127.0.0.1 -e REDIRECT_PORT=9527 -e DRIVER_CLASS_NAME=org.postgresql.Driver -e URL='jdbc:postgresql://127.0.0.1:5432/pulsa

Currently, After we create a partitioned topic, for a topic that has no producer/consumer created on it,
running command
bin/kafka-run-class.sh kafka.tools.GetOffsetShell --broker-list 127.0.0.1:9092 --topic topic8 --time -1
will return
"Topic topic8 does not exist".

Add Pulsar Proxy support.

This is required to use SAAS offerings, which do not expose the brokers directly to the internet.