add dashboard service for aggregated information collection #326
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@tuteng Can you review this pull request when you have time? |
tuteng
approved these changes
Oct 1, 2020
sde-melo
pushed a commit
to Singlespot/pulsar-manager
that referenced
this pull request
Jan 15, 2021
Fixes apache#282 ### Motivation This is the way I understand how it would be: The access controll is done by environmentController when users retrive the environment list from 'environment' front end page, where the aggregated data is displayed on. And we can then retrieve the total number of tenant and corresponding namespace from certain environments, as well as a list of topicStat, from which we can further retrieve the number of cluster, broker, producer and consumer. 1. environment -> tenant 2. tenant -> namespace 3. environment -> topicStat 4. topicStat -> cluster 5. topicStat -> broker 6. topicStat -> producer 7. topicStatId -> consumer For the number of bookies, currently it is not persistent in database, so the bookieservice is called to retrieve the data. *Explain here the context, and why you're making that change. What is the problem you're trying to solve.* ### Modifications As apache#282 suggested, added some new sql statements in corresponding mapper and a new service to collect aggregated data for dashboard. ### Verifying this change - [ yes ] Make sure that the change passes the `./gradlew build` checks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #282
Motivation
This is the way I understand how it would be: The access controll is done by environmentController when users retrive the environment list from 'environment' front end page, where the aggregated data is displayed on. And we can then retrieve the total number of tenant and corresponding namespace from certain environments, as well as a list of topicStat, from which we can further retrieve the number of cluster, broker, producer and consumer.
2. tenant -> namespace
4. topicStat -> cluster
5. topicStat -> broker
6. topicStat -> producer
7. topicStatId -> consumer
For the number of bookies, currently it is not persistent in database, so the bookieservice is called to retrieve the data.
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
As #282 suggested, added some new sql statements in corresponding mapper and a new service to collect aggregated data for dashboard.
Verifying this change
./gradlew buildchecks.