Describe the bug
There seems to have a regression in the documentation #1650

There is still no body request in the current admin REST API

To Reproduce
Steps to reproduce the behavior:

1. Go to https://pulsar.apache.org/admin-rest-api/?version=2.5.0#operation/setMaxProducersPerTopic
2. There is no request body parameters

Expected behavior
To see request body parameters, th

I am looking for how to install and use PULSAR for FIM monitoring ,

The repo has been changed three times from the looks to what it is now. And from the look it looks like this has gone to the standalone app called hubble , but I don't see anyway to run, execute , or configure pulsar in hubble.

Here is the documentation , let me know which should I be following for this.

https://hubbl

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

Rather than have the users choose from a list of pre-defined configurations, it might be useful to have a simple command line tools that will take in all of these values as parameters, and generate the YAML configuration file automatically.

e.g. ./bin/generate-workload --num-topics=3 --msg-size=100kb --num-producers=5 ....etc.

in send_message, we request from the producer engine that it sends a message on a topic without specifying which producer should do it (we could have multiple producers for one topic): https://github.com/wyyerd/pulsar-rs/blob/master/client/src/producer.rs#L97-L100
we should have some kind of internal identifier to decide which producer should send the message

Currently when we are in topic's details view, we have to use the reload button to refresh.

When we use browser refresh it doesn't work. It should be great to generate url from topic's label to directly show topic's detail using url.

"Pulsar源码解析.md" becomes a very large file. It might be good to break it down into multiple smaller md files and organize them into sections.

All CSS declarations in the product scratch file should be reviewed, documented, and ticketed in the appropriate issue tracker.

Further details in epic: #1053

Done when

Must

• All scratch rules documented with pattern detailed in Pulsar developer guide
• All scratch rules linked to an appropriate ticket in GitHub or Jira

It would be good to have plotting functions to produce plots of one parameter vs another for any numerical parameters that had been queried.

In particular, for a start it would be nice to have a pvspdot function that automatically produces a P-Pdot diagram (this could include the pulsar death line, lines of characteristic age, lines of constant magnetic field, and it could have different marker