Admin API Research about new potential aggregated Information - Githubissues

amosproj / amos2023ss01-apache-pulsar-ui

MIT License

5 stars 2 forks source link

Admin API Research about new potential aggregated Information #152

Open MPSebastian opened 1 year ago

MPSebastian commented 1 year ago

User story

As a user
I want to see more statistical/aggregated information on all levels
So that the apache pulsar installation gets even more transparent

Acceptance criteria

Create a list of potential new (aggregated) information, that can either be retrieved by the Admin API directly or calculated in the backend based on already exisitng information => for example the active/passive subsriptions rate, etc...
Also consider the implementation/performance effort for each item

Definition of done (DoD)

Feature is done when the acceptance criteria are fullfiled
Feature is done when there are test where it is necessary and they pass
Feature is done when the linter passes
Feature is done when it is merged onto our main branch (after the code has been reviewed by at least one other person)
Feature is done when the code has been documentend or commented properly

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release